Impeccable
Design guidance for AI coding agents. 1 skill, 23 commands, live browser iteration, and 41 deterministic detector rules for AI-generated frontend design.
Quick start: From your project root, run npx impeccable skills install, then run /impeccable init inside your AI coding tool. Full docs: impeccable.style.
Why Impeccable?
Anthropic's frontend-design was the first widely-used design skill for Claude. Impeccable started from there.
Every model trained on the same SaaS templates. Skip the guidance and you get the same handful of tells on every project: Inter for everything, purple-to-blue gradients, cards nested in cards, gray text on colored backgrounds, the rounded-square icon tile above every heading.
Impeccable adds:
- One setup flow.
/impeccable init writes PRODUCT.md and offers DESIGN.md, so later commands know the audience, brand/product lane, voice, anti-references, colors, type, and components.
- 23 commands. A shared design vocabulary with your AI:
polish, audit, critique, distill, animate, bolder, quieter, and more.
- 41 deterministic detector rules plus LLM-only critique checks. The CLI and browser extension run the deterministic rules with no LLM and no API key.
What's Included
The Skill: impeccable
The skill installs as one command:
/impeccable <command> <target>
Start every new project with:
/impeccable init
init asks whether the surface is brand (marketing, landing, portfolio) or product (app UI, dashboard, tool), then writes project context that every later command reads.
23 Commands
All commands are accessed through /impeccable:
| Command | What it does |
|---|
/impeccable craft | Full shape-then-build flow with visual iteration |
/impeccable init | One-time setup: gather design context, write PRODUCT.md and DESIGN.md, configure live mode, recommend next steps |
/impeccable document | Generate root DESIGN.md from existing project code |
/impeccable extract | Pull reusable components and tokens into the design system |
/impeccable shape | Plan UX/UI before writing code |
/impeccable critique | UX design review: hierarchy, clarity, emotional resonance |
/impeccable audit | Run technical quality checks (a11y, performance, responsive) |
/impeccable polish | Final pass, design system alignment, and shipping readiness |
/impeccable bolder | Amplify boring designs |
/impeccable quieter | Tone down overly bold designs |
/impeccable distill | Strip to essence |
/impeccable harden | Error handling, i18n, text overflow, edge cases |
/impeccable onboard | First-run flows, empty states, activation paths |
/impeccable animate | Add purposeful motion |
/impeccable colorize | Introduce strategic color |
/impeccable typeset | Fix font choices, hierarchy, sizing |
/impeccable layout | Fix layout, spacing, visual rhythm |
/impeccable delight | Add moments of joy |
/impeccable overdrive | Add technically extraordinary effects |
/impeccable clarify | Improve unclear UX copy |
/impeccable adapt | Adapt for different devices |
/impeccable optimize | Performance improvements |
/impeccable live | Visual variant mode: iterate on elements in the browser |
Use /impeccable pin <command> to create standalone shortcuts (e.g., pin audit creates /audit).
Usage Examples
/impeccable audit blog # Audit blog hub + post pages
/impeccable critique landing # UX design review
/impeccable polish settings # Final pass before shipping
/impeccable harden checkout # Add error handling + edge cases
Or use /impeccable directly with a description:
/impeccable redo this hero section
Anti-Patterns
The skill includes explicit guidance on what to avoid:
- Don't use overused fonts (Arial, Inter, system defaults)
- Don't use gray text on colored backgrounds
- Don't use pure black/gray (always tint)
- Don't wrap everything in cards or nest cards inside cards
- Don't use bounce/elastic easing (feels dated)
See It In Action
Visit impeccable.style to see before/after case studies of real projects transformed with Impeccable commands.
Installation
Option 1: CLI installer (Recommended)
From the root of your project, run:
npx impeccable skills install
This auto-detects your harness and writes the build compiled for it to the right location (.claude/skills/, .cursor/skills/, etc.). Works with Cursor, Claude Code, Gemini CLI, Codex CLI, and every other supported tool. Reload your harness afterward.