Impeccable is a free, open-source design skill for AI coding agents — and, more usefully for most of us, it ships a small command-line detector that scans a web page and flags the visual tells that make a site look AI-generated: purple gradients, Inter everywhere, nested cards, grey text on colour, eyebrow labels. No model, no API key, no account. We ran the detector on November 17, 2026, on three pages of our own — one deliberately sloppy, one deliberately clean, and our own homepage — and every number below is what the tool actually reported.
Impeccable (pbakaus/impeccable on GitHub) is a design skill for AI coding agents: 24 named commands such as /impeccable polish, /impeccable bolder, /impeccable critique and /impeccable audit that teach a coding agent design taste. Alongside the skill it ships a deterministic detector — a small CLI that reads a page's HTML and CSS and flags AI-design tells with fixed rules, no LLM and no API key involved.
The numbers behind the surge: 111,487 GitHub stars, up 3,907 in the last 7 days as of November 17, 2026, and a place on GitHub's weekly trending list. (For scale, it stood at about 96,134 stars on October 30 — roughly 15,000 stars in 18 days.) The version we tested is CLI 4.9.2; reviews from late October 2026 cite 4.8.0, so this is a newer build than the ones most write-ups describe. For anyone who builds websites — designers, small shops, creators — a free tool that spots "this looks AI-made" before your visitors do is genuinely useful. That is exactly the audience we tested it for, and this tutorial covers only the free detector path: the 24 skill commands need a paid coding agent (Claude Code, Cursor, Codex and similar), which we did not test.
Requirements: Node 18 or newer. Nothing else — no account, no login, no API key for the detector. Our test ran on November 17, 2026, on Ubuntu 24.04 with Node v24.22.1 and npm 10.9.4. The package comes from the official npm registry; we checked the name character by character against the project's README (pbakaus/impeccable → npm package impeccable), and the registry confirms the licence is Apache-2.0.
Step 1 — Check the version. No install step is needed; npx fetches and runs it. First download and run took about 7.5 seconds.
npx impeccable --version # 4.9.2
Step 2 — See what it can do.
npx impeccable --help
The command list includes detect, ignores, install, link, update, check, telemetry, login, logout, whoami, status, walkthrough, world, health and foundations. The only command this tutorial uses is detect (plus ignores in section 3) — install, link and update rewrite your agent's configuration, so we did not run them, and login is only needed for Pro rules, which we did not test.
Step 3 — Run the detector on a page.
npx impeccable detect your-page.html
That is the whole free workflow: point it at an HTML file and read the findings. Cost: $0.
Important scope note: the 24 skill commands (/impeccable polish, /impeccable critique, /impeccable audit…) only run inside a paid coding agent, and we did not test them. This tutorial covers only the free detector path, and the skill side is described from the project's documentation, not presented as tested.
Target: prove — on our own files, with answers we could check in advance — that the detector really finds AI-design tells, really passes a clean page, and says something useful about a real site. All three test pages are our own files; no third-party commercial software was analysed.
We built slop.html deliberately full of AI clichés: Inter font, a purple-to-blue gradient hero, grey text on a coloured background, an eyebrow label chip, cards nested three layers deep, emoji icon titles, and marketing buzzwords ("supercharge", "cutting-edge", "enterprise-grade").
npx impeccable detect slop.html # 7 anti-patterns found.
The 7 findings hit 5 of the traps we planted: low-contrast ×3 (2.4:1, 3.0:1 and 4.1:1 — all below the 4.5:1 bar), hero-eyebrow-chip, overused-font (Inter), ai-color-palette (the purple gradient) and marketing-buzzword ×3 (the output truncates the match as "ure of Work Supercharge your workflow wi"). Exit code 2 — findings present.
Honestly recorded, it missed two traps: the three-layer nested cards were not flagged (the nested-cards rule did not trigger this time), and the emoji icon titles were not listed separately. The detector is not all-seeing — keep that in mind when you use it.
clean.html was the opposite: a Georgia serif font, solid colours, no gradient text, no buzzwords, no nested cards.
npx impeccable detect clean.html # (no output at all) — exit code 0
Zero findings, exit code 0. One thing that will confuse newcomers: with 0 findings there is no "passed" summary line — the output is literally empty. That is normal. Empty output plus exit code 0 is the pass signal, not a sign the command failed.
Then the real test: our own homepage, index.html, scanned where it lives so the detector could read its linked style.css and motion.css.
npx impeccable detect index.html # 25 anti-patterns found. # 6 advisory notes.
| What we checked | Result |
|---|---|
| Sloppy test page (slop.html) | 7 findings, exit code 2. low-contrast ×3 (2.4:1, 3.0:1, 4.1:1), hero-eyebrow-chip, overused-font (Inter), ai-color-palette (purple gradient), marketing-buzzword ×3. |
| Clean control page (clean.html) | 0 findings, exit code 0. Empty output — that is the pass signal. |
| Our homepage (index.html, in place) | 25 anti-patterns + 6 advisories, exit code 2. See the breakdown below. |
| Ignoring a rule (ignores add-value) | Passed. Adding overused-font inter to the ignore list took slop.html from 7 findings to 6; the rest were unchanged. |
| Cost, account, API key | Passed. $0, no account, no login, no API key for the detector at any point. |
The homepage breakdown, in the detector's own terms: low-contrast ×10 (including white text on #ebc9b7 at 1.5:1 and 1.4:1 in our call-to-action band), gradient-text ×2, kicker-above-heading ×3, overused-font ×2 (Fraunces and Inter), wide-tracking ×2, undersized-ui-text ×3 ("Free Tool" / "Free to Try" at 10.88px, below the 11px floor), cramped-padding, cream-palette, skipped-heading (an h1 followed directly by an h3), and a marquee. The 6 advisories add low-contrast ×3 (4.2–4.4:1, just under the bar), tiny-text (11.52px body text), repeating-stripes-gradient and em-dash-overuse (14 em dashes).
Our honest read of that list: most of the low-contrast items are real problems and worth fixing. But Fraunces and Inter are fonts we chose on purpose, the cream background and the marquee are deliberate brand choices — and the detector flags them anyway. That is the difference between a taste rule and a law, and it is the subject of section 4.
One trap we hit ourselves — run it in place. Our first homepage scan copied the file to /tmp and ran it there. The detector could not read the linked stylesheets ("could not read linked stylesheet"), and the results were wrong: it falsely reported a flat type hierarchy with everything at 16px, and only 3 findings. Run detect in the folder where the page and its CSS actually live, or the results will mislead you.
Inter is our brand font, so we told the detector to stop flagging it:
npx impeccable ignores add-value overused-font inter --reason "brand font test" # Added overused-font=inter to shared detector ignoreValues (.impeccable/config.json).
Re-scanning slop.html then reported 6 anti-patterns — the overused-font finding was gone, everything else unchanged. The setting is written to .impeccable/config.json in the project, so it can be committed and shared with a team (there is also a --local option that writes config.local.json instead).
Our verdict: the free detector is real, reproducible and useful — it caught the traps we planted, passed the clean page, and found genuine contrast problems on our own homepage. It is a taste checker with blind spots, not an oracle, but for $0 and one command it earns its place before you publish.
detect in place./impeccable commands need a paid coding agent and were not run in this test. The install, link and update commands were not run either (they rewrite agent configuration), and neither were login or the Pro rules.impeccable, matching the pbakaus/impeccable README. Check the name character by character — lookalike packages are a real risk with popular tools. It needs no install beyond npx.telemetry: on. The project's own privacy text says roll requests and choice pings carry only a seed key, scope, mode, round, pool revision, card kind, catalog id and client version — "never your project's names or code". To switch it off: impeccable telemetry off, or set DO_NOT_TRACK=1, or set IMPECCABLE_NO_TELEMETRY=1. Full details at impeccable.style/privacy.npx impeccable detect into a build check so a page with new AI-design tells fails the build.Yes — that is the whole point of this tutorial. The detector runs with npx impeccable detect your-page.html: no agent, no account, no API key, $0. The 24 skill commands (/impeccable polish, /impeccable critique…) are the part that needs a paid coding agent such as Claude Code, Cursor or Codex. If you only want a design check on your pages, the free detector is all you need.
First decide whether the flag is right or a deliberate choice. Inter is flagged because it is overused across AI-generated sites — but if it is your brand font, that is a decision, not a mistake. Tell the detector to stop flagging it, exactly as we did in our test:
npx impeccable ignores add-value overused-font inter --reason "brand font"
Our slop page went from 7 findings to 6, and the setting is saved in .impeccable/config.json so your team shares it. Do the same for any other deliberate brand choice the detector disagrees with — but fix the real contrast problems first.
They are different kinds of tool. Impeccable is the only one of the three with a free, standalone detector you can run with npx and no paid agent — that is what we tested here. Anthropic's frontend-design and UI/UX Pro Max are agent skills: they live inside a coding agent and only work if you already pay for one. If you want a quick, free check on a page, start with Impeccable's detector. If you already pay for Claude Code and want the agent to redesign a page for you, an agent skill is the better fit — and Impeccable's own 24 commands are its version of that.
Note: this answer is from the project's documentation, not from a hands-on test — we did not test the agent side. Check, in order: (1) that the skill is actually installed in your agent's skills directory (impeccable install is the command that sets it up); (2) that you restarted the agent after installing, so it picks up the new skill; (3) that you invoke it explicitly, e.g. /impeccable polish, rather than hoping the agent discovers it on its own; (4) run impeccable status and impeccable health to see whether the CLI itself is healthy. If the detector works from the command line but the agent ignores the skill, the problem is on the agent side, not the tool.
No. The contrast findings are real accessibility problems (WCAG AA, 4.5:1) and worth fixing — our homepage's 1.5:1 white-on-peach text genuinely needs work. The taste findings (your font, your cream background, your marquee) are the detector's opinion: if a choice is deliberate and on-brand, keep it and add it to the ignore list, as we did with Inter. Fix what is broken, ignore what is intentional, and re-run to confirm the count drops.
No, according to the project's own privacy text: telemetry sends only a seed key, scope, mode, round, pool revision, card kind, catalog id and client version — "never your project's names or code". It is on by default (our check showed telemetry: on), and you can turn it off with impeccable telemetry off, or with DO_NOT_TRACK=1 or IMPECCABLE_NO_TELEMETRY=1.
A detector can flag problems, but fixing them — contrast, type, spacing, layout — is design work, and it is the kind of work we do: see our free tools (including a contrast checker you can run in your browser) and our AI Business Pack — a bilingual website with 24/7 AI customer service, AI product images and a business email, from C$699. If your site needs a human eye after the detector's report, talk to us.
We can put your design on T-shirts, hoodies, mugs, posters and more — printed to order in Quebec, no minimums, with a free preview before you pay.
Contact us for a free quote