Impeccable Skill: 24 Design Commands and a 62-Rule Slop Detector

pbakaus/impeccable gives a coding agent a design vocabulary: /impeccable plus 24 commands, a 62-rule detector that runs as a hook, a CLI or a Chrome extension, the Claude Code and DeepSeek Harness install lines, and the community dsh port that drops the engine binary.

Last updated: 2026-11-19

Quick answer

impeccable is a design skill for coding agents: a vocabulary of commands that tells an agent which design move you want, plus a detector that names the tells of AI-generated UI. The repository summary is one sentence: "The design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, and catch AI slop before it ships."

Three parts make up the thing people install:

  • /impeccable — the entry command. Type it alone and the agent prints the command list.
  • 24 commands behind it: 23 named playbooks, plus craft, which the README describes as "a deprecated alias for a plain build request."
  • 62 deterministic rules in the slop detector — "No LLM, no API key", per the README.

It is by Paul Bakaus, licensed Apache-2.0, and the README says it "started from Anthropic's frontend-design skill." At the GitHub API snapshot of 2026-11-19 the repository had 112,991 stars and 6,730 forks, created 2025-11-16 and last pushed 2026-11-18. Those are snapshot numbers, not fixed values.

Everything below was read on 2026-11-19; commands are copied verbatim from the README and the port's files. If you want a one-screen UI rewrite rather than a command vocabulary, the unslop skill is the closer match.

The 24 commands

The README heads the table "### 24 commands" and groups them by what you are doing. Command names are verbatim:

GroupCommands
Steerbolder, quieter, distill, colorize, typeset, layout, animate, delight, overdrive
Reviewcritique (a scored UX review), audit (a technical quality report)
Finishpolish, harden, clarify, adapt, optimize, onboard
Iterate livelive, generate
Plan and set upshape, init, document, extract

That is 23 named playbooks. The README adds the twenty-fourth in the next line: "The 24th, craft, is a deprecated alias for a plain build request." Each command has its own page at impeccable.style/docs.

The two setup commands are the ones to run first, because everything else reads their output. init writes PRODUCT.md — the README says it "reads your code, asks only what it can't infer (who the product is for, what it needs to do, the constraints)". document captures your existing visual system in DESIGN.md "so changes stay on-brand". Working files live under .impeccable/ in the project.

Commands take a target, and narrow targets win: /impeccable critique the onboarding flow, /impeccable quieter the landing page, /impeccable polish settings, /impeccable harden checkout. On Codex you open /skills or type $impeccable instead of the slash command. /impeccable pin audit gives a command its own shortcut (/audit); the README lists pinning, and the dsh port drops it (see below).

live is the browser loop: it "opens your running dev server with an overlay. Select an element, pick a direction, and Impeccable hot-swaps variants in place." The README says it works with Vite, Next, SvelteKit, Astro, Nuxt and plain HTML, and that it edits a local checkout only.

The detector: 62 rules, three ways to run it

The README's own description: "A slop detector. 62 deterministic rules flag the tells above, plus quality problems like cramped padding and skipped headings. No LLM, no API key." The slop page states the same count: "The catalog includes 62 detector rules and 6 patterns for design review."

In your agent. The design hook "scans every UI file your agent edits and hands the findings back before the agent calls the work done". The README is explicit about the coverage: "It's available on Claude Code, Cursor, Codex, GitHub Copilot, Grok Build, and Hermes Agent, and the installer sets it up." dsh is not on that list — see the DeepSeek Harness section below.

In CI or your terminal. The CLI needs no agent:

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 --sarif src/           # SARIF 2.1.0 for code scanning
npx impeccable detect --list-rules           # every rule with its id and description
npx impeccable detect --report-unused-ignores src/  # inline ignores that waive nothing

Source files like 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 — so point the CLI at your dev server too: npx impeccable detect http://localhost:5173.

Exit code 0 is a clean scan, 2 means findings, 1 means a target couldn't be scanned. Rule ids are the handles you work with afterwards — overused-font and gradient-text are the two the detector docs use as findings. Two ways to silence one:

npx impeccable ignores add-value overused-font Inter --reason "Brand font"
<!-- impeccable-disable overused-font: exported brand doc -->

The first allows a brand font everywhere, the second turns a rule off for one file.

In your browser. The Chrome extension "overlays the same findings on any live page, yours or anyone else's".

Install it

From your project root:

npx impeccable install

The installer detects your coding tools, asks whether to install for this project or globally, and offers the design hook where your tool supports one. npx impeccable update refreshes an existing install. For scripts, pass --providers=claude,codex,cursor and --scope=project|global.

Three tools need one more step before the hook runs, per the README: in Codex open /hooks and approve the project hook; in Grok Build run /hooks-trust or launch with --trust; in Hermes Agent run hermes plugins enable impeccable-design-hook once.

Claude Code has a plugin route as well: /plugin marketplace add pbakaus/impeccable, then open /plugin and install Impeccable. After installing, reload your tool and run /impeccable init in your agent ($impeccable init on Codex). A team-wide pinned copy is possible too: git submodule add the repo and run npx impeccable link --source=vendor/impeccable --providers=claude,cursor — linking installs skills, not hooks.

No Node? The README ships a manual-copy table instead, and DeepSeek Harness is a row in it:

ToolRepo folderGlobal skills folder
DeepSeek Harness.dsh/${DSH_HOME:-$HOME/.dsh}/skills/

So the copy is skills/impeccable into .dsh/skills/ in the project, or into the global folder. The upstream repository does commit a .dsh/skills/impeccable/ folder at its main tree — SKILL.md, reference/ (50 markdown files) and scripts/ (the launcher plus the live-browser-*.js files and a font index) — which is what you would copy.

One footnote from the same table matters on dsh: "impeccable install and update manage a DeepSeek Harness global copy only when DSH_HOME is inside your home directory." If your DSH_HOME points somewhere else, do the copy yourself.

Node is only needed for npx. The skill itself runs "a self-contained engine binary that ships next to it or downloads once into ~/.impeccable/bin/" — that binary is the reason a manual copy is not a full install: "A manual copy skips the design hook and subagents."

Using it with DeepSeek Harness

Read these two facts together, because they are the whole dsh story:

  1. DeepSeek Harness is officially supported. The README's support line reads, verbatim: "Works with 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." The manual-copy table has a dsh row, and the repo ships a .dsh/skills/impeccable/ folder.
  2. The automatic post-edit hook is not available on dsh. The hook covers Claude Code, Cursor, Codex, GitHub Copilot, Grok Build and Hermes Agent only. On dsh, detection is a command you run: npx impeccable detect src/, or point it at your dev server for the rendered-page rules.

That is the practical difference between "supported" and "fully wired". The commands, the reference files and the context files (PRODUCT.md, DESIGN.md) work the same; the safety net that fires after every edit does not. If you install it by hand, the install-skills walkthrough covers the .dsh/skills/ layout, and what a skill is explains the folder shape the copy relies on.

The community dsh port

Because the upstream skill wants an engine binary, someone packaged a dsh-native edition: kechao-sgp/dsh-impeccable-skill. It is a community port, not an upstream or DeepSeek release — its NOTICE says it is "not published, endorsed, or supported by the upstream author".

What it actually ships, from the repository:

  • A bundled impeccable skill. index.js reads the packaged skill/SKILL.md once and registers it (source: bundled). It uses Node built-ins only: no file writes, no subprocesses, no tools or slash commands registered. package.json declares dsh.capabilities: ["fs:read"].
  • 23 playbooks in the README table, 24 in the command table. The README's playbook table groups 23 named playbooks (plan, review, polish, enhance, fix, iterate); the skill's own command table adds craft as "Deprecated alias for an ordinary new-work request", which is where the 24 comes from. skill/reference/ holds 46 .md files (4 under degraded/, 2 *.native.md, 3 mode-*.md), plus craft-floor.md, new-work.md, region-map.md, routing.md and dsh-runtime.md.
  • No engine binary. The README's reason, verbatim: "本移植版不打包该二进制:来源不可审计、体积与本插件定位不符。" Instead, skill/reference/dsh-runtime.md maps every engine verb onto a native dsh action: impeccable context becomes reading PRODUCT.md / DESIGN.md / .impeccable/; detect becomes a manual sweep (craft-floor bans, grep, reading the context line by line); generate-image becomes dsh's generate_image; screenshots become the playwright skill, a committed visual baseline or a user screenshot; comp-spec becomes a hand-written regions.json with the dimensions marked as estimates; font-match becomes the closest available font, declared an estimate; live becomes static variant files plus screenshots for the user to pick from; hooks become nothing.
  • Three documented limits. SKILL.md has an "Edition limits" section: Pin/Unpin is unavailable; hooks do not run, so after its own edits the model runs the anti-pattern pass by hand and says so; Doctor has no automated repair, so it walks doctor.md manually.
  • Three install routes. From the repository (the package declares dsh.bundle, so the repo URL goes into plugin management) — the README marks this one available now; from a local directory, for development; and from the marketplace, which the README marks as pending. The npm package dsh-impeccable-skill is not published: https://registry.npmjs.org/dsh-impeccable-skill returned HTTP 404 on 2026-11-19, which matches the README.
  • A name clash. npm already has a different dsh-impeccable from Cassius0924 (latest 0.1.2, published 2026-10-31, described as 23 design playbooks) with a client workbench and a detector. The port's README warns that both register the same skill name: "两者都注册同名技能 impeccable,不要同时安装(同层同名先到先得,后装的不生效)。"

Licensing: the skill text and skill/reference/ come from pbakaus/impeccable under Apache-2.0; reference/ios.md and reference/android.md come from ehmo/platform-design-skills under MIT. The port packages upstream skill version 4.8.0, "re-checked against the repository on 2026-11-07" — upstream's own .dsh SKILL.md was at version: 4.10.0 when read on 2026-11-19, so the port trails the upstream skill content.

Directory facts, since they decide whether you can read more here: kechao-sgp/dsh-impeccable-skill is in this site's catalog as a curated entry in ecosystem & resources, with 0 stars and 0 forks at the 2026-11-19 snapshot, created and last pushed 2026-11-07. It has no dedicated detail page on this site yet, so the catalog links above are the way in: the directory search for "impeccable". One of the other hits, zc7hyz/dsh-taste, describes its own scanner in its README as "25 条设计方法论 + 61 条确定性反模式扫描器" — that is that project's own count for its own tool, not the upstream 62-rule catalog.

Impeccable vs unslop

Both are design skills, and they are not interchangeable. The short split:

  • Impeccable is a vocabulary plus a detector plus context files: 24 commands to aim the agent, 62 rules to check the result, PRODUCT.md and DESIGN.md to keep it on-brand across sessions. It is strongest on interfaces that already exist — "point it at a page or a component and iterate", per the README.
  • The unslop skill is a single playbook for one screen: it lists the slop, proposes a direction from your product, then fixes the screen in ordered passes, and it can record a short video of the result.

If you want repeatable command words and a CI-checkable detector, take Impeccable. If you want one vibecoded page redesigned end to end, take unslop. The two can coexist — they are separate skills with separate names — but running both on the same screen in one session mostly duplicates work. For the wider field, see the best dsh skills and pstack skills.

When it is the wrong tool

  • You want the copy rewritten, not the interface. Impeccable has clarify for unclear copy inside a UI, but prose de-slopping is a different job — see humanizer skills.
  • You want a security or correctness audit. audit is a design-quality report: accessibility, performance, theming, responsive behaviour. It is not a code audit.
  • You are on dsh and expect the hook. The detector will not fire by itself there. Budget the npx impeccable detect run, or accept that nothing checks the edit.
  • You cannot run the engine binary at all. The upstream skill needs it; a manual copy gives you the skill without the hook and subagents, and the community port gives you playbook text with manual substitutions instead of the engine's measurements.
  • You need pixel-exact measurements. On the port, comp-spec and font-match degrade to declared estimates. If exact numbers matter, that is not the tool.

FAQ

What is the Impeccable skill? It is a design skill for coding agents, built by Paul Bakaus and licensed Apache-2.0. The repository calls it "the design vocabulary for your coding agent": a /impeccable command with 24 commands behind it (23 named playbooks plus craft, a deprecated alias for a plain build request) and a slop detector with 62 deterministic rules that uses no LLM and no API key.

How do I install it in Claude Code? From your project root run npx impeccable install. The installer detects your coding tools, asks whether the install is for this project or global, and offers the design hook. Or add it as a plugin: /plugin marketplace add pbakaus/impeccable, then open /plugin and install Impeccable. Reload the tool, then run /impeccable init in your agent. npx impeccable update refreshes an existing install.

Does Impeccable work in DeepSeek Harness? DeepSeek Harness is in the README support list, and the manual-copy table gives dsh two folders: .dsh/ in the repository and ${DSH_HOME:-$HOME/.dsh}/skills/ globally. What does not carry over is the automatic post-edit hook: it is available on Claude Code, Cursor, Codex, GitHub Copilot, Grok Build and Hermes Agent, and dsh is not on that list, so on dsh you run npx impeccable detect yourself.

How do I run the 62 rules? Three ways. In the agent, the design hook scans every UI file it edits. In CI or a terminal, npx impeccable detect src/ scans a directory, npx impeccable detect https://example.com scans a rendered page, and --json, --github, --sarif, --list-rules and --report-unused-ignores change the output. In the browser, the Chrome extension overlays the same findings on any live page. Exit code 2 means findings, 1 means a target could not be scanned, 0 means a clean scan.

Is there a DeepSeek Harness port? Yes, a community one: kechao-sgp/dsh-impeccable-skill packages the playbooks and 46 reference files as a bundled impeccable skill with no engine binary, and ships a dsh-runtime.md that maps each engine command onto a native dsh action. It is Apache-2.0, it is not an upstream or dsh-official release, it had 0 stars and 0 forks at the 2026-11-19 snapshot, and its npm package is not published — the registry returns 404. It registers the same skill name as the separate dsh-impeccable package, so do not install both.

Sources

Every claim above comes from these pages, read on 2026-11-19:

  • github.com/pbakaus/impeccable — README: the one-sentence summary, the support list naming DeepSeek Harness, the "### 24 commands" table and the craft deprecated alias, the 62-rule detector sentence, the hook coverage list and its extra approval steps, the seven detect invocations, the exit codes, the ignores and impeccable-disable forms, the install and update commands with --providers and --scope, the Claude Code /plugin marketplace add route, the submodule route, the manual-copy table with the .dsh/ and ${DSH_HOME:-$HOME/.dsh}/skills/ rows, the DSH_HOME footnote, the "Node is only needed for npx" and ~/.impeccable/bin/ note, the "manual copy skips the design hook and subagents" note, the live-mode paragraph, the .impeccable/ project files and the licence line ("Apache 2.0. See LICENSE. Impeccable started from Anthropic's frontend-design skill."). Repository tree read 2026-11-19: .dsh/skills/impeccable/ holds SKILL.md (version: 4.10.0), 50 reference markdown files and a scripts/ folder with the launcher, the live-browser-*.js files and a font index. GitHub API snapshot 2026-11-19: Apache-2.0, 112,991 stars, 6,730 forks, created 2025-11-16, pushed 2026-11-18 (a snapshot, not a fixed number).
  • impeccable.style/slop — "The catalog includes 62 detector rules and 6 patterns for design review."
  • impeccable.style/docs/detector — the exit-code table (0 / 2 / 1), the overused-font and gradient-text findings, and the rule ids used in the ignore examples.
  • github.com/kechao-sgp/dsh-impeccable-skill — README, NOTICE.md, skill/SKILL.md and index.js: the bundled impeccable skill and its index.js behaviour, the 23-playbook table plus the craft alias row, the dsh-runtime.md command mapping, the "Edition limits" section, the three install routes, the dsh-impeccable name clash, the Apache-2.0 / MIT split, the packaged upstream version 4.8.0, and the "not published, endorsed, or supported" line. Repository tree read 2026-11-19: 46 .md files under skill/reference/ (4 in degraded/, 2 *.native.md, 3 mode-*.md). GitHub API snapshot 2026-11-19: Apache-2.0, 0 stars, 0 forks, created 2026-11-07, pushed 2026-11-07.
  • registry.npmjs.org/dsh-impeccable-skill — HTTP 404 on 2026-11-19, matching the README's "npm 包 dsh-impeccable-skill 尚未发布".
  • registry.npmjs.org/dsh-impeccable — the separate Cassius0924 package: latest 0.1.2, published 2026-10-31.

Impeccable is an open-source project by Paul Bakaus; the dsh port is a community package. Neither is a DeepSeek product, and neither is affiliated with this site. Commands come from the README at the date shown — this repository pushed on the day of this reading, so re-check before you run one.

Related reading: the unslop skill, installing skills, what a skill is, the best DeepSeek Harness skills, pstack skills.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.