Tool: final quality pass (impeccable polish)
What it does
- The last quality pass before something ships.
- It refines. It never hides a redesign inside a polish.
- If the idea itself is wrong, it says so and recommends a redesign or
bolder.
When to reach for it
- The direction is right and the details are off.
- After a
critique: it reads the P0 and P1 issues as its to-do list.
How to use it
- Run
/impeccable polish <target>. The source's example: /impeccable polish settings.
- It sorts each problem first: a missing token, a one-off, a mismatch with the idea, or a local fault. Then it fixes at the narrowest level that's right.
- Order of work:
- broken tasks, data loss and paths some people can't use;
- missing states;
- flow, order, phones, and drift from the design system;
- visual and motion mismatches;
- code cleanup.
- A rule-checker hit is evidence of a fault. A clean scan is not proof of quality.
- It doesn't perfect one corner while the rest stays below the same bar.
- It doesn't add animation just to make the polish visible.
- The source's form is
/impeccable <command> <target>, typed in your agent ($impeccable on Codex). Narrow targets get better results: one section beats a whole page.
What happened when we used it
- Not run as a command. Its "de-tell" fixes were applied by hand: numbers off, softer section labels, a plain off-white background.
Source