Workflows

Impeccable commands are designed to chain. These are the high-value sequences.

New feature, start to finish

init → shape → natural-language build request → critique → polish

1. /impeccable init once per project writes PRODUCT.md and offers document when an existing codebase needs DESIGN.md.
2. /impeccable shape runs discovery and produces a design brief.
3. Run /impeccable <describe the feature> to build from the confirmed brief. craft is deprecated and adds no behavior.
4. /impeccable critique scores the result and runs persona tests.
5. /impeccable polish closes the gap between good and great.

Already shipped, needs work

Choose the route by the kind of problem:

• Technical quality: audit → harden

• Subjective design quality: critique → polish

• Focused browser iteration: live

• /impeccable live for iterating on a page directly in the browser, three variants per element.

• /impeccable audit for a technical pass, then /impeccable harden to fix.

Refinement pairs

Voice has two halves. Pick the direction, never leave it neutral.

Push it up	Tone it down
bolder	quieter
overdrive	distill

Evaluate then fix

Find the problem	Then resolve it
audit	harden
critique	polish
audit (performance)	optimize