What is the Impeccable skill? Installation and commands

Impeccable is an open-source skill that refines the design of screens built by AI coding agents. It turns requests such as “make it bolder” and “review this” into 24 commands, and it uses rules to find the patterns that make a page look AI-made. This guide covers installation, first steps, common commands and the detector.

Skillshop operator and creator of the Maker Evan YouTube channel
8 min read

Translated from Korean. View original

Misaligned interface blocks snapping to guides after the /impeccable polish command
In this guide
  1. What is the Impeccable skill?
  2. Why use a design skill?
  3. How do you install Impeccable?
  4. What should you do first after installing?
  5. How are the 24 commands grouped?
  6. How do you ask for a command?
  7. How do critique and audit differ?
  8. Where do you run the detector?
  9. What should you know before using it?
  10. Frequently asked questions
  11. Sources

What is the Impeccable skill?

Impeccable is a design skill created by Paul Bakaus. The repository describes itself as the design vocabulary for your coding agent. It started from Anthropic's frontend-design skill and is released under the Apache 2.0 license. It had passed 100,000 GitHub stars as of November 2026.

It works with many coding tools, including Claude Code, Cursor, Codex CLI, GitHub Copilot, Gemini CLI and OpenCode. The official documentation is at impeccable.style.

The README says Impeccable is strongest on interfaces that already exist. You point it at a page or a component and iterate. It can also build new pages.

Why use a design skill?

Ask an agent for a page with no other guidance and similar screens keep appearing. The README lists examples: Inter for all text, purple-to-blue gradients, cards nested in cards, gray text on colored backgrounds and a rounded-square icon above every heading.

Impeccable addresses this in three ways: words for the direction you want, commands that review a design and a detector that finds common patterns with rules.

Words for what you wantInstead of “make it pop”, use a command such as bolder that names one move.
Review commandscritique scores usability, and audit checks accessibility and performance.
Pattern detector62 rules find common patterns and quality problems. It needs no LLM and no API key.
The three roles of Impeccable described in the README.

How do you install Impeccable?

Run “npx impeccable install” in your project folder. The installer detects the coding tools you use and asks whether to install for this project or globally. When it finishes, reload your coding tool and run “/impeccable init”. In Codex the command is “$impeccable init”.

In Claude Code you can also install it as a plugin. Type “/plugin marketplace add pbakaus/impeccable”, then install Impeccable from the “/plugin” screen. If it is already installed, “npx impeccable update” fetches the new version.

The installer also asks whether to install the design hook. The hook runs the detector every time the agent edits a UI file and hands the findings back to the agent. The README notes that in Claude Code hooks run separately from the model's command approvals. Review the installed hooks before you leave an agent running unattended.

STEP 1InstallRun npx impeccable install in the project folder.
STEP 2Reload the toolRestart the coding tool so it reads the skill.
STEP 3Describe the projectCreate PRODUCT.md with /impeccable init.
The install order given in the README.

What should you do first after installing?

Run “/impeccable init” once per project. It reads your code and asks only what it cannot infer: who the product is for, what it needs to do and what the constraints are. The answers are saved to a PRODUCT.md file, and every later command reads it.

If the project already has a design, run “/impeccable document”. It captures the colors, fonts and spacing rules you use now in a DESIGN.md file. With that file in place, changes stay on-brand. Commit PRODUCT.md and DESIGN.md to the repository so teammates work to the same standard.

How are the 24 commands grouped?

The commands fall into five groups by when you use them. You do not need to memorize them. Type “/impeccable” alone to see the list. The 24th, craft, is a deprecated alias.

GroupCommandsWhen to use
Steerbolder, quieter, distill, colorize, typeset, layout, animate, delight, overdriveTo make a design bolder, calmer or simpler
Reviewcritique, auditTo learn what to fix and in what order
Finishpolish, harden, clarify, adapt, optimize, onboardTo cover error states, copy, screen sizes and performance before shipping
Iterate livelive, generateTo pick an element on a running page and try variants
Plan and set upshape, init, document, extractTo plan before writing code or to organize project information
The command list in the README, organized by group.

How do you ask for a command?

Write the target after the command name. The README examples are “/impeccable critique the onboarding flow”, “/impeccable quieter the landing page” and “/impeccable polish settings”. You can also describe what you want without a command name, as in “/impeccable redo this hero section”.

Narrow targets give better results. The README says that reviewing one section closely beats looking over a whole page. If you are starting out, pick one component such as a pricing table or a sign-up screen and run critique first.

You can pin a command you use often, as in “/impeccable pin audit”. After that, typing “/audit” runs it.

critiqueGet what to fix and the priorities.
Steer commandsChange one thing at a time with bolder or quieter.
polishMake the final pass before shipping.
An example flow: review one component, change it and finish it.

How do critique and audit differ?

Both are review commands, but they look at different things. critique evaluates the design against usability criteria, and audit checks technical quality. Run critique when a screen looks off, and audit for a check before shipping.

critique
  • Scores the design against usability heuristics
  • Ranks what to fix first
  • Use it to learn why a screen looks off
audit
  • Checks accessibility, performance, theming and responsive behavior
  • Ranks findings from P0 (blocking) to P3 (polish)
  • Use it to find what is missing before shipping
A comparison of the two review commands, based on the README.

Where do you run the detector?

You can run the detector in three places. Inside the agent, the design hook runs it automatically. In a terminal or CI, name a folder, as in “npx impeccable detect src/”, or pass a URL to scan the rendered page. In the browser, the Chrome extension overlays the same findings on the page.

Source files such as JSX and TSX get the pattern rules only. Rules that need a rendered page, such as low contrast and tiny text, run when you scan a URL. That is why the README recommends scanning your dev server address as well.

If you use it in CI, know the exit codes. 2 means findings, and 1 means a target could not be scanned. You can register exceptions for deliberate choices such as a brand font.

WhereHowGood to know
AgentThe design hook runs automaticallyIt scans every time the agent edits a UI file
Terminal and CInpx impeccable detect src/It runs without an agent
BrowserChrome extensionIt overlays findings on the open page
The three ways to run the detector described in the README.

What should you know before using it?

“/impeccable live” opens an overlay on your running dev server. Select an element and pick a direction, and it swaps variants in place, then writes the one you accept back to your source code. The README says to use live mode only in a local checkout and not to inject it into a deployed site.

When a new design starts, the skill fetches a set of visual directions from impeccable.style. You can turn off the anonymous record of which directions were shown and which one you picked with “npx impeccable telemetry off”. The README states that your project name, files, code and PRODUCT.md are never sent.

If the setup breaks, run “/impeccable doctor”. It finds stale context files, unused settings and broken hooks.

Frequently asked questions

Is Impeccable free?

It is open source under the Apache 2.0 license, so it is free to install. Run “npx impeccable install” in your project folder. The detector works without an LLM or an API key.

Does Impeccable work only in Claude Code?

No. It supports many coding tools, including Claude Code, Cursor, Codex CLI, GitHub Copilot, Gemini CLI and OpenCode. In Codex you type “$impeccable” instead of the slash command.

Which Impeccable command should you try first?

Pick one component and run critique first. It tells you what to fix and in what order. Then change one thing at a time with a steer command such as bolder or quieter, and finish with polish before shipping.

Sources