Skip to content
← All guides

Impeccable: The Free Claude Design Skill, Set Up

Every website Claude builds you starts to look the same: purple gradients, cards inside cards, the same fonts. Impeccable is a free skill that gives Claude a designer's eye and a slop detector with 62 checks. Here's the full setup in one prompt, every command explained, and the 5 prompts I'd actually run.

What Impeccable is

Impeccable logo Impeccable is a free, open-source design skill made by Paul Bakaus. It has over 100,000 stars on GitHub. Full credit to him: everything in this guide is built on his work and his docs at impeccable.style.

It isn't one skill, it's 24 commands. Each one does a different job a real designer would do: critique your page, make it bolder, fix the typography, polish it before launch. And it comes with a slop detector: 62 checks for the defaults AI keeps reaching for (purple gradients, cards inside cards, eyebrow chips, identical icon tiles, low-contrast text). With the automatic checks on, every time Claude edits a page the detector runs, sends the findings back, and Claude fixes them before it calls the work done.

It saves two small files in your project so it never forgets: PRODUCT.md (who the site is for and what it has to do) and DESIGN.md (your colors, fonts and components). Every command reads them first.

What you need

  • Claude Code
    Claude logo Comes with any paid Claude plan. The easiest way in is the Code tab in the Claude desktop app: no terminal, you just type to it. Impeccable also works in Cursor, Codex, Gemini CLI, GitHub Copilot and a dozen more.
  • A project folder
    The folder your website lives in. An empty folder is fine if you're starting fresh.
  • Node.js 18.19 or newer
    Only needed for one of the install routes. If you don't have it, the setup prompt below tells Claude to check and walk you through it.

1. Install it (one prompt)

This is the prompt from the video. Open your project folder in Claude Code, paste it, and answer Claude's questions. It installs Impeccable, sets it up for your site, turns on the automatic slop checks, and proves it works with a first critique.

Prompt 1: Install and set up Impeccable
Install the free Impeccable design skill for me and set it up for this project: https://github.com/pbakaus/impeccable

I'm not a developer, so do every technical step yourself and explain what you're doing in plain English.

1. Install it. Use the Claude Code plugin marketplace ("/plugin marketplace add pbakaus/impeccable", then install Impeccable from /plugin > Discover). If that doesn't work here, run "npx impeccable install" in this project folder and pick Claude Code. If I need Node.js 18.19 or newer, tell me exactly how to get it.
2. Tell me when to reload, then check that /impeccable shows up.
3. Run "/impeccable init". Read the project first, then interview me one question at a time to fill the gaps: who the site is for, what they need to do on it, what it must never lose (names, colors, anything locked), and the feeling it should give people. Save it all to PRODUCT.md and show it to me so I can fix anything you got wrong.
4. If this project already has a design, run "/impeccable document" so DESIGN.md records my current colors, fonts and components before anything changes.
5. Turn on the automatic design checks with "/impeccable hooks on" and walk me through any approval my setup asks for.
6. Prove it works: run "/impeccable critique" on my main page and give me the top 3 things to fix first, in plain English, with a one-line reason for each. Don't change anything yet.

Prefer to do it by hand?

Pick one of these, then run /impeccable init in Claude.

Inside Claude Code (no terminal)
/plugin marketplace add pbakaus/impeccable

Then open /plugin, choose Discover, and install Impeccable.
In a terminal, inside your project folder
npx impeccable install
Turn on the automatic slop checks
/impeccable hooks on

2. All 24 commands

You type them as /impeccable plus the command and what you want, like /impeccable critique the pricing page or /impeccable bolder the hero section. Plain English after the command is enough.

Create

  • /impeccable
    Just describe what you want to make or improve in plain English. The catch-all.
  • /shape
    Turns a rough idea into a design brief before anything gets built.

Evaluate

  • /critique
    Reviews your page like a senior designer and tells you what to fix first.
  • /audit
    Finds the technical problems: accessibility, speed, phone layout, broken states.

Refine

  • /bolder
    Gives a safe, boring section more presence while keeping it on-brand.
  • /quieter
    The opposite: tones down a page that is too loud, keeps its personality.
  • /typeset
    Makes text easier to read: headings, sizes, line lengths.
  • /layout
    Rearranges the page so people know where to look first.
  • /colorize
    Uses color on purpose: for actions, states and character.
  • /animate
    Adds motion that explains what changed, not motion for the sake of it.
  • /delight
    Adds the small satisfying moments people remember.
  • /overdrive
    Pushes past the expected for a page that needs to feel extraordinary.

Simplify

  • /distill
    Cuts clutter so the important things are easy to find.
  • /clarify
    Rewrites confusing labels and messages so people know what to do next.
  • /adapt
    Makes a design work on another screen size or device.

Harden

  • /polish
    The final pass before launch: spacing, labels, hover and focus states.
  • /harden
    Keeps things usable when data is missing, slow or wrong.
  • /optimize
    Finds what makes the page slow, fixes it and measures the difference.
  • /onboard
    Helps new users get to their first useful result.

System

  • /init
    Saves who your site is for and what it must do (PRODUCT.md). Run this first.
  • /document
    Records your colors, fonts and components (DESIGN.md) so new pages match.
  • /extract
    Turns repeated pieces into shared components.
  • /generate
    Makes a few versions of one element so you can compare and keep the best.
  • /live
    Point at something on your page, try variations, keep the one you like.

3. Fix a site that looks AI-made

Already have a site that screams "Claude made this"? This runs the commands in the order a designer would: find the problems, kill the slop, cut the clutter, make it stand out, then polish. It stops after every step so you stay in control.

Prompt 2: Fix my AI-looking site
My site looks like AI made it. Use Impeccable to fix it without breaking anything that works.

Work in this order and stop after each step to show me what changed before you continue:
1. "/impeccable critique" the homepage. List what's holding it back, ranked by what to fix first.
2. Run the slop detector on every page and list each AI tell it finds (purple gradients, cards inside cards, the same font everywhere, eyebrow chips, identical icon tiles, low contrast). Fix them all.
3. "/impeccable distill" anything cluttered so the one thing that matters on each page is obvious.
4. "/impeccable bolder" the hero section so it actually stands out, but keep my brand colors and names.
5. "/impeccable typeset" the whole site so headings, body text and line lengths are easy to read.
6. "/impeccable polish" every page for the final pass: spacing, labels, hover and focus states.
7. "/impeccable audit" before we call it done: accessibility, speed and how it looks on a phone.

Rules: keep my content, links, prices and product names exactly as they are. Show me a before/after for the homepage at the end.

4. Build a new page

Fill in the three brackets and paste. Asking for 3 directions first is the single biggest upgrade: you pick the look before Claude writes any code, instead of fighting the first thing it made.

Prompt 3: Build a page that doesn't look like AI
/impeccable design a [type of page, e.g. landing page for my coaching program] for [who it's for, e.g. busy dentists who want more 5-star reviews]. Visitors should be able to [the one thing they should do, e.g. book a free 15-minute call].

Before you build:
- Show me 3 different design directions with a one-line reason each, and let me pick one.
- Ask me anything you need to know about the business. Don't invent facts, prices or testimonials.

While you build:
- No AI tells: no purple gradients, no cards inside cards, no eyebrow labels above every heading, no identical icon tiles.
- One clear action per section. Make it work on a phone first.

When you're done, run "/impeccable critique" on what you made, fix the top 3 issues, then "/impeccable polish".

5. The pre-launch slop check

Run this before anything goes live. It doesn't stop until the slop detector comes back with 0 findings.

Prompt 4: Check everything before launch
Before I launch, run a full Impeccable check on this site.

1. Run the slop detector on every page and list every finding with the page it's on.
2. "/impeccable audit" the whole site: accessibility, performance, responsive layout and broken states.
3. "/impeccable harden" anything that breaks when data is missing, slow or wrong (empty states, error messages, long names).
4. "/impeccable polish" the pages that still feel unfinished.
5. Re-run the slop detector and don't stop until it reports 0 findings.

Give me one short list at the end: what you fixed, and anything you think I should decide myself.

6. Keep every page consistent

Once a page looks right, lock the design in so the next page Claude builds matches it instead of drifting back to AI defaults.

Prompt 5: Lock in my design system
Make sure every page we build from now on matches the design we just landed on.

1. "/impeccable document" this site so DESIGN.md records the colors, fonts, spacing and components we use now.
2. "/impeccable extract" any pattern that's repeated on more than one page into a shared component.
3. Check PRODUCT.md is still accurate about who the site is for and what it needs to do. Update anything that changed.
4. From now on, read PRODUCT.md and DESIGN.md before any design work, and tell me if a request would break the system.

The best ways to use it

  • Critique before you change anything
    Run /impeccable critique first and read it. Fixing the top 3 issues it names beats running every command at once.
  • Say what to keep
    Add your constraints to any command: "keep our colors and the current plan names." Impeccable refines what's there; it won't throw away what you tell it to protect.
  • Use bolder and quieter as a pair
    If bolder goes too far, quieter brings it back without losing the personality. Two quick passes beat ten rounds of "make it pop."
  • Compare instead of guessing
    Not sure about a section? /impeccable generate a few versions of it, or use live to point at it on the page and keep the one you like.
  • Leave the automatic checks on
    With hooks on, the slop detector runs every time Claude edits a page, without an AI model or API key. That's how you stop slop from creeping back in.
  • Always check it on your phone
    Open the page and try the one thing visitors should do. Then check a narrow screen. Most AI sites break there first.

What breaks it

  • /impeccable doesn't show up
    Reload Claude Code after installing. Still missing? Run the installer again and make sure you picked Claude Code and the right folder.
  • The automatic checks never run
    Some setups make you approve hooks first. Run /impeccable hooks on again and follow the approval step it shows you.
  • It designs for the wrong people
    Your PRODUCT.md is vague or wrong. Open it, rewrite who the site is for in one or two plain sentences, and re-run the command.
  • New pages don't match the old ones
    You never ran /impeccable document, so there's no DESIGN.md to follow. Run Prompt 5.
  • It's out of date
    Marketplace installs update from the /plugin menu. Terminal installs update with npx impeccable update.

Star Impeccable on GitHub →