Impeccable
I run Impeccable because /polish, /audit, and /critique ship the typography, color and accessibility passes I used to do by hand, fighting AI slop without leaving Claude Code. If you build sites/apps and are not a designer, it acts as your in-residence designer on Claude Code: audits, improves, and polishes the output. **Since version 4.0** the tool no longer lives only in the terminal. Two additions change how you work with it: **Worlds**, which returns several generations at once drawn from distinct design families instead of a single proposal to reprompt, and a **live in-browser editor**, which moves the finishing pass out of the command line. **The front entrance exists too**, and it is the half people forget when they only remember `/polish`. `/impeccable init` writes a `PRODUCT.md` from what you tell it about your product; `/impeccable document` goes the other way and derives a `DESIGN.md` from code that already exists. Those two files are the base every other command reads, and without them the finishing passes arbitrate on the tool default taste rather than on yours. Two opposite commands, `/impeccable bolder` and `/impeccable quieter`, then tune intensity on a named area, replacing the reprompt loop where you keep asking for "a bit less" without ever knowing by how much.
Strengths
- 23 specialized commands: /polish, /audit, /critique and 20+ targeted passes
- NPX skills add, single-command install, no boilerplate
- AI-slop-aware: typography, color, and accessibility audited at the end of the pipeline
- Open source by Paul Bakaus, auditable and extensible
Limitations
- Opinionated design taste, may friction with a very specific existing brand guide
- Tokens burned per pass, target critical surfaces only
Best for
- Vibecoders shipping sites/apps who want a pro look without a designer
- Final design audit before commit/deploy, typo, colors, contrast, alignment
- Product differentiation in a market saturated with generic AI slop