Design & frontend

Impeccable

One frontend design skill with 24 commands (critique, audit, polish, bolder and more), PRODUCT.md and DESIGN.md context, and a 62-rule design detector.

Install

Any supported tool

(from the project root)

npx impeccable install

The README says the installer detects your coding tools, asks whether to install for the project or globally, and offers the design hook where the tool supports one. Reload the tool afterwards. For scripts, pass --providers=claude,codex,cursor and --scope=project|global. To update:

npx impeccable update

Node is only needed for npx; the skill runs a self-contained engine binary that ships next to it or downloads once into ~/.impeccable/bin/. In Codex, open /hooks and approve the project hook (again after an update that changes it).

Claude Code plugin

/plugin marketplace add pbakaus/impeccable

Then open /plugin and install Impeccable. The repository’s marketplace.json names the marketplace and the plugin impeccable.

GitHub Copilot in VS Code

code --install-extension renaissance-geek.impeccable

Or install Impeccable from the Visual Studio Marketplace. The README says it needs VS Code 1.109.3+, Copilot Chat and a trusted workspace, and installs the skill without the hook.

Grok Build

grok plugin install pbakaus/impeccable#plugin --trust

Pinned version for a team

(git submodule)

git submodule add https://github.com/pbakaus/impeccable vendor/impeccable
npx impeccable link --source=vendor/impeccable --providers=claude,cursor

Commit .gitmodules, the submodule and the generated links; linking installs skills, not hooks.

Manual copy, no Node

each tool’s build is committed at the repository root. For Claude Code, copy .claude/skills/impeccable into your project’s .claude/skills/ or into ~/.claude/skills/:

mkdir -p your-project/.claude/skills && cp -r .claude/skills/impeccable your-project/.claude/skills/

A manual copy skips the design hook and subagents. Codex CLI uses the .agents/ build, Cursor .cursor/, Gemini CLI .gemini/, Copilot .github/ and Google Antigravity .agent/ (folder table).

Commands as given in the repository README, version 4.8.2.

Impeccable is Paul Bakaus’s Apache-2.0 design skill for coding agents: 24 commands and a design detector.

Impeccable lives in the pbakaus/impeccable repository, which its README calls “the design vocabulary for your coding agent” (README). It is a single skill, impeccable, whose SKILL.md says to use it to “design, redesign, critique, audit, polish or animate a frontend”, from landing pages and dashboards to native iOS and Android screens.

The README says it started from Anthropic’s frontend-design skill, which has its own listing here as the Frontend Design skill. The code is under the Apache 2.0 license; the skill, the Claude Code plugin.json and the npm package are all at version 4.8.2, published to npm on November 9, 2026.

The README lists Claude Code, Cursor, Codex CLI, GitHub Copilot, Devin, Replit Agent, Gemini CLI, Grok Build, OpenCode, Google Antigravity, Kiro, Trae, Rovo Dev, Qoder, Mistral Vibe, Pi, Hermes Agent, DeepSeek Harness and Veto as supported tools.

How it is used

You run /impeccable init once per project ($impeccable init on Codex). The README says it reads your code, asks only what it can’t infer and writes PRODUCT.md, which every later command reads; /impeccable document writes your existing visual system to DESIGN.md. After that you name a command and a target, for example:

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

The README groups the 24 commands like this (README):

Group Commands
Steer bolder, quieter, distill, colorize, typeset, layout, animate, delight, overdrive
Review critique (scored UX review), audit (accessibility, performance, theming and responsive checks, ranked P0 to P3)
Finish polish, harden, clarify, adapt, optimize, onboard
Iterate live live, generate
Plan and set up shape, init, document, extract

The 24th, craft, is a deprecated alias for a plain build request. Typing /impeccable alone shows the list, and /impeccable pin audit gives a command its own shortcut (/audit). The README says the skill is strongest on interfaces that already exist and suggests starting with one component, such as /impeccable critique the pricing cards.

The detector is a set of 62 deterministic rules that, per the README, need no model and no API key. It runs three ways: as a design hook that scans UI files the agent edits (Claude Code, Cursor, Codex, GitHub Copilot, Grok Build and Hermes Agent), from the terminal or CI, and through a Chrome extension. Terminal commands as given in the README:

npx impeccable detect src/                   # scan a directory
npx impeccable detect https://example.com    # scan a rendered page (uses your installed Chrome or Edge)
npx impeccable detect --json .               # machine-readable output
npx impeccable detect --github src/          # GitHub Actions annotations
npx impeccable detect --list-rules           # every rule with its id and description

Exit code 2 means findings and 1 means a target couldn’t be scanned. Rules that need a rendered page, such as low contrast, run only when you scan a URL, so the README suggests pointing it at your dev server too: npx impeccable detect http://localhost:5173.

Before you turn on hooks and live mode

Hooks run outside model approval.

In Claude Code, installed command hooks run even when you deny the model’s own commands, so the first edit can download the engine. — Impeccable README

The README’s advice is to review installed hooks before unattended runs, or pass --settings '{"disableAllHooks": true}' to turn them off for one run. How hooks load and run in Claude Code is covered in Claude Code hooks.

/impeccable live opens your running dev server with an overlay and writes accepted variants back to your source. The README says live mode edits a local checkout only and warns not to inject it into a deployed site or weaken a production CSP. Its Apply button sends staged copy edits to your chat agent; if no session has polled in the last minute, it runs the codex CLI from your PATH (or claude when codex is missing) “with approvals, permission checks, and sandboxing off” (--dangerously-bypass-approvals-and-sandbox or --permission-mode bypassPermissions) and your environment inherited. The safer settings the README documents:

IMPECCABLE_LIVE_COPY_AGENT=chat   # keep Apply in your chat session
IMPECCABLE_LIVE_COPY_AGENT=off    # disable Apply

Set it in the environment that starts live mode; the server reads it once at startup. Applying copy edits also runs your package.json’s optional impeccable:manual-edit-validate script with your permissions, so the README says to review it in an unfamiliar repo. What those bypass flags do is explained in claude --dangerously-skip-permissions and Codex: dangerously skip permissions.

Telemetry. When a new design starts, the skill fetches visual directions from the impeccable.style catalog. Turning telemetry off doesn’t stop that request; it stops the anonymous record of which directions were shown and picked. The README says project names, files, code and PRODUCT.md are never sent. Turn it off with npx impeccable telemetry off, DO_NOT_TRACK=1, or "telemetry": false in .impeccable/config.json (privacy page).

Impeccable keeps its working files in .impeccable/. The README says config.json, live/config.json, design.json, surfaces/*.md and critique/*.md belong in the repo along with PRODUCT.md and DESIGN.md, and gives a .gitignore block for the rest.

Questions

How do I install the Impeccable skill in Claude Code?
Run npx impeccable install from the project root, accept the design hook if you want automatic checks, and reload Claude Code. As a plugin instead, run /plugin marketplace add pbakaus/impeccable, then install Impeccable from /plugin. Then run /impeccable init once in the project.
Does Impeccable work in Codex?
Yes. The installer covers Codex CLI, and the manual build is in the repository’s .agents/ folder (global folder ~/.agents/skills/). On Codex you open /skills or type $impeccable instead of the slash command, and you approve the project hook in /hooks.
Is Impeccable official?
No. It is not from an agent vendor: Paul Bakaus publishes it in his own GitHub repository under Apache 2.0. It grew from Anthropic’s frontend-design skill.
How is it different from Anthropic’s frontend-design skill?
The frontend-design skill is one set of design instructions. Impeccable adds named commands for single moves (bolder, quieter, polish), scored reviews (critique, audit), the PRODUCT.md and DESIGN.md context files, live browser iteration, and the 62-rule detector with its edit hook and CLI.
Can I run the detector without an agent?
Yes. npx impeccable detect src/ scans files, npx impeccable detect --github src/ writes GitHub Actions annotations, and exit code 2 means findings, so it can fail a CI step.

Sources

Checked November 13, 2026.

Design & frontend

View all
Aftergradient

What are you looking for?

Search commands, errors, tools