Impeccable is a design language for AI coding agents: one installable skill, 24 commands and 61 deterministic detector rules aimed at the frontend work those agents produce. It is for developers who build interfaces with an AI harness and keep noticing that every project arrives wearing the same font, the same gradient and the same nested cards. If you write your own CSS by hand, or your visuals come from a design team that hands you finished specs, this is not built for you.
What it does
The premise is stated plainly in the README: every model was trained on the same SaaS templates, so skipping design guidance gets you the same handful of tells on every project. Inter for everything. Purple-to-blue gradients. Cards nested inside cards. Gray text on colored backgrounds. A rounded-square icon tile floating above every heading.
Impeccable attacks that from two directions. The first is vocabulary: 24 commands that give you and the agent shared words for what you want changed. polish, audit, critique, distill, animate, bolder, quieter, craft and more, each invoked against a target. Instead of describing in a paragraph that a page feels loud, you say quieter.
The second is detection. Sixty-one deterministic rules look for the specific habits above and flag them, with LLM-only critique checks layered on top for the judgments a rule cannot make. The deterministic half is the interesting part: the CLI and the browser extension run those rules with no LLM and no API key at all, which makes them cheap enough to run repeatedly and predictable enough to trust. There is also live browser iteration, so you can keep adjusting a real rendered page rather than guessing from source.
How it works
Setup is a single flow. Running /impeccable init inspects the project, asks only about material gaps it cannot infer, and writes a PRODUCT.md file recording durable product truth: audience, purpose, operating context, constraints, voice and evidence. That file is deliberately separated from anything visual, so later commands do not confuse "who this is for" with "what this should look like."
Visual decisions live elsewhere and are chosen per surface rather than once for the whole repository — visitor mode and visual direction are picked later, when a specific screen is being worked on. An existing visual system, or a new one the agent builds with you, is recorded separately in DESIGN.md. The result is that the agent has two stable reference documents to reason from instead of re-deriving your product from scratch on every prompt.
Everything else runs through one command surface: /impeccable <command> <target> inside your AI coding tool, backed by the JavaScript CLI and the browser extension.
Getting started
From your project root, run npx impeccable install, then run /impeccable init inside your AI coding tool. Start every new project with init before reaching for the other commands, since they depend on the product truth it records. Fuller documentation lives at impeccable.style. The project is Apache-2.0 licensed and written in JavaScript.
When to use it / when not
Reach for it when an agent writes your frontend and the output keeps landing in the same generic place, or when you want an objective check before shipping a page you did not lay out yourself. The no-LLM detector path also makes sense as a routine pass on a codebase where several people are prompting agents and the visual drift is hard to police by eye.
Skip it if you are not using an AI coding agent — the commands live inside the agent and there is nothing to invoke them from. Skip it for backend, CLI or data work, since the rules are about rendered interface. And if your visuals are already locked by a mature design system you must follow exactly, the opinionated commands will fight you, though recording that system in DESIGN.md is the intended way to make them cooperate.
Alternatives
Impeccable started from Anthropic's frontend-design skill, the first widely-used design skill for Claude, and the README says so directly. That skill remains the lighter option: less to install, less to configure, no per-project setup file. Impeccable is what you move to when you want the deterministic rules, the larger command vocabulary and the durable product record.
It is not a CSS framework and not a component library; it does not give you buttons or a grid. It shapes how an agent makes design decisions and then checks the result.
Anyone whose frontend is substantially written by an AI agent should take this seriously, and 70,000 stars since November 2025 suggest many people recognized the problem the moment it was named. The detector rules alone justify a look, because they cost nothing to run and catch things you have stopped noticing. The wider command set asks more of you — an init pass, two maintained files, a habit of using its words instead of your own — and pays back only if you actually build that habit.