agentleFS
EmzyjepppEmzyjeppp/devflow-rules/skills/impeccable-design/SKILL.md

impeccable-design

Skill0 starsChanged 43 days agoMITView on GitHub

Frontend design guidance and anti-pattern elimination based on Impeccable to prevent generic AI UI clichés, overused fonts, and nested card layouts.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Overused Typography: Avoid defaulting to Inter, Roboto, Arial, or generic system sans for every project without brand rationale.

    line 14
  2. Distinctive:

    Cliché Gradients: Stop using generic purple-to-blue or neon violet background gradients.

    line 15
  3. Distinctive:

    Nested Card Hell: Do not wrap every section in a card, and never nest cards inside cards.

    line 16
  4. Distinctive:

    Low-Contrast Gray on Colors: Never place light gray text on vibrant or colored backgrounds.

    line 17
  5. Very specific:

    Pure Black/White: Avoid #000000 and flat #808080.

    line 18
  6. Distinctive:

    Dated Easing: Avoid springy or bouncy easing curves.

    line 19
  7. Distinctive:

    When establishing a new interface or redesigning an existing surface:

    line 25
  8. Very specific:

    DESIGN.md: Document the visual system, typographic scale, color tokens, surface hierarchy, and component contracts.

    line 28
  9. Distinctive:

    Harden: Add edge-case handling for long text truncation, dynamic empty states, and viewport resizing.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Impeccable Design

This skill eliminates predictable AI frontend generation patterns and elevates web interfaces into distinctive, intentional designs.

AI Frontend Anti-Patterns to Eliminate

AI models consistently generate identical visual tropes unless explicitly guided. Avoid these defaults:

  1. Overused Typography: Avoid defaulting to Inter, Roboto, Arial, or generic system sans for every project without brand rationale.
  2. Cliché Gradients: Stop using generic purple-to-blue or neon violet background gradients.
  3. Nested Card Hell: Do not wrap every section in a card, and never nest cards inside cards. Use negative space, subtle borders, or background tint shifts to separate content.
  4. Low-Contrast Gray on Colors: Never place light gray text on vibrant or colored backgrounds. Ensure strict WCAG AA contrast.
  5. Pure Black/White: Avoid #000000 and flat #808080. Always use subtly tinted darks (e.g. slate, zinc with a hint of blue or warm stone).
  6. Dated Easing: Avoid springy or bouncy easing curves; use clean cubic beziers for purposeful, subtle transitions.

For a comprehensive catalog of design anti-patterns, see references/anti-patterns.md.

Durable Product and Design Truth

When establishing a new interface or redesigning an existing surface:

  1. PRODUCT.md: Record the target audience, user intent, functional constraints, tone of voice, and core workflows before writing CSS.
  2. DESIGN.md: Document the visual system, typographic scale, color tokens, surface hierarchy, and component contracts.

Design Modification Commands & Actions

Apply these focused adjustments when refining interfaces:

  • Critique: Review layout for visual hierarchy, semantic grouping, and clarity.
  • Distill: Strip unnecessary visual clutter, decorative wrappers, and extraneous dividers.
  • Bolder: Increase typographic contrast, scale up key metrics, and sharpen visual rhythm.
  • Quieter: Soften high-contrast borders, reduce font weights, and expand whitespace.
  • Harden: Add edge-case handling for long text truncation, dynamic empty states, and viewport resizing.
  • Polish: Align border radiuses, standardize spacing tokens, and verify interaction states (hover, focus, active).

Quick Verification Checklist

  • Typography fits the product personality rather than generic defaults.
  • Content uses open layouts, rhythm, and spacing instead of endless nested card boxes.
  • All text colors maintain accessible contrast against their background surfaces.
  • Animations are subtle, purposeful, and respect reduced motion preferences.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.