3 Free Skills That Give Claude Actual Design Taste

Working code is not the same as good design

Claude will build the thing you asked for and it will run. Then you look at it and the spacing is off, the animation eases the wrong direction, and every border is a solid one-pixel line. Nothing is broken. It just looks like a project built by a machine.

That gap is taste, and taste is teachable. Three people packaged theirs up and gave it away.

What each one does

All three are free and open-source. Impeccable is Apache-2.0, the other two are MIT.

Before you start

• Node.js 22.20 or newer — all three install through the terminal using npx, which ships with Node. The shared skills installer behind Steps 2 and 3 requires 22.20 or newer (Impeccable's own installer runs on Node 18.19 or newer). Run node -v to check.
• Chrome, Edge or Chromium — Taste-Skill checks its own pages in a real browser, so one of them has to be installed. It also needs the internet to find photos.
• Claude Code, already set up — these teach Claude how to make design decisions. They do not replace it.
• A real project open — install from the folder your project lives in, not an empty directory.

Two of them share one installer

This trips people up, so it is worth saying up front. Skills for Design Engineers and Taste-Skill both install through the same community skills CLI. Impeccable ships its own installer. Same idea, different command, and mixing them up is the most common mistake.

Run this from the root of your project:

npx impeccable install

It detects which AI tools you have set up, asks whether to install into this project or globally, and wires itself in. Reload Claude Code afterward or it will not pick the skill up. Then run /impeccable init once. It asks about your product and saves the answers in a PRODUCT.md file, so later commands know your audience and tone.

Once it is in, you get commands that work on pages you have already built:

/impeccable audit blog
/impeccable critique landing
/impeccable polish settings
/impeccable harden checkout

You can also just describe what you want instead of using a subcommand:

/impeccable redo this hero section

Impeccable can also work on the page while you watch. Run /impeccable live, pick an element in your browser, describe the change and compare variants. Live mode is in beta and needs your site running on a local development server (or a local static HTML file). It does not work on a deployed production site.

To refresh it later, run npx impeccable update.

npx skills@latest add emilkowalski/skills

This one is mostly about motion. It ships fifteen skills covering animation vocabulary, building an animation, finding places worth animating, reviewing animation you already have, fixing animation that drops frames, picking a UI library, and an Apple-design pass. A few go beyond motion: mobile-native fixes, a stress test with worst-case data, and Swift.

The reason it matters: agents pick the wrong easing constantly. An ease-in on something entering the screen when it should be ease-out. A solid border where a soft shadow would look better. Each mistake is tiny and they compound into an interface that feels cheap.

npx skills add https://github.com/Leonxlnx/taste-skill --skill "design-taste-frontend"

That installs one skill, design-taste-frontend. A script deals Claude three of 20 researched art directions and Claude picks one. Then it finds real photos in open collections such as Wikimedia Commons, Openverse and the Met, builds the page, checks it in a real browser at three widths, and fixes the top three problems it sees, for up to three rounds. A build takes roughly 30 to 45 minutes and a few hundred thousand tokens, so start it and let it run.

The older Taste-Skill skills (brand kits, minimalist and brutalist directions, image-to-code) moved out of this repo. They now live in Leonxlnx/taste-skill-classics and Leonxlnx/imagegen-skills.

What to do once they are in

Do not install all three and then keep prompting the way you always did. Name the tool you want in the request:

Build the pricing page, then run /impeccable critique on it before you show me.

For anything with motion, ask for the animation pass explicitly. For anything where the whole look feels generic, reach for Taste-Skill and name a direction instead of asking for "modern."

Three things that trip people up

• Not reloading after installing Impeccable — it wires itself into your tool's config, and that config gets read at startup. Skip the reload and it looks like nothing happened.
• Guessing the skill name — the name you pass to --skill is the one written inside the skill file, which is not always the folder name. Taste-Skill's folder is called taste-skill, but the skill is design-taste-frontend. Copy the command above instead of guessing.
• Expecting them to fix a finished project on their own — these change how Claude decides things going forward. On something already built, use the audit and critique commands rather than hoping it self-corrects.

Frequently asked questions

Are these free?

Yes. All three are open-source on GitHub. Impeccable is Apache-2.0, the other two are MIT. You still need a Claude plan for Claude itself.

Do I need all three?

No, and they overlap a little. If you only take one, take Impeccable for its audit commands. Add the animation skills the moment anything on your page moves.

Do they only work with Claude?

Impeccable supports Claude Code, Cursor, Codex, Gemini CLI, and several others. The other two install as skills through a shared CLI and work anywhere that reads skills.

Will they change my existing files?

Installing does not touch your project code. It adds skill files that shape how Claude makes decisions from then on.

Do I need an API key?

No. None of the three ask for an account or a key.

Get them

• Impeccable — github.com/pbakaus/impeccable (opens in a new tab)
• Skills for Design Engineers — github.com/emilkowalski/skills (opens in a new tab)
• Taste-Skill — github.com/leonxlnx/taste-skill (opens in a new tab)