impeccable
Skill589 starsChanged todayApache-2.0View on GitHub
Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: product UI, dashboards, components, forms, settings, onboarding, empty states, and landing pages. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, and edge cases. Also for making bland UI bolder or loud UI quieter. Not for backend-only or non-UI tasks.
161 other projects use a version of this, 105 of them edited.
Adopted by
Most recently taken up by
- joaoguimaraespro/personal-financeedited, first seen Nov 16, 2026
- abiramcodes/angular-doctoredited, first seen Nov 16, 2026
- RIJUDEVx/agent-skillsedited, first seen Nov 16, 2026
- nxxxsooo/loopedited, first seen Nov 16, 2026
- jnMetaCode/impeccable-zhedited, first seen Nov 16, 2026
- vaferkhanom/Website-skillsedited, first seen Nov 16, 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 review Azure and Microsoft ecosystem architecture, GitHub CI/CD, and auth/API diagrams as editable draw.io files; resolve Microsoft and GitHub icons. Use for architecture visualization, diagram critique, or missing icons. Azure DevOps only when explicitly requested. Not for competing-cloud architecture, deployment, live 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-hubSkillbolder
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 versions161 projects use a version of this.
Word for word · 0
None found.
Edited · 105
- pbakaus/impeccable★ 111k19% same
- clidey/whodb★ 5.1k20% same
- guilhermerodz/input-otp★ 3.3k18% same
- bestofjs/bestofjs★ 3.1k18% same
- compozy/compozy★ 2.9k17% same
- Draculabo/AntigravityManager★ 2.5k20% same
- monoscope-tech/monoscope★ 2.1k16% same
- danieleteti/delphimvcframework★ 1.4k18% same
- waynesutton/markdown-site★ 62810% same
- boraoztunc/skills★ 47317% same
95 more not listed
Wrote their own version · 56
- bergside/awesome-design-skills★ 2.9ksame name
- FidelusAleksander/ghcertified★ 1ksame name
- Pasta-Devs/Marinara-Engine★ 765same name
- Fast-Editor/Lynkr★ 640same name
- deadlock-mod-manager/deadlock-mod-manager★ 617same name
- 10xChengTu/Mux0★ 337same name
- theexperiencecompany/gaia★ 327same name
- better-notify/better-notify★ 318same name
- Peiiii/nextclaw★ 263same name
- jagrat7/linux-wallpaper-engine★ 227same name
46 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 repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- pixijs-3dSkill
- pixijsSkill
- cohub-appsSkill
- cohub-boardSkill
- cohub-generateSkill
- cohubSkill
- public-filesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 160 edited versions we read keep these.
3
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 13
Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again.
- Distinctive: line 17
Read the project context: PRODUCT.md (users, purpose, voice) and DESIGN.md (visual system, tokens, components, motion).
- Distinctive: line 63
Otherwise: treat the request as general design work under Setup and How to design.
“Common” is measured: kept by at least 6 in 10 of the 160 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
Design like an award-winning design director: production-grade code, a clear point of view, and a deep grasp of what the product and its users need.
Core principles:
- Finish the job. No hedging, no shortcuts: the deliverable is complete, except assets the user must provide.
- Scale ambition to the surface's mode (see Modes). On Operate and Read, ambition shows as precision and restraint, and patterns the visitor already knows earn their place.
- Verify by looking at the rendered result at the sizes it ships at, and batch the checks: fix what one look shows before looking again.
Setup
- Read the project context: PRODUCT.md (users, purpose, voice) and DESIGN.md (visual system, tokens, components, motion). They are binding; do not invent missing context.
- Load the playbook for the requested command from the table below. For app UI, also read reference/operate.md.
- Immediately before any UI edit, including small refinements, read reference/craft-floor.md: the quality floor and absolute bans. Skip it for planning-only work.
How to design
- The brief wins. Honor pinned aesthetics, fonts, and palettes. Redirecting a clear brief toward your taste is failure.
- Refinement preserves; redesign replaces. Refinement keeps the incumbent identity, behavior, copy, and everything outside scope. Ask before replacing factual copy or adding claims. A redesign keeps product truth, content, and function, but needs the user's explicit go-ahead and ends with DESIGN.md updated.
- Work inside the system. Reuse the tokens, shared primitives, and patterns DESIGN.md names before adding new ones.
Modes
The mode names what the visitor's success looks like on this surface. Choose it from the surface, not the product.
- Operate: the visitor completes a task. App UI, dashboards, editors, settings, tools. Scanability, consistency, native expectations, and the real usage scene outrank expression. Brand lives in precise details.
- Read: the visitor understands something. Docs, guides, changelogs. Structure for comprehension first.
- Persuade: the visitor decides and acts. Landing pages, marketing, pricing. Earn attention and action with bold, distinct work.
- Experience: the visitor is inside the work itself, such as a Board or a showcase. Let the artifact lead; the interface recedes.
Commands
| Command | Description | Reference |
shape [feature] | Plan UX/UI before writing code | reference/shape.md |
extract [target] | Pull reusable tokens and components into the design system | reference/extract.md |
critique [target] | UX design review: heuristics, cognitive load, personas | reference/critique.md |
audit [target] | Technical quality checks (a11y, perf, theming, responsive) | reference/audit.md |
polish [target] | Final quality pass before shipping | reference/polish.md |
bolder [target] | Amplify safe or bland designs | reference/bolder.md |
quieter [target] | Tone down aggressive or overstimulating designs | reference/quieter.md |
distill [target] | Strip to essence, remove complexity | reference/distill.md |
harden [target] | Production-ready: errors, i18n, edge cases | reference/harden.md |
onboard [target] | First-run flows, empty states, activation | reference/onboard.md |
animate [target] | Purposeful animation and motion | reference/animate.md |
colorize [target] | Strategic color for monochromatic UIs | reference/colorize.md |
typeset [target] | Typography hierarchy and fonts | reference/typeset.md |
layout [target] | Spacing, rhythm, and visual hierarchy | reference/layout.md |
delight [target] | Personality and memorable touches | reference/delight.md |
clarify [target] | UX copy, labels, and error messages | reference/clarify.md |
adapt [target] | Different devices and screen sizes | reference/adapt.md |
optimize [target] | Diagnose and fix UI performance | reference/optimize.md |
Routing:
- Explicit or clearly implied command: load its reference and follow it. Ask once if two commands fit.
- No argument: suggest the two or three commands that fit the current context; never auto-run one.
- Otherwise: treat the request as general design work under Setup and How to design.
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.

