impeccableby Paul Bakaus

Impeccable Skill.

A Claude Code and Codex skill for design review: one skill to design, critique, audit, polish, animate, and refine interfaces.

Design Review & Accessibility
UI code

Download OpenDesign View usage guide

pbakaus/impeccable · plugin/skills/impeccable/SKILL.mdSKILL.md

--- name: impeccable description: Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, … --- ## Setup ## How to design ## Modes ## Commands

Front matter and section headings read from the upstream file on 2026-09-14 · 11,912 characters in full

01 What it does

What the impeccable Skill Does in Claude Code and Codex

Summary, workflow and outputs, all read from the skill's SKILL.md.

From the SKILL.mdRead 2026-09-14 · not a recorded run

In the Skill's Own Terms

Impeccable transforms frontend interfaces through design, critique, audit, polish, animation, and refinement. It covers websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, and empty states—handling UX review, visual hierarchy, accessibility, performance, responsive behavior, theming, typography, spacing, layout, color, motion, micro-interactions, and design systems.

The skill delivers out-of-distribution craft through production-grade code, peak creativity, a clear POV, and exceptional craft. It organizes work around four modes—Persuade, Operate, Read, Experience—and over twenty specialized commands. Each session loads product context, visual world, and surface briefs via a launcher script, then follows command-specific playbooks and a craft quality floor.

What it produces

PRODUCT.md capturing durable product context via the init command
DESIGN.md generated from existing project code via the document command
Reusable tokens and components pulled into design system via the extract command
Production-grade UI code with complete deliverables, peak creativity, and exceptional craft

See the example prompt ↗

How It Works

01
Load Session Context Once
Run the impeccable script with context argument once per session from the skill directory.
02
Load the Request's Playbook
For explicit or implied sub-commands, load the Commands table reference; for new surfaces or replacement visual worlds, load new-work.md.
03
Read Craft Floor Before Editing
After resolving analysis and direction, read craft-floor.md immediately before any UI edit, including small refinements.
04
Choose Mode from Surface Type
Select Persuade for landing pages and marketing where visitors decide and act. Choose Operate for app UI and dashboards where visitors complete tasks.
05
Verify in Bounded Passes
Build fully, inspect once with a batched round covering desktop and mobile together on web or shipped device classes on native.

02 Find your fit

When to Use the impeccable Skill

Use the impeccable skill in Claude Code or Codex when the job is design review of this kind. Fit and limits below are taken from the skill's own file.

Good Fit

User wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface
Bland designs that need to become bolder or more delightful
Loud designs that should become quieter
Live browser iteration on UI elements
Ambitious visual effects that should feel technically extraordinary

Know the Boundaries

Backend-only tasks

What to Provide

Target file or routePass a named source file or route using the --target flag with a path argument when running the context script.
PRODUCT.mdDurable product context file loaded by the launcher. When launcher fails, read the existing file directly without inventing missing context.
Visual-regression goldens or screenshot fixturesWhen the app cannot run, start with committed visual-regression goldens or screenshot fixtures.

03 Inside the skill

Rules the impeccable Skill Gives Claude Code and Codex

6 concrete instructions, defaults and limits the SKILL.md sets for the agent — the part of the file that changes the result.

The Brief Wins
Honor pinned aesthetics, eras, materials, fonts, and palettes even when they conflict with a saturated-pattern warning. Redirecting a clear brief toward your taste is failure.
Refinement Preserves; Redesign Replaces
Refinement keeps the incumbent identity, behavior, copy, and everything outside scope.
Visual Authority Is Evidence, Not a Filename
Missing DESIGN.md alone does not make a project greenfield. The new-work playbook decides whether to preserve, expand, or replace the incumbent world based on visual evidence.
Verify in Bounded Passes, Not a Loop
The ceiling covers the whole cycle: screenshots, defect scans, micro-edits, and rebuilds.
Never Repair Drift as Side Effect
A CONTEXT_STALE directive is reported, not acted on, unless the user explicitly asks. The only exception is findings marked auto, which the next write to that file performs anyway.
Launcher Failure Does Not Block Work
On script refusal or failure, send a separate message, then read existing PRODUCT.md and DESIGN.md directly without inventing missing context.

04 Put it to work

Install impeccable in Claude Code or Codex

One npx skills add command, then a first task in your agent and a checklist for the result.

Add impeccable to Claude Code, Codex or Your Agent

Run in your project; the installer asks which agent to add it to.

Terminal

npx skills add https://github.com/pbakaus/impeccable --skill impeccable

Generic skills CLI form for plugin/skills/impeccable/SKILL.md; the repository may document its own path.

Give the Skill a First Design Review Task

Written in the skill's own terms; replace the bracketed parts with your material.

Starter prompt

Audit [src/components/SettingsPanel.tsx] for accessibility and responsive behavior, then polish the form layout and typeset the section headings to improve visual hierarchy. The panel should feel confident but scannable for users managing account preferences.

Source: written from the SKILL.md in the skill's own terms.

Check the First Result

What the SKILL.md itself says a correct result looks like:

Confirm with at most one more round, then stop polishing
Run defect scans as part of the bounded verification cycle
Verify target and freshness against current tokens, CSS, components, or assets
Compare theme and variant captures when working with theming systems

In OpenDesign impeccable is bundled: Plugins → Skills, pick it in the top bar.

Download OpenDesign Read the quickstart

05 Open source, traceable

Source, License and Verification

Where this page's facts come from, and when they were last checked.

Author: Paul Bakaus
Repository: github.com/pbakaus/impeccable Branch main
Skill file: plugin/skills/impeccable/SKILL.md Content checksum recorded at verification; commit cb56ed6
License: Apache-2.0 From LICENSE; SKILL.md says “Apache 2.0”.
Repository stars: 67,876 GitHub snapshot taken 2026-09-14 for the whole pbakaus/impeccable repository. Not a rating or usage count for impeccable.
Verified by OpenDesign: 2026-09-14 Source file, path, license text and star count were checked. Bundled in OpenDesign main (checked 2026-08-28); a live run has not been recorded on this page.

Inside the SKILL.md

SetupRun context script once per session, load playbook, read craft floor before editing
How to designBrief wins, refinement preserves identity while redesign replaces, visual authority is evidence not filename
ModesPersuade for landing pages, Operate for dashboards, Read for docs, Experience for portfolios
CommandsTwenty-plus commands organized into Build, Evaluate, Refine, Enhance, Fix, and Iterate categories with reference files

The Skill's Own Description

“Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.”

Front-matter description from SKILL.md. The full file is about 11,912 characters. Read the full file on GitHub.

06 Before you install

Questions About the impeccable Skill

Answers come from the SKILL.md as read on 2026-09-14, not from a recorded run.

Which command should I use for my request?

If no argument is given, read routing.md and present its context-aware menu; never auto-run a command. For explicit or clearly implied requests, load the Commands table reference.

For workflow or command-selection questions, read the Workflow questions section in routing.md. Otherwise treat the request as general design work.

Impeccable

Run impeccable on a Real Design Review Task.

The impeccable skill ships inside OpenDesign. Download the app, pick the skill in Plugins → Skills, paste the prompt above, and read the plan before the result.

Download OpenDesign Browse all skills