Shipping a real interface is a loop. Four phases, each with one place to begin.
Run /impeccable teach once per project to establish PRODUCT.md and DESIGN.md. Then reach for /impeccable craft and describe what you want to build. Shape, build, and iterate happen inside one invocation.
/impeccable teach
/impeccable craft
Teach runs a short discovery interview about audience, register, voice, and anti-references. It writes PRODUCT.md and, if there's code to scan, a DESIGN.md.
PRODUCT.md
DESIGN.md
From that point on, every command reads both files before generating. Craft, polish, critique, live, all of them.
Once something exists, you're iterating. There are two paths: specific commands for named dimensions, or Live Mode for visual exploration.
Type a command and let the skill encode a specific discipline. Best when you know the word: typography, layout, color, motion.
Pick any element in the browser, draw, type, hit Go. Three production-quality variants. Accept one and it writes to source.
Three commands in sequence before anything ships. They don't redesign; they find what still needs to change.
Five dimensions scored 0 to 4: accessibility, performance, theming, responsive, anti-patterns. Findings tagged P0 to P3.
Labels, error messages, empty-state prose, microcopy. Tuned to the audience from PRODUCT.md.
60-character names, German product titles, prices in the billions, 500s, offline. Production data is messy.
Features ship, drift happens. Two commands close the gap before it solidifies.
Find patterns used three or more times with the same intent. Propose tokens and primitives. Migrate call sites in the same pass.
Scans tokens, components, and rendered output. Writes a spec-compliant DESIGN.md that every other command reads.
Brand and product surfaces have different defaults. Impeccable tracks this in PRODUCT.md as a single field, so commands like typeset, animate, and colorize adapt their vocabulary to match.
typeset
animate
colorize
The same element, rendered in brand register (editorial masthead) and product register (utility). Register is answered once during teach and applies to every downstream command.
teach
DESIGN.md follows the format Google Stitch publishes. Not a lock-in. When you outgrow Impeccable or want a second opinion from another tool, the file comes with you.
An anti-patterns list, for using the anti-patterns tool.
Anthropic still promotes their skill in Claude Code, but it's been unmaintained and is now behind on recommended patterns. Run both and they collide on vocabulary, cancelling each other out. Pick one.
Pinning brings back /audit, /polish, /critique as shortcuts. Pin everything and you've re-exploded the / menu the v3.0 consolidation cleaned up. Pin the two or three you reach for daily.
/audit
/polish
/critique
/
Commands still run without PRODUCT.md and DESIGN.md. They default to generic SaaS patterns. The floor is meaningfully higher with context. Run teach once; every later command benefits.
Impeccable is an opinionated design partner, not a validator. It has a point of view. Push back with a reason and it'll work with you. Ignore the opinion without a reason and output gets worse, not better.
Five minutes of discovery, one PRODUCT.md, one DESIGN.md. Every command downstream gets sharper from here.
Four short walkthroughs of the highest-leverage flows: getting started, Live Mode, critique with the overlay, brand vs product.