Impeccable: design commands and an AI-look checker for your coding agent

What it does

Impeccable, by Paul Bakaus, gives your coding agent a shared design vocabulary. Instead of "make it look nicer", you say /impeccable critique landing or /impeccable polish settings, and the agent knows what kind of pass you mean.

The README describes two parts:

The skill. One /impeccable command with 24 sub-commands: init to record who the product is for, shape to plan before building, critique for a design review, audit for accessibility, speed and phone checks, polish for a final pass, plus bolder, quieter, typeset, layout and more.
The checker. Plain rules that scan your page for common tells of AI-made design. It runs with no AI model and no API key.

It started from Anthropic's frontend-design skill. I have an older copy installed; the commands below come from the current README.

What you need first

Claude Code, Codex, Cursor or another supported agent.
A web project to work on.
Node.js, only if you use the npx installer below.
The skill is free, but it runs inside a coding agent such as Claude Code or Codex, which may need a paid plan.

Install (checked 30 Sep 2026)

From the root of your project, in a normal terminal:

npx impeccable install

It shows which agents it found on your computer and asks whether to install into this project or for all projects. Then, inside your agent's chat (not the terminal), run:

/impeccable init

We ran the installer on a throwaway project on 30 Sep 2026 with npx impeccable install --providers=claude --scope=project. The first try timed out while downloading and installed nothing; the second worked. It added the skill, four helper agents and a design check that runs after each edit, in the project's .claude folder.

Claude Code also has a plugin route: /plugin marketplace add pbakaus/impeccable, then open /plugin and install Impeccable from the list.

First use

Run the checker on a page. In a terminal:

npx impeccable detect index.html

You can point it at a folder (src/) or a live address instead. We tried it on a deliberately generic test page: gradient headline, grey text on purple, Inter font, a card inside a card, "Supercharge your workflow". It reported 8 problems, each with a rule name and one line on what to do, for example that grey text on a coloured background looks washed out and fails the contrast rule.

Then ask the agent to fix the worst ones. In your agent's chat:

and then:

Fix one area at a time and look at the page after each pass.

How it chains with other library skills

Use it after frontend-design or Fable Forge builds a first version.
The checker reads code and pages; it does not look at the page the way a visitor does. Take phone and desktop screenshots with agent-browser too.
The full order is in Vibe-code a website that does not look AI-made.

Watch-outs

Licence: Apache-2.0.
It changes your agent's settings. The installer adds a hook, a small command that runs the checker after your agent edits UI files. You can skip it with --no-hooks. Codex asks you to approve the hook in /hooks.
Rules are opinions, and they clash with other skills. It flags Inter, purple accents and bounce animations as tells, and it discourages cards nested inside cards. high-end-visual-design asks for the opposite on nesting (a card inside an outer shell) and for spring-like motion, and the two disagree on icon sets too. When they conflict, your approved design file wins. Write down each exception you keep (for example "nested cards allowed on the pricing section") in that file, and use the checker's ignore settings for them.
Check before you ship. A clean scan does not mean the page is good, and the agent's edits still need your review before anything is deployed.

Link and credit

github.com/pbakaus/impeccable, by Paul Bakaus, Apache-2.0. Full docs at impeccable.style. This page is our own summary.