Skip to content
UI Aesthetics

Impeccable

Tool coverage — filled cells are supported. Full names under “Works with” below.

A design director you invoke by verb — shape, critique, bolder, quieter, distill, harden — each command a separate playbook, loaded only when the work actually calls for it.

The largest design skill in circulation, and the one with the most opinionated theory of its own use. Where most skills are a single document you either load or don’t, Impeccable is a hub plus roughly forty reference playbooks, and the hub’s real job is deciding which one applies before any editing starts.

The command table is the interface: shape plans UX before code exists, critique runs a heuristic design review, audit runs the technical checks, polish is the pre-ship pass, and then the pair worth the price of admission — bolder for work that came out safe, quieter for work that came out loud. Naming those as separate operations is a real insight. Most design feedback fails because “make it better” points in two opposite directions and the agent picks the one requiring less nerve.

Its second good idea is modes, chosen from the surface rather than the product: Persuade (the visitor decides and acts), Operate (the visitor completes a task), Read (the visitor understands something), Experience (the visitor is inside the work). The rule that makes it useful is the counter-example attached to it — a tool’s landing page is still Persuade, a fashion house’s documentation is still Read. That stops the mode collapsing into a description of the company.

Watch for: it explicitly gives itself permission to be maximalist — “go all out, no hedging” — which is right for a portfolio piece and wrong for a settings screen. The Operate mode exists to counterweight that, so name your surface precisely or you’ll get expressiveness where you wanted restraint.

The verification budget is unusually well specified: build fully, inspect once in a batched round covering desktop and mobile together, fix everything that round shows, confirm with at most one more, stop. Bounded passes rather than an open loop, with the stated reason that open-ended self-QA burns the user’s money doing worse what a dedicated review pass does better.

Gotcha: it wants node scripts/context.mjs run once per session before it does anything, and it maintains its own PRODUCT.md and DESIGN.md. This is the most infrastructure-shaped skill in the gallery — closer to a framework you adopt than a file you drop in.

Apache-2.0, versioned (4.1.1 at the time of writing), and packaged for around twenty different agent harnesses.

File & content map

SKILL.md

Impeccable

A design director you invoke by verb — shape, critique, bolder, quieter, distill, harden — each command a separate playbook, loaded only when the work actually calls for it.

Contents — 4 sections

Setup
How to design
Modes
Commands

Package — 2 folders

content section file folder