
Design skill for coding assistants...
Without project context, an assistant tends to return an interface that could belong to anyone. This skill starts with a short interview and writes the audience and goals into a product brief, then can record existing colors, type, and components in a design brief. Commands are grouped into create, evaluate, refine, simplify, and harden, including type, noise reduction, audit, and picking an element in the browser to compare variants. The design check runs in code and does not need a separate model key. It fits product and frontend teams who keep changing UI in a coding assistant and want the next page to reuse the same visual decisions.
Impeccable is a design skill for coding assistants, published as pbakaus/impeccable. A set of commands splits creating an interface, changing an existing page, and recording a design system into named actions. Init writes the audience and goals into a product brief, and colors, type, and components can be recorded in a design brief. Later commands read both files first. Checks can send findings back while the assistant edits, or scan files and a rendered page from the terminal. The installer picks the build for the coding tool you use.
Difficulty: Intermediate
Product brief and design brief
Init writes audience and goals into the product brief. The document command records existing colors, type, and components into a design brief that later commands read.
Commands named by the kind of change
Commands cover shaping, audit, critique, type, color, layout, motion, noise reduction, adaptation, and polish, so one kind of change can be requested alone.
Compare variants in the browser
The live command points at the running page, lets you pick an element, compare variants, and keep the one you want.
Design checks while editing
A hook sends detector findings back to the assistant when UI changes. The detector runs in code and does not need a separate model key.
Build a signup page from one sentence
Tell the assistant to design a signup page for a monthly book club, let the skill pick a direction, and then land it in code.
Polish an existing pricing page
Polish the pricing page, keep the corners and palette that already work, and only change the parts that still look templated.
Record the visual system in the repo
When the project already has components, the document command writes a design brief so the next page and the next assistant read the same rules.
The docs say to run init in the assistant first. It holds a short interview and writes the audience and goals into the product brief. At the end you can run the document command, which looks at existing colors, type, and components and writes the design brief. Later commands read both files before they generate. Without that context, the result is more likely to be a generic interface. The install command picks the build for your coding tool.
Use a description or the shape command for something new. For a page that exists, pick the command that matches the problem. Distill when it is cluttered, the type command when text is hard to read, critique to see what is holding the design back, and audit before release to find implementation problems. Polish is a finishing pass, not a rewrite. The live command picks an element on the running page, compares variants, and keeps one. If you are unsure, describe the outcome and let the main command choose.
The docs say the design hook runs in code. It inspects UI edits and sends findings back to the assistant without a separate model key. The same kind of detector can be run again from the terminal against files or a rendered page. Some coding tools require you to trust the hooks first, and the checks do not run automatically until you do. The Copilot app can enable it in experimental settings. Other tools use the install command or the skills command.
Real reviews and feedback from users