Impeccable
The missing design vocabulary for coding agents
About Impeccable
Impeccable is a command set you install into a coding agent to give it design vocabulary. Ask an agent to build an interface and you tend to get the same thing every time: an italic serif headline over a beige palette, a hairline border under a wide soft shadow, a pulsing status dot, cards nested inside cards. Impeccable exists to name that problem and fix it. One command installs about two dozen commands across six groups - create, evaluate, refine, simplify, harden and system - so instead of describing the look you want in prose, you say polish, typeset, layout, distill, clarify, critique or audit, and the agent knows what that means. It also ships a detector of 62 checks that catches those defaults before they reach your repository, and it reads a project's PRODUCT.md and DESIGN.md so it works inside the design system you already have rather than imposing its author's taste wholesale.
It is Apache-2.0 on GitHub, with roughly 105,000 stars and about 331,000 npm downloads in a week, which is a far harder usage signal than stars. The repository was created in November 2025, so it has a year of history rather than a launch spike, and the GitHub Copilot app now ships it built in. One honest caveat on the evidence: the website itself publishes neither a price nor a licence line and has no pricing page at all. The Apache-2.0 licence comes from the project's own GitHub repository, which is the same author's source and so clears the open-source bar, but the site makes no commitment of its own.
You install it with a single npx command, or through a marketplace, and run the init command in your agent chat so it can record your audience and goals in PRODUCT.md. From then on you work in plain language: describe the outcome you want and the agent brings the design expertise, or reach for a focused command when you already know the kind of change. Ask it to design a new page and it can either mock up a comp first, which opens bolder visual directions at the cost of several rounds translating image into code, or build directly in code, which tends to produce a more coherent first pass with less ambitious visuals. Checks run automatically as the agent edits, giving it detector feedback in the loop, and you can also run a detector scan from the terminal against files or a rendered page. A visual overlay shows findings on the page itself so you decide what to fix. Shared rules go in DESIGN.md, and configuration supports local overrides and detector exceptions.
- •About two dozen focused commands - Grouped into create, evaluate, refine, simplify, harden and system, covering polish, typeset, layout, distill, clarify, critique, audit, animate, harden, onboard, optimize, extract and more
- •A 62-check slop detector - Catches the visual defaults models keep reaching for, runnable as a scan or fed to the agent automatically while it edits
- •Works inside your design system - Reads PRODUCT.md and DESIGN.md so it follows your existing rules rather than replacing them
- •Agent-agnostic - Works with Claude Code, Codex CLI, Cursor, Gemini CLI, OpenCode and others, and is built into the GitHub Copilot app
- •Comp-led or code-led workflows - Generate a mockup first for bolder directions, or build straight in code for a more coherent first build
- •Visual review overlay - Findings are shown on the rendered page, with priorities, so you can decide what actually matters
Developers who ship frontend work with an agent and keep having to explain, every single time, why the output looks generated. It pays off most for people without a designer to hand, and for teams trying to hold a design system together across several agents working in parallel. The free and open licence makes it almost costless to try. Two things argue against it. It is a prompt and skill pack rather than software with a runtime, so its whole value depends on the host agent following instructions, and there is nothing stopping anyone copying the rules. And it is opinionated by design: the detector encodes one person's taste, and where yours disagrees it will push back. If you already have a designer reviewing every screen, you are solving a problem you do not have.
Pricing
No pricing page found
Free and Apache-2.0, installed with npx impeccable install. The website publishes no price and no pricing page; the licence is read from the project's own GitHub repository. There is no paid tier.
Checked 2026-11-06
