Impeccable

What it is

Impeccable is Paul Bakaus’s design skill for coding agents: 24 commands such as polish, bolder, critique and audit, plus a detector for generic AI design. Ask an agent for a page with no other guidance and the same habits come back, such as Inter everywhere, purple-to-blue gradients and cards nested in cards. The detector flags them with 62 deterministic rules, no model and no API key. The README says it is strongest on interfaces that already exist.

1. /impeccable init writes PRODUCT.md once
2. You name a command and a narrow target
3. The agent follows that command’s playbook
4. The design hook scans each UI file it edits
5. Findings go back before the agent calls it done

Who it suits

Front-end developers, designers who code and product teams that ship UI through an AI agent. Teams iterating on a product they already have get the most, since that is where the README says it does best.

If you never touch interface code, there is nothing for it to work on.

Where to use it

It reaches well past one agent.

• Coding agents: the README lists 19, among them Claude Code, Cursor, Codex CLI, GitHub Copilot, Gemini CLI, Grok Build, OpenCode and Google Antigravity
• Design hook: runs on six of them, Claude Code, Cursor, Codex, GitHub Copilot, Grok Build and Hermes Agent
• Terminal and CI: the CLI scans a folder or a rendered page with no agent
• Chrome: an extension overlays the same findings on any live page
• VS Code: an extension installs the skill for GitHub Copilot Chat, without the design hook
• GitHub Copilot app: Impeccable is built in, and you turn it on under Settings, then Experimental

How to set it up

Get it saves a zip of Mindket’s setup notes in your downloads folder, with each agent’s steps from pbakaus’s README.

1. From your project root, run the installer.
2. Pick your coding tools and a project or global scope.
3. Accept the design hook where your tool offers one.
4. Reload your coding tool, then run /impeccable init in your agent, or $impeccable init on Codex.

npx impeccable install

In Claude Code you can add it as a plugin instead, then open /plugin and install Impeccable.

/plugin marketplace add pbakaus/impeccable

Later, one line refreshes an install made with npx.

npx impeccable update

How to use it

Name a command and a target. A narrow target gets better results, since one section reviewed closely beats a whole page at a glance.

/impeccable critique the onboarding flow
/impeccable quieter the landing page
/impeccable polish settings
/impeccable harden checkout

Type /impeccable alone to list the commands, and /impeccable pin audit gives you /audit. In a terminal or in CI, the detector needs no agent. Exit code 2 means findings, and 1 means a target could not be scanned.

npx impeccable detect src/
npx impeccable detect --json .
npx impeccable detect --github src/

Example

After adding a pricing section, you ask for a second opinion on that one component.

/impeccable critique the pricing cards

The agent scores the cards against usability heuristics and ranks what to fix first. Run audit instead and you get a technical report, with findings ranked from P0, blocking, to P3, polish.

For newcomers and experts

If you are new. An AI agent left to itself tends to give every site the same look. Impeccable gives it named design moves, such as bolder or quieter, and a checker that flags the usual habits while it edits. Run /impeccable init on a small project, then ask it to critique one component.

For experts. The detector’s rules make no model call, so a scan is fast and repeatable but catches only what a rule describes. Source files such as JSX and TSX get the pattern rules only. Low contrast and tiny text need a rendered page, so point the CLI at your dev server too. Commands read PRODUCT.md and DESIGN.md, and results improve once both exist. A critique is still a model’s judgment against heuristics: a second opinion, not a pass mark.

Good to know

Checks run on your machine, with a few calls out to the maker’s site.

• Your project: the README says your project name, files, code and PRODUCT.md are never sent
• Design directions: when a new design starts, the skill fetches them from the impeccable.style catalog, even with telemetry off
• Version check: normally at most once a day, it asks impeccable.style for a newer version, with no project content, and IMPECCABLE_NO_UPDATE_CHECK=1 stops it
• Hooks in Claude Code: they run even when you deny the model’s own commands, and the first edit can download an engine binary into ~/.impeccable/bin/
• Live mode: it edits a local checkout only, and applying its copy edits runs your package.json’s impeccable:manual-edit-validate script with your permissions
• Working files: under .impeccable/
• Origin: it started from Anthropic’s frontend-design skill, but it is Paul Bakaus’s project
• License: Apache 2.0

The line below turns telemetry off, which stops only the anonymous record of which direction you picked. DO_NOT_TRACK=1 and IMPECCABLE_NO_TELEMETRY=1 do the same.

npx impeccable telemetry off