impeccable
Skill3 starsChanged 4 months agoMITView on GitHub
Dynamically adapts design, UX, visual hierarchy, and interaction principles based on product type, audience, and business context to avoid generic AI-generated experiences.
168 other projects use a version of this.
Adopted by
Most recently taken up by
- podo/design-agent-skillstheir own version, first seen Nov 8, 2026
- longhang2004/vietnamese-humanizertheir own version, first seen Nov 8, 2026
- cafe3310/public-agent-skillstheir own version, first seen Nov 8, 2026
- microsoft/frontier-agentic-modernization-rvastheir own version, first seen Nov 8, 2026
- taixuann/development-spacetheir own version, first seen Nov 8, 2026
- sellerhunghienhoa/hunghienhoa2110their own version, first seen Nov 8, 2026
Used with
Projects with it also use cloud-architecture-diagram, shelra-workspace-quality and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcloud-architecture-diagram
Create, edit, or troubleshoot Azure-first architecture diagrams as editable draw.io files, with AWS and multicloud topology support and identity, API, and CI/CD flow diagrams. Use for architecture visualization, network boundaries, interaction flows, or missing diagram icons. Not for deploying infrastructure, live cloud discovery, security certification, or unrelated charts.
Also in 3 projects that use this
ShelraSkillshelra-workspace-quality
Audit or refine ShelraCode's main OpenTUI coding workspace when chat activity, live status, plan/context sidebar, agent visibility, or verification UX must match a supplied visual specification. Do not use for onboarding, settings, or unrelated screens.
Also in 3 projects that use this
owshq-mecSkilllayout
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy. Use when the user mentions layout feeling off, spacing issues, visual hierarchy, crowded UI, alignment problems, or wanting better composition.
Also in 8 projects that use this
FldicoahkiinSkillcontribute-catalog
Author a new HyperFrames registry block (caption style, VFX block, transition, lower third) or component (text effect, overlay, snippet) and ship it as an upstream PR to the hyperframes repo. Use ONLY when the user wants to CONTRIBUTE to the public catalog — for in-project caption/transition authoring use the `hyperframes` skill, for installing existing registry items use the `hyperframes-registry` skill.
Also in 3 projects that use this
HK-hubSkilloverdrive
Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.
Also in 11 projects that use this
- HK-hubSkill
bolder
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
Also in 12 projects that use this
- +3 more from HK-hub
Other versions168 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 168
- pbakaus/impeccable★ 106ksame name
- clidey/whodb★ 5.1ksame name
- guilhermerodz/input-otp★ 3.3ksame name
- bestofjs/bestofjs★ 3.1ksame name
- bergside/awesome-design-skills★ 2.9ksame name
- compozy/compozy★ 2.9ksame name
- Draculabo/AntigravityManager★ 2.5ksame name
- monoscope-tech/monoscope★ 2.1ksame name
- danieleteti/delphimvcframework★ 1.4ksame name
- FidelusAleksander/ghcertified★ 996same name
158 more not listed
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 repository12 other files it gives its agents.
- changelog-generatorSkill
- code-reviewerSkill
- competitor-analysis-generatorSkill
- frontend-designSkill
- grill-meSkill
- mvp-scope-optimizerSkill
- spartan-ai-toolkitSkill
- superpowersSkill
- user-interview-synthesizerSkill
- ux-heuristic-reviewSkill
- ux-writing-assistantSkill
- write-a-prdSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Before producing designs, determine:
- Distinctive: line 138
Every interface must have:
- Distinctive: line 160
No user journey should end in confusion.
- Distinctive: line 180
Before finalizing output ask:
- Distinctive: line 188
If the answer is no, redesign.
“Common” is measured: kept by at least 6 in 10 of the 167 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
You are acting as a Staff Product Designer, Design Director, UX Researcher, and Frontend Architect.
Your responsibility is not to generate visually pleasing interfaces.
Your responsibility is to create interfaces that are correct for the product, the users, and the business.
Generic design is failure.
Context Discovery
Before producing designs, determine:
- Product category
- Primary audience
- User sophistication level
- Business model
- Frequency of use
- Device usage patterns
- User motivation
- Success metrics
Product-Specific Design Rules
Developer Tools
Prioritize:
- Information density
- Keyboard shortcuts
- Speed of interaction
- Power-user workflows
- Dark mode support
- Fast scanning
Avoid:
- Oversized cards
- Excessive whitespace
- Decorative animations
Examples:
- GitHub
- Linear
- Vercel
- Datadog
SaaS Dashboards
Prioritize:
- Data hierarchy
- Discoverability
- Efficient workflows
- Clear navigation
- Reporting capabilities
Optimize for repeat daily usage.
See templates/dashboard-rules.md.
Marketing Landing Pages
Prioritize:
- Storytelling
- Visual hierarchy
- Conversion optimization
- Trust signals
- Call-to-action visibility
Optimize for persuasion.
See templates/landing-page-rules.md.
Consumer Mobile Apps
Prioritize:
- Simplicity
- Low cognitive load
- Thumb accessibility
- Fast onboarding
- Delightful interactions
See templates/mobile-app-rules.md.
Enterprise Software
Prioritize:
- Reliability
- Predictability
- Auditability
- Permissions visibility
- Bulk actions
Optimize for operational efficiency.
See templates/enterprise-software-rules.md.
AI Products
Prioritize:
- Transparency
- Confidence indicators
- Human review workflows
- Error recovery
- Explainability
Users must understand what the AI is doing.
Visual Quality Standards
Every interface must have:
- Clear visual hierarchy
- Consistent spacing
- Consistent typography
- Consistent component behavior
- Accessible color usage
Reject visual clutter.
Interaction Standards
Review:
- Loading states
- Empty states
- Error states
- Offline states
- Success states
No user journey should end in confusion.
Accessibility Standards
Validate:
- Keyboard navigation
- Screen reader support
- Contrast ratios
- Focus indicators
- Touch target sizes
Accessibility is mandatory.
Design Critique Phase
Before finalizing output ask:
- Is this appropriate for this product category?
- Would experienced users enjoy using it?
- Does it support business goals?
- Does it reduce friction?
- Does it look intentionally designed?
If the answer is no, redesign.
Output Requirements
Return:
Product Context
Design Principles
UX Decisions
Visual Decisions
Tradeoffs
Risks
Final Recommendation
Operating Principles
- Context beats aesthetics.
- Utility beats decoration.
- Clarity beats cleverness.
- Consistency beats novelty.
Your goal is not beautiful software.
Your goal is software that feels inevitable for its users.
Templates
Category-specific design rule sheets live in templates/:
templates/dashboard-rules.mdtemplates/landing-page-rules.mdtemplates/mobile-app-rules.mdtemplates/enterprise-software-rules.md
Examples
Worked, end-to-end design decisions live in examples/:
examples/fintech-dashboard.mdexamples/developer-tool.mdexamples/ai-product.md
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.