Impeccable

Impeccable gives coding agents persistent product/design context, a shared design vocabulary, and deterministic anti-slop checks instead of relying on one giant aesthetic prompt.

Routing Summary

Start with Kevin's installed routes: taste, design-engineering-polish, frontend-design, and web-design-engineer. Use Impeccable when a project would benefit from its PRODUCT.md / DESIGN.md setup, command vocabulary, browser/live iteration, or deterministic detector layer. It is currently a reviewed external source, not a silently installed global default. Source: Impeccable README, reviewed 2026-07-14

Why It Matters

Impeccable turns “make it look better” into named operations such as shape, critique, audit, polish, bolder, quieter, distill, harden, animate, typeset, and layout. Its initialization flow records audience, product/brand lane, voice, anti-references, colors, type, and components so later agent passes share the same design model. The project also advertises 46 deterministic detector rules alongside LLM critique checks. Source: Impeccable README, reviewed 2026-07-14

Adoption Boundary

Situation Route
One-off local polish Existing Kevin design skills first
Project needs durable design context Evaluate /impeccable init and generated design files
Repeatable anti-pattern enforcement Evaluate deterministic detectors and hooks
Third-party install requested Inspect source, run skill/security audit, then choose project-local before global

Current Snapshot

As checked on 2026-07-14, the Apache-2.0 repository has roughly 46.5K stars. Its latest GitHub skill release is skill-v3.9.1 from 2026-07-01, while the impeccable npm installer reports version 3.2.1, updated 2026-07-09. Keep those version streams distinct. The README documents npx impeccable install and npx impeccable update, with provider selection for Claude, Codex, Cursor, Gemini, and other harnesses. Source: GitHub and npm APIs; Impeccable README, checked 2026-07-14


Timeline