How you invoke /impeccable.

A loop, not a list. Run one sub-command in a chat, chain a few in a session, or open the live picker and iterate on the surface in your browser.

Iterate where you can see it.

Click an element in the running app. Pick a sub-command, optionally annotate, hit Go. Impeccable wraps the element, writes two or three variants into the source, and HMR cycles them in front of you. Accept the one you want. The rest are removed.

Read the live spec

Plan, build, review, refine.

One canonical shape. Each step is a sub-command you invoke in chat.

  1. Plan /impeccable shape Think before you build. Produce a design brief through discovery, not guesswork.
  2. Build /impeccable craft Design it, then build it, all in one flow.
  3. Review /impeccable critique A design review with scoring, persona tests, and automated detection.
  4. Refine /impeccable polish The meticulous final pass between good and great.

Already shipped? Skip ahead with /impeccable live on the page that needs work, or /impeccable audit for a technical pass.

How commands imply each other.

Four shapes that show up across most sessions. Learn these and the rest is filling in detail.

bolder quieter

Two halves of voice. Loud or restrained, never neutral.

audit harden

Find the technical issues. Then fix them.

shape craft

Plan the feature. Then build the plan.

Every sub-command, by lifecycle phase.