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
- All-The-Vibes/ATV-PaperBoardtheir own version, first seen Oct 13, 2026
- baekenough/oh-my-customcodetheir own version, first seen Oct 3, 2026
- susannakhloyan-debug/claude-skillstheir own version, first seen Aug 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- baekenough/oh-my-customcode★ 42same name
- All-The-Vibes/ATV-PaperBoard★ 1same name
- susannakhloyan-debug/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- skills/project-starter/template/AGENTS.mdAGENTS.md
- commit-nyancodeidSkill
- dealtech-uiSkill
- devflow-orchestratorSkill
- humanize-writingSkill
- no-emojiSkill
- ponytail-leanSkill
- project-starterSkill
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
- Distinctive: line 14
Overused Typography: Avoid defaulting to Inter, Roboto, Arial, or generic system sans for every project without brand rationale.
- Distinctive: line 15
Cliché Gradients: Stop using generic purple-to-blue or neon violet background gradients.
- Distinctive: line 16
Nested Card Hell: Do not wrap every section in a card, and never nest cards inside cards.
- Distinctive: line 17
Low-Contrast Gray on Colors: Never place light gray text on vibrant or colored backgrounds.
- Very specific: line 18
Pure Black/White: Avoid #000000 and flat #808080.
- Distinctive: line 19
Dated Easing: Avoid springy or bouncy easing curves.
- Distinctive: line 25
When establishing a new interface or redesigning an existing surface:
- Very specific: line 28
DESIGN.md: Document the visual system, typographic scale, color tokens, surface hierarchy, and component contracts. - Distinctive: line 38
Harden: Add edge-case handling for long text truncation, dynamic empty states, and viewport resizing.
“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.
Files
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:
- Overused Typography: Avoid defaulting to Inter, Roboto, Arial, or generic system sans for every project without brand rationale.
- Cliché Gradients: Stop using generic purple-to-blue or neon violet background gradients.
- 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.
- Low-Contrast Gray on Colors: Never place light gray text on vibrant or colored backgrounds. Ensure strict WCAG AA contrast.
- Pure Black/White: Avoid
#000000and flat#808080. Always use subtly tinted darks (e.g. slate, zinc with a hint of blue or warm stone). - 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:
PRODUCT.md: Record the target audience, user intent, functional constraints, tone of voice, and core workflows before writing CSS.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.
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
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.

