daily nerdingHow to use Impeccable

How to use Impeccable

Impeccable is a free design skill for AI coding agents like Claude Code, Codex and Cursor. It stops your agent building the same generic-looking page every time. Everything on this page is typed in your coding tool's chat. No Terminal.

Start here: on the map, pick a new build or a site that's already up, then follow the seven steps. Site already live? Read this part too.

Original sources

pbakaus/impeccable on GitHub github.com Getting started tutorial impeccable.style Paul Bakaus on X x.com

Six things to know

The whole tool in six boxes. Each links to the part of this page that explains it.

01
One skill, one word
Everything starts with /impeccable in your coding tool's chat. 24 commands sit behind it, but plain words work too.
How
02
Install it from the chat
In Claude Code it's a plugin you add with /plugin. Restart, type /impeccable, and it tells you what to do next.
How
03
init comes first
It asks who the product is for and saves the answers in PRODUCT.md. Users on X call this the step that makes the rest work.
How
04
New build: you pick the look
Describe the page. It shows a few complete design directions in your browser; you choose one, ask for more, or steer.
How
05
Site already up: look first
critique and audit only report. Start there, then polish. Your live site doesn't change until you deploy.
How
06
A checker rides along
The design hook checks each page your agent edits for the usual AI tells, and the agent fixes them on the spot.
How

Words on this page

22 terms, in plain words. Read this first if coding agents are new to you.

Skill: A folder of instructions your coding agent loads when a task needs it. Impeccable is one skill.
Coding tool: The app you chat with to write code: Claude Code, Codex, Cursor, Copilot and others. Impeccable's docs call it the harness.
Agent chat: Where you type to your coding tool. Every command on this page goes here.
Slash command: A word starting with / that your coding tool treats as an instruction, like /impeccable.
Plugin: A bundle that adds skills and hooks to Claude Code in one go. You add Impeccable's with /plugin, right in the chat.
PRODUCT.md: The file init writes: who the product is for, what it does, what must not change. No colours or fonts.
DESIGN.md: The file that records the look: colours, type, components. Written by document, or after your first new design is built.
Surface: Impeccable's word for one page, screen or flow you're working on.
Direction: A complete look for a new page: colours, type, layout, feel. You choose between a few.
The picker: A page that opens in your browser with design directions side by side. The docs also call it the decision page.
Mockup first / build directly: Mockup first (comp-led) draws a picture of the page before any code; it needs image generation. Build directly (code-led) skips the picture.
Critique: A design review: is it clear, does it look generic, what to fix first. Changes nothing.
Audit: A technical check: accessibility, speed, dark mode, phones. Changes nothing.
Polish: A final pass that fixes the details and keeps the look you have.
P0 to P3: Audit's severity labels. P0 stops someone finishing the task; P3 is cosmetic.
AI slop: The look every AI build drifts to: Inter everywhere, purple gradients, cards inside cards, gray text on colour.
Detector: Impeccable's built-in checker: 61 fixed rules, no AI. It runs inside critique, audit and the hook; you never call it yourself.
Hook: A check your coding tool runs by itself at set moments. Impeccable's runs the detector after page edits.
Test copy (localhost): Your site running on your own computer, so you can look before anything goes live. Your agent can start it for you.
Deploy: Putting your changes on the live site. Impeccable never does this; you do, the way you already do.
Live mode: Point at part of your test copy in the browser and try versions of it. Not for the live site.
.impeccable folder: Where Impeccable keeps its working files: settings, reports, screenshots. Most of it stays out of git.

Your agent can code. Impeccable gives it taste.

Every AI model learned from the same templates, so left alone they ship the same few tells. Impeccable is a set of design rules, a short setup and a checker that your coding agent follows. It started from Anthropic's frontend-design skill.

Without it · the usual AI tells, from the README

Inter, or the system font, for everything
A purple-to-blue gradient somewhere
Cards nested inside cards
Gray text on a coloured background
A rounded-square icon tile above every heading

With it

PRODUCT.md tells every command who the page is for
You choose the look from a few full directions
The design rules ban the five tells on the left
A checker flags slop the moment it's written
Reviews rank problems so you fix the worst first

Want to see a real one? Impeccable's Neo Mirai case study shows a project before and after.

Three basic uses

A first landing page
Empty folder, one idea. Run init, then: /impeccable design a landing page for my dog-walking business. You get a working page in a look you picked.
New build
Fix a page that feels off
Ask for a critique of the pricing page, read what it says, then polish it and name what must stay.
Site already up
A check before launch
Audit the checkout. It lists what blocks keyboard or phone users, worst first, with the fix for each.
Either

Three advanced uses

Make new pages match
document records your look in DESIGN.md. extract pulls repeated buttons and cards into shared pieces, so the next page fits.
Design system
Try three versions in the browser
Ask it to generate 3 bold variants of the pricing cards. Compare them on your test copy and keep one. live lets you point and pick.
Variations
Let the hook clean as it goes
With /impeccable hooks on, every page edit is checked and the agent fixes what's flagged, round after round, until nothing is left.
Hook

Everything named

What each piece is and whether you need it. Day one, you need the skill and a way to install it.

What your agent followsDay one
The skill: /impeccable
The instructions: 24 commands, the design rules, the things never to do. One skill, so one word to remember.
Docs
How you install itDay one
The Claude Code plugin
Adds the skill and the design hook in one go, from the chat. The skill checks for updates once a day and offers them.
Docs
Background checkerOn by default
The design hook
Runs the checker after your agent edits a page. Comes with the plugin; /impeccable hooks on, off or status.
Docs
Inside the commandsAutomatic
The detector
61 fixed rules for AI tells and basic quality. critique, audit and the hook run it for you. Also a browser extension.
Docs
For mockup firstOptional
Image generation
Your coding tool's own, or an OpenAI API key. Without it, Impeccable builds straight in code, which is fine.
Docs
DocsReference
impeccable.style
Tutorials, one page per command, and a before-and-after case study.
Docs

Works in

Claude Code (plugin), the GitHub Copilot app (built in under Settings → Experimental), VS Code with Copilot (an extension), and Codex, Cursor, Gemini CLI, OpenCode, Pi, Grok Build, Hermes Agent, Kiro and others through Impeccable's installer.

The seven steps

Pick a new build or a site that's already up. Then click any box, or press Start and follow one page from install to the final check. Each step shows what to type, what you'll see, and what someone using it said on X. The dashed box is the hook, which runs by itself the whole time.

First, what are you working on?

A new build · seven steps · all typed in your coding tool's chat

Follow one page: a book club signup

One made-up page, from install to the last check. Press Start and the boxes above light up in order.

A new build

01 · Install it Coding tool
```
/plugin marketplace add pbakaus/impeccable
```
Adds Impeccable's plugin list to Claude Code. Then type /plugin, pick Impeccable and install it (or type /plugin install impeccable@impeccable). The skill and the design hook come together.
02 · Restart and ask what's next Coding tool
```
/impeccable
```
Coding tools load new skills when they start. /impeccable on its own reads your project and suggests the two or three best next commands. On a fresh project, that's init.
03 · Tell it about your project Agent chat
```
/impeccable init
```
Reads your folder first, then asks only what it couldn't find: who uses this, what job they're doing, what must not change. Three questions at most per round. The answers go in PRODUCT.md, which every later command reads.
04 · Describe the page Agent chat
```
/impeccable design a signup page for our monthly book club. Help visitors understand the next event and reserve a seat.
```
Starts the new-design flow. It asks two or three questions, like who must act and what would convince them, then prepares design directions for you.
05 · Choose a direction Browser
The picker shows a few complete directions side by side, each with a preview, its choices and its risks. Press Build this on the one you want. Re-roll for new ones, Safer hand or Bolder hand to shift the range, or type what to change. A plain, familiar option is always there too.
06 · Try it, steer, polish Browser + chat
```
The event card is clear now. Keep that, but make the date bigger and keep the Reserve button visible on phones. Then run /impeccable polish on the signup page.
```
It builds the direction you chose and writes DESIGN.md from what it built, so your next page matches. Your job: open the test copy, do the main task, look at it phone-sized, and say one thing to keep and one to change. Then a polish pass.
07 · Check before you ship Agent chat
```
/impeccable audit the signup page
```
Checks five areas: accessibility, performance, theming, responsive layout and consistency. Each scores 0 to 4, out of 20. Findings are ranked P0 (blocks someone) to P3 (small).
Always · The design hook Background
```
/impeccable hooks status
```
After your agent edits a page or stylesheet, a checker looks for the usual tells (gradient text, glows, gray on colour, tiny tap targets) and tells the agent, which fixes them while the change is fresh.

A site that's already up

01 · Install it Coding tool
```
/plugin marketplace add pbakaus/impeccable
```
Adds Impeccable's plugin list to Claude Code. Then type /plugin, pick Impeccable and install it (or type /plugin install impeccable@impeccable). The skill and the design hook come together.
02 · Restart and ask what's next Coding tool
```
/impeccable
```
Coding tools load new skills when they start. /impeccable on its own reads your project and suggests the two or three best next commands. On a fresh project, that's init.
03 · Tell it about your project Agent chat
```
/impeccable init
```
Reads your folder first, then asks only what it couldn't find: who uses this, what job they're doing, what must not change. Three questions at most per round. The answers go in PRODUCT.md, which every later command reads.
04 · Record the look you have Agent chat
```
/impeccable document
```
Reads your site's code and writes down its colours, fonts and component rules in DESIGN.md, so fixes and new pages match what's already there.
05 · Look before you change Agent chat
```
/impeccable critique the pricing page
```
Reviews the page like a design lead would: what looks generic or inconsistent, how clearly it guides people, a 0 to 4 score per check, and a priority list. Nothing changes.
06 · Fix it, keep it yours Agent chat
```
/impeccable polish the pricing page. Keep our colors, plan names, and monthly/yearly switch.
```
Fixes spacing, type, alignment, labels, focus and hover states, and missing loading, empty or error states, while keeping your look, words and features. It works through the critique's priorities first.
07 · Check before you ship Agent chat
```
/impeccable audit the pricing page
```
Checks five areas: accessibility, performance, theming, responsive layout and consistency. Each scores 0 to 4, out of 20. Findings are ranked P0 (blocks someone) to P3 (small).
Always · The design hook Background
```
/impeccable hooks status
```
After your agent edits a page or stylesheet, a checker looks for the usual tells (gradient text, glows, gray on colour, tiny tap targets) and tells the agent, which fixes them while the change is fresh.

Step 1 of 7 · Coding tool

Impeccable's docs

Install it

In Claude Code's chat

/plugin marketplace add pbakaus/impeccable

Adds Impeccable's plugin list to Claude Code. Then type /plugin, pick Impeccable and install it (or type /plugin install impeccable@impeccable). The skill and the design hook come together.

What you see

Impeccable in the /plugin list, then a confirmation that it's installed.

Watch out

Not on Claude Code? The GitHub Copilot app has it built in (Settings → Experimental). In VS Code, install Impeccable from Extensions. In Codex, Cursor and others, ask your agent to install the Impeccable skill for this project and approve what it runs.

The order is from Impeccable's getting-started tutorial: install, init, then a new page or an existing one, then review. The seven-box split per path and both walkthrough stories are FakeNerd's. Quotes are from posts on X, linked and dated.

Site already live? It works on the code, not the website

Impeccable never touches your live website. It works on the code your site is built from, and you look at each change on a test copy first. Visitors see nothing until you deploy, the same way you do today. Follow the “site that's already up” path on the map, one page at a time, plus the three moves below.

Where it works · how a change travels

Edits happen hereYour site's codeThe project your site is built from. Your agent and Impeccable read and edit only here.
You check hereYour test copyThe site running on your own computer. You look at every change here. Ask your agent to start it.
Read-onlyYour live siteNothing reaches it until you deploy, the same way you do today. Impeccable can look at it, never edit it.

Three extra moves for a live site

01
Work on a copy of the code
Before any change, have your agent set your work aside on its own branch. Your live site can't change by accident, and you can throw it all away.
In agent chat · FakeNerd's prompt
```
Before you change anything, start a new git branch called impeccable and work there.
```
02
First look at the real thing
critique works on a web address too. It reviews the live page as visitors see it and changes nothing. Best when your coding tool can open a browser.
In agent chat
```
/impeccable critique https://yoursite.com
```
03
Tell the checker what's on purpose
If your brand uses something the checker flags, record it once with a reason. Inter as a brand font is the docs' own example. Only that one thing is skipped.
In agent chat
```
/impeccable hooks ignore-value overused-font Inter --reason "Brand font"
```

Three kinds of change, and what each keeps

Fix what's there

polish, layout, typeset, clarify and the rest. Your look, words and features stay. It asks before replacing facts in your copy.

Docs example

/impeccable polish the pricing page. Keep our colors, plan names, and monthly/yearly switch.

Add a page

The new page follows the look you already have. For a whole new page you may get a picker, but only for the layout, not colours or fonts.

Docs example

/impeccable add a billing settings page. Follow our existing settings screens and reuse the shared form controls.

Redesign

Only when you say redesign. It replaces the look but keeps your content, features and facts, and goes through the direction picker.

Docs example

/impeccable redesign the marketing site. Keep the product facts and signup flow, but replace the current visual style.

No code to open? · FakeNerd's read

If your site lives in a site builder like Squarespace or Wix and there's no code project, Impeccable can only look: critique the address, or use its browser extension. It changes code, so it can't edit those sites for you.

The address critique, the brand-font exception and the three change prompts are from the skill files and the impeccable.style docs. The branch prompt and the site-builder note are FakeNerd's.

From people using it, on X

Posts from Paul Bakaus and people using Impeccable, found on X on Oct 20, 2026. Most posts about it are lists of repos; these are the ones that say how it was used. Translated posts are marked. Older posts use old names: teach is now init.

On a new buildinit first, describe the page, polish once it works.

“The teach step is the unlock: one-time setup where you give it your audience, use case, brand personality … every session after references it instead of guessing.”
teach is the old name for init. It still works.
sonicdr1p · @sonicdr1p Aug 10, 2026
“No command to learn, it works out the job itself (blank slate, redesign, added section, scoped refinement).”
Paul Bakaus, who makes it · @pbakaus Jul 22, 2026
“Once it's up and running, use the "impeccable polish" skill to make the UX look cool.”
Part of his prompt to the agent for a new app.
Franci Penov · @francip Sep 18, 2026
“Before and after … how fast can you create a better landing page in 5-10min max.”
Alex Giuseppe Ispas · @agispas May 5, 2026

On a site that's already upLook first, keep your identity, polish, let the hook clean up.

“First, try running /impeccable audit on the site you already have.”
Translated from Japanese.
Aircle · @AiAircle34052 Sep 25, 2026
“A visitor would not be surprised to learn it's AI-generated, but it doesn't scream "AI" either; it whispers "template."”
What the critique said when he tried it on a website. His reaction: "Ouch".
Aaron Powell · @slace Jul 1, 2026
“Existing codebase, it reads your design system and preserves your identity.”
Paul Bakaus, who makes it · @pbakaus May 29, 2026
“Give your agent the "Impeccable" skill and give your homepage a polish.”
His advice on someone's live homepage with too many colours and about four fonts.
Ali Homsi · @Ali_Homsi Oct 19, 2026
“Your agent writes UI, the detector flags what's wrong, the agent fixes it, and it repeats until there are zero findings.”
He turns it on with /impeccable hooks on, and is pointing it at "the ugliest page I own".
Dizzzank · @dank0296 Oct 15, 2026

Revamps people shippedReal projects, said in their own words.

“Latent Scope 1.0 … topped off with a skill definition and an Impeccable powered UI revamp.”
Ian Johnson · @enjalot Jul 12, 2026
“Codex with the impeccable skill is really good for UI tweaks and redesigns.”
On redesigning his mobile app.
Wamwea · @wamweaaa May 20, 2026
“Done, but something still feels off → bolder, distill and polish turn "make it look better" into specific changes.”
Vox · @Voxyz_ai Sep 27, 2026

Cautions and other viewsNot everyone stays, and the hook deserves a look.

“In Claude Code hooks run outside tool approval and can download the engine on first edit, so review it before unattended runs.”
Syb · @DegenOfWallSt Oct 4, 2026
“Ok so claude design is dope. Was using the impeccable skill before for designs but damn.”
He moved to Claude Design, which one-shots new screens for an app he already had. An older Impeccable version.
Martin · @DWalkingFridge Apr 18, 2026

The commands: start with seven

Impeccable is one skill with 24 commands, all typed as /impeccable followed by the command. You don't need to know them: plain words get routed to the right one. These seven cover a first project.

initSaves who it's for in PRODUCT.mdWrites PRODUCT.mdFirst, once per project

design … (plain words)A new page or a new look, through the pickerBuilds codeA new build

shapePlans a page and stops before codeWrites a briefYou want a plan first

documentRecords your current look in DESIGN.mdWrites DESIGN.mdYour site is already up

critiqueDesign review with scores and prioritiesNothing, it reportsIt feels off and you can't say why

auditAccessibility, speed, dark mode, phonesNothing, it reportsBefore you ship

polishFixes the details, keeps the lookChanges codeDirection's right, details aren't

What do I use for…? · six rows from the docs, three from the command list

Unfinished details, alignment, uneven spacingpolish

A confusing structure or weak hierarchylayout

Hard-to-read text, mixed-up fontstypeset

Too much competing for attentiondistill

Vague labels or instructionsclarify

Too timid, or too loudbolder / quieter

Breaks on phonesadapt

Feels slowoptimize

Blank screens when data is missing or failsharden

The other seventeen, for later

Refine

animate · Motion that explains changes and feedback
bolder · More presence for a timid section
colorize · Colour that does a job
delight · Memorable touches in the right moments
layout · Spacing, rhythm, where the eye goes
overdrive · Effects past the expected
quieter · Less noise, same personality
typeset · Fonts and text hierarchy

Simplify

adapt · Work on another screen or device
clarify · Clearer labels, errors and instructions
distill · Strip clutter to the essentials

Harden

harden · Errors, long text, missing data
onboard · First-run flows and empty states
optimize · Find what's slow, fix, measure

System and browser

extract · Repeated bits into shared components
generate · Variants of one element, in the browser
live · Point at the page, compare, accept one

Make a shortcut · in agent chat

/impeccable pin audit

Now /audit works on its own. Undo with /impeccable unpin audit.

Turn the checker on or off · in agent chat

/impeccable hooks on

Also off and status. The full command list is in the skill file.

The files it writes

Two plain text files at the top of your project, and one working folder. PRODUCT.md is about people, DESIGN.md is about the look. Keeping them apart is the point.

PRODUCT.md

Written by: init

Holds: Users and their job, purpose, positioning, constraints, brand commitments, accessibility needs

Not: Colours, fonts, page ideas, made-up testimonials

Keep it with your code

DESIGN.md

Written by: document, or the first new design when it finishes

Holds: Colours, type, components and their rules: the look future work must follow

Not: Who the product is for (that's PRODUCT.md)

Keep it with your code

.impeccable/

Written by: Every command, as it runs

Holds: Shared settings, critique reports, page briefs, screenshots, live-mode state

Not: Your code

Keep the shared files, skip the rest

PRODUCT.md · the headings init fills in

# Product

## Platform
## Stack
## Users
## Product Purpose
## Positioning
## Operating Context
## Capabilities and Constraints
## Brand Commitments
## Evidence on Hand
## Product Principles
## Accessibility & Inclusion

From the init instructions in the repo. It leaves a heading blank rather than invent an answer.

Keep the clutter out of git · in agent chat

Add Impeccable's recommended .gitignore block from its README to this project's .gitignore, so screenshots and session files stay out of git.

Shared settings, page briefs and critique reports still get saved with your code; screenshots and session files don't.

Starter prompts

Three prompts from Impeccable's own docs, each with a FakeNerd fill-in version. Paste into your coding tool's chat and fill in the [BRACKETS].

A new build · Impeccable's example

/impeccable design a signup page for our monthly book club. Help visitors understand the next event and reserve a seat.

From the getting-started tutorial.

A new build · FakeNerd fill-in

/impeccable design a [PAGE] for [WHO IT'S FOR]. Help visitors [THE ONE THING THEY SHOULD DO]. Keep [ANYTHING THAT MUST NOT CHANGE].

A site that's already up · Impeccable's example

/impeccable this dashboard feels crowded and the important numbers are hard to find. Improve the hierarchy while keeping our colors and existing features.

From the improve-a-design docs.

A site that's already up · FakeNerd fill-in

/impeccable this [PAGE] feels [WHAT'S WRONG, IN YOUR WORDS]. Improve [WHAT TO WORK ON] while keeping [WHAT MUST STAY].

Feedback after a round · Impeccable's example

The plan comparison is easier to read now. Keep that, but restore the monthly/yearly switch above it.

From the getting-started tutorial. One keep, one change.

Feedback after a round · FakeNerd fill-in

The [PART] is better now. Keep that, but [ONE SPECIFIC CHANGE].

Six watch-outs

The things that trip up first-timers, and what to do about each.

1Restart after installingCoding tools load new skills when they start.Do: Restart, then type /impeccable to check.
2Reports don't fix anythingcritique and audit only read. Beginners often wait for changes that never come.Do: Read the report, then ask for the fixes you want.
3The hook runs without askingIn Claude Code it runs on every page edit and may download Impeccable's checker the first time. Syb flagged this on X; the README says the same.Do: Know it's on. /impeccable hooks off before unattended runs.
4Live mode is for your test copyIt edits the site running on your computer. Never point it at the live site or loosen your site's security to make it work.Do: To look at the live site, use /impeccable critique with its address.
5The picker talks to impeccable.styleDealing design directions asks Impeccable's server. Unless you opt out, it also logs which card won, anonymously. Your files, code and PRODUCT.md are not sent.Do: Ask your agent to turn off Impeccable telemetry for this project.
6Keep the clutter out of gitScreenshots and session files pile up in .impeccable/.Do: Use the .gitignore prompt in the files section.

Telemetry details are in Impeccable's privacy page.

Try it, smallest version first

Six steps, all in the chat. Step 3 is the smallest look at a site you already have; steps 4 to 6 are a new build in an empty folder. Works in Claude Code, and in a cloud box in Cloudroom or bb; if the picker can't open a browser there, the choice happens in the chat.

01
Add the plugin
Free · 2 min
In Claude Code's chat. Then type /plugin and install Impeccable from the list. Other tools: see step 01 on the map.
Step 1 · In Claude Code's chat
```
/plugin marketplace add pbakaus/impeccable
```
02
Restart and ask what's next
Free
Restart Claude Code in any project and type /impeccable. It reads the project and suggests where to start.
Step 2 · in agent chat
```
/impeccable
```
03
Smallest look: a site you already have
Your tool's usage · 5 min
Read-only. Point it at your live site and read the verdict. Aaron Powell's told him his site "whispers template".
Step 3 · in agent chat
```
/impeccable critique https://yoursite.com
```
04
Or start fresh: init in an empty folder
Your tool's usage
Open Claude Code in a new, empty project. When init asks what to build with, say plain HTML and CSS. Answer the who-and-why questions in a sentence or two.
Step 4 · in agent chat
```
/impeccable init
```
05
Ask for one page
Your tool's usage
Use the fill-in prompt below, or the book club one as it is. Pick a direction in the picker.
Step 5 · in agent chat
```
/impeccable design a signup page for our monthly book club. Help visitors understand the next event and reserve a seat.
```
06
Steer, polish, audit
Your tool's usage
Ask your agent to open the page. Say one thing to keep and one to change, then polish, then audit and fix the P0 and P1 findings.
Step 6 · in agent chat
```
/impeccable polish the signup page
```

Commands are from the README, the skill file and the tutorial. The step order is FakeNerd's.

Next to the others

Other design and skill pages on this site, and one more Impeccable map.

Design like Ras Mic A six-step design loop built around Paper and its MCP, with his prompts. No skill pack.You'd rather design on a canvas first
Which skill pack, when Pocock, Addy Osmani and pstack compared. Impeccable is design-only, so it sits next to any of them.You're choosing your agent's general skills
Eric Tech's Impeccable map Another picture of the commands, already in the Cortex as its own card.You want a second view of all 24

FakeNerd's take

Read PRODUCT.md. Really.

Users on X call init the step that makes everything else work, and they're right. One wrong line about who the users are quietly steers every page after.

On a live site, look before you touch

critique and audit change nothing, which makes them the safest first move on a site people already use. Read one before you ask for a single change.

Ignore 20 of the 24 commands for a week

init, critique, polish, audit, and plain words for anything new. That covers most first projects. Pin the one you use most: /impeccable pin audit gives you /audit.

Let the hook do the nagging

It catches gradient text and gray-on-colour while the agent still has the edit in mind. Just know it's on, and switch it off for unattended runs.

Attribution

Impeccable is made by Paul Bakaus, Apache 2.0. The commands, install steps, file names, the AI tells, scores and P0 to P3 labels are from the README, the skill file and the impeccable.style docs (docs), read Oct 20, 2026, at release 4.7.0. Prompts marked as Impeccable's are quoted from its docs.
Disclosure: Paul Bakaus runs Renaissance Geek, the company behind Impeccable, backed by a16z and partnered with GitHub (his post, Jun 22, 2026). It sells a paid review product for pull requests; the skill on this page is free. Choosing design directions contacts impeccable.style and, unless you opt out, records which card won.
Quotes from X were found on Oct 20, 2026 and are each linked and dated. Translations from Japanese and Chinese are FakeNerd's. Posts were read, not tested; claims in them are the posters'. Older posts use old command names (teach, now init).
The README's command table calls craft a full shape-then-build flow; the newer skill file calls it an old name for an ordinary new-design request. This page follows the skill file and the docs. Rule counts (61) are Impeccable's, not recounted.
No video. The two-path map, the seven-step split, both walkthrough stories, the glossary, the example grouping, the fill-in prompts, the branch prompt, the step order in Try it and the takes are FakeNerd's. Not sponsored by anyone on this page.

Six things to know

One skill, one word

Install it from the chat

init comes first

New build: you pick the look

Site already up: look first

A checker rides along

Words on this page

Your agent can code. Impeccable gives it taste.

A first landing page

Fix a page that feels off

A check before launch

Make new pages match

Try three versions in the browser

Let the hook clean as it goes

Everything named

The skill: /impeccable

The Claude Code plugin

The design hook

The detector

Image generation

impeccable.style

The seven steps

Install it

Site already live? It works on the code, not the website

Work on a copy of the code

First look at the real thing

Tell the checker what's on purpose

Fix what's there

Add a page

Redesign

From people using it, on X

The commands: start with seven

The files it writes

PRODUCT.md

DESIGN.md

.impeccable/

Starter prompts

Six watch-outs

Try it, smallest version first

Add the plugin

Restart and ask what's next

Smallest look: a site you already have

Or start fresh: init in an empty folder

Ask for one page

Steer, polish, audit

Next to the others

FakeNerd's take

Read PRODUCT.md. Really.

On a live site, look before you touch

Ignore 20 of the 24 commands for a week

Let the hook do the nagging

Attribution