Brooke Wright
Brooke Wright · @wright_mode
FREE GUIDE

6 plugins that fix Claude Code's front-end design

One prompt sets up all six: the skill that bans the purple gradient, Vercel's pre-ship audit, a design system preset, a real browser to test with, Anthropic's own design brief, and Apple's guidelines as an audit for the site you already have.

Copy-paste readyFree tools onlyEvery claim fact-checkedBuilt by Brooke
Something went wrong. Please try again.

No spam. Unsubscribe anytime.

One prompt sets up all six: bans the AI defaults, audits the interface, tests the site, marks it against Apple's rules, then designs with an opinion Jump to the prompt → Join the Membership
Wright Mode — Free Guide

6 Plugins That Fix Claude Code's Front-End Design

Purple gradient, centred hero, three equal cards, same font as everyone. Claude has one default look and it is obvious. These six free tools replace it — and check the thing actually works before you ship.

6 free tools One installer prompt Mac, Windows or Linux About 10 minutes Every claim fact-checked

What's inside

Open Claude Code, paste this, and it installs four of the six for you and hands you the two lines you type yourself. It reports back in plain English after each one, so you always know what just changed.

Before you paste

You need Claude Code open — Mac, Windows or Linux all work. Use the project you are actually designing, not a scratch folder. It takes about ten minutes. Claude asks permission before each install, so say yes. Most of these install through outside tools rather than the Claude plugin menu, which is normal but worth knowing so you are not surprised.

Install these six free design add-ons for Claude Code, one at a time, and tell me in plain English what you did after each one. Work out which operating system I am on first. Check whether each one is already installed before installing it. If a step fails, tell me what went wrong in one sentence and move on. Do not stop the whole job. 1. The design taste skill (stops you defaulting to the same AI-looking layout). Run: npx skills add https://github.com/Leonxlnx/taste-skill Note the installable skill is called design-taste-frontend, not taste. Tell me that name so I can invoke it properly. 2. Vercel's web interface guidelines (audits my code against their accessibility and interface rules). Run: npx skills add vercel-labs/agent-skills Tell me the skill I want out of that pack is web-design-guidelines, and that it fetches the current rules from the internet each time it runs, so it needs a connection. 3. A design system preset from the awesome-design-skills collection. Run: npx typeui.sh pull clean Tell me that clean is only one of 67 presets, that this is a third-party tool writing into my .claude folder, and that I can swap the last word for another preset later. Show me the browse link: https://typeui.sh/design-skills 4. Playwright (drives a real browser so you can test that my site actually works) is a plugin I install myself. Tell me to type this inside Claude Code: /plugin install playwright@claude-plugins-official 5. Anthropic's frontend-design skill is also a plugin I install myself. Check first whether I already have it, since it is a popular one. If I do not, tell me to type: /plugin install frontend-design@claude-plugins-official 6. The platform design skills pack (Apple's Human Interface Guidelines, Google's Material Design 3 and the WCAG accessibility rules, written out as rules Claude can audit my work against). Run: npx skills add ehmo/platform-design-skills Tell me it installs nine skills, that the one I want for auditing a website is called web-design-guidelines, and that Vercel's pack from step 2 ships a skill with that exact same name — so I know to say which pack I mean when I invoke it. When you are done, give me a six-line summary: each tool, installed or not, and the one thing I do next to use it.
2

Then type these two lines inside Claude Code

These two come from Anthropic's own plugin marketplace, which is built in, so there is nothing to add first. Paste them one at a time.

/plugin install playwright@claude-plugins-official /plugin install frontend-design@claude-plugins-official

Only want one?

Make it the design taste skill. It is the one that actually names the purple gradient and the centred hero on a dark mesh background and tells Claude to stop. The other four are useful; that one is the fix.


"It looks AI-made" is really six different complaints. The palette and layout are the defaults. Nobody checked whether it is usable. There is no consistent system underneath. Nobody tested whether it works. Nothing was ever measured against a published standard. And the model was never told to design like a person with an opinion. One of these for each.

🎨

"Purple gradient, centred hero, again"

The design taste skill. Names the defaults out loud — the purple gradient, the dark mesh hero, three equal feature cards, glass on everything — and bans them before Claude writes a line.

♿

"Is any of this actually usable?"

Vercel's interface guidelines. Audits your files against 100-plus rules on focus states, forms, motion, contrast and touch targets, and reports them by file and line.

🧭

"Every page looks like a different site"

awesome Design Skills. Hands Claude one named aesthetic with its own colours, spacing and component rules, so page five matches page one.

🔍

"I never checked if it works"

Playwright. Gives Claude a real browser. It walks your signup flow, submits your forms, and tells you what 404s or breaks on a phone.

✎

"It designs like nobody in particular"

frontend-design. Anthropic's own skill. Puts Claude in the role of a designer whose client has already rejected the templated version, and makes it justify its typography.

📏

"It looks fine, but it does not look premium"

Apple's Human Interface Guidelines. Hands Claude a published rulebook instead of an adjective, and has it mark the site you already have against it, line by line.

The prompt sets up all six. One at a time: taste skill first, then frontend-design, then Vercel's audit before you ship, then Playwright to prove it works, then the Apple guidelines pack when you want a second opinion on a site that is already built, and the preset collection only if you are struggling to stay consistent.


What each one actually does, a prompt to prove it is working, and the catch. Two of these are commonly described as things they are not, so read the catches — they are the useful part.

1

The design taste skill · bans the AI defaults

Before it writes any code it has to produce a one-line design read: what kind of page this is, who it is for, the feel, and the system it will use. Then it is banned from the defaults every AI site reaches for — the purple gradient, the centred hero on a dark mesh, three equal feature cards, glass on everything, the same grey-blue text on the same sans-serif. The repo also ships a dozen sibling skills for specific looks: brutalist, minimalist, soft, and a redesign one.

The skill you invoke is called design-taste-frontend. Ask for "taste" and nothing happens, which is where most people give up on it.

Using the design-taste-frontend skill, build me a landing page for [describe what you sell in one line]. Give me your design read first, before any code. Then tell me which default look you are deliberately steering away from and what you are doing instead.

The catch: it says out loud what it is not for — "landing pages, portfolios and redesigns, not dashboards, not data tables, not multi-step product UI". If you are building an app rather than a marketing page, this is the wrong tool and it will tell you so. It also has no library of beautiful sites to copy from; it is a written rulebook that works by banning the bad defaults, not by showing Claude good examples. And the current version is labelled experimental, with the older one kept available separately, which tells you the behaviour changed enough that people wanted a way back. See it on GitHub →

2

Vercel's web interface guidelines · the pre-ship audit

Vercel publish a long list of rules for building interfaces that actually work: focus states, keyboard access, form behaviour, animation that respects people who have switched motion off, contrast, line length, image handling, dark mode, touch targets. This skill reads your files and reports every breach by file and line, tersely, without rewriting anything.

Run it as the last thing before you ship. It catches the boring failures that make a site feel cheap to use even when it looks fine.

Use the web-design-guidelines skill to audit my main page and components. Give me the findings by file and line, then rank them by what would actually hurt a real visitor first, not by how easy they are to fix.

The catch: it is a compliance checker, not a taste critic. It will tell you a button has no label and your animation ignores reduced-motion settings. It will never tell you the page looks generic — that is what number one is for. It also fetches the current rules from the internet on every run rather than storing them, so it needs a connection to do anything. One more trap: this skill is not in the Vercel plugin you may already have installed from Anthropic's marketplace. It comes from the separate agent-skills repo, which is what the install prompt uses. See it on GitHub →

3

awesome Design Skills · one aesthetic, applied consistently

A collection of 67 design presets. Each one is a file describing a named look — brutalist, clean, bento, clay, corporate, colourful — with its colour tokens, spacing, component rules and accessibility constraints written out for the agent. You pull the one you want and Claude designs inside it, so page five matches page one instead of drifting.

You can browse them all with previews at typeui.sh before committing, which is worth doing — the names do not tell you much.

Rebuild my pricing page using only the tokens and component rules from the design skill I just pulled. Show me which of my existing styles you had to throw out to stay inside it, and flag anything in the preset that clashes with my logo colours.

The catch: it hands you one aesthetic preset, not a full design system. You pick brutalist or clean and get that look's rules — useful for consistency, not the same as having a brand. It installs through an outside command-line tool rather than the Claude plugin menu, which means trusting a third-party package to write into your .claude folder, so read what it does before you run it. And watch the name: there are at least three similarly-named collections on GitHub and they are not the same thing. The one described here is bergside/awesome-design-skills. See it on GitHub →

4

Playwright · a real browser Claude can drive

Made by Microsoft, installed as a plugin from Anthropic's own marketplace. It gives Claude an actual browser to use: navigate pages, click things, fill and submit forms, upload files, resize to a phone, take screenshots, read the console and watch network requests. It reads the page through its accessibility structure rather than by looking at pictures, which is why it works reliably and does not need a model that can see.

This is how you find out that your contact form has been quietly broken for three weeks.

Using Playwright, open my site, walk the whole signup flow end to end, and submit my contact form with test data. Report anything that 404s, throws a console error, or breaks at 375 pixels wide. Do not fix anything yet, just tell me what you found.

The catch, and it is a big one: Playwright has no design opinion whatsoever. It cannot tell you a page looks generic, and anyone who says it can is wrong. It confirms your forms submit and your links resolve; the aesthetic judgement is entirely on you and the other four tools. It is also a browser server, not a command-line tool, despite how it usually gets described — there is a separate Playwright command-line tool for running test files you have written yourself, and that is not this. Install it with the plugin line above and you will get the right one. See it on GitHub →

5

frontend-design · Anthropic's own design brief

Made by Anthropic, and quietly the most opinionated thing on this list. It puts Claude in the role of a design lead whose client has already knocked back the templated version, so it has to work out the subject, the audience and the actual job of the page before designing. It pushes deliberate typography — one or two typefaces, a real scale, lines short enough to read — and names specific AI-design giveaways to avoid, including Anthropic's own cream-and-terracotta house style, on the grounds that it is now a dead giveaway too.

Check before you install. It is popular enough that you may already have it.

Design a landing page for [describe what you sell in one line]. Before you write any code: tell me the subject, the audience and the main job of this page as you understand them, name the two typefaces you are picking and why they suit this subject specifically, and list which AI-design cliches you are steering away from.

The catch: it is written instruction only — no code, no components, no colour tokens, no checker. Nothing stops Claude ignoring it, and you will not get an error when it does. It also pushes towards taking a risk rather than playing it safe, which is the point, but if you needed something conventional for a conservative client it can pull the wrong way. Pair it with the Vercel audit so somebody is still checking the boring things. See the skill on GitHub →

6

Apple's Human Interface Guidelines · rules instead of adjectives

You cannot prompt your way to "premium". You can hand Claude somebody else's actual rulebook. This pack takes Apple's published Human Interface Guidelines, Google's Material Design 3 and the WCAG 2.2 accessibility standard and rewrites them as rules an agent can mark work against — nine skills in total, one for each Apple platform, one for Android and one for the web. The web skill is the one that matters for a website: about seventy rules covering contrast, focus states, forms, motion, typography, dark mode and what happens to your layout on a phone.

The best use is not building something new with it. It is pointing Claude at the site you already have and asking it to mark the work — which is a job it can do without needing a single idea of its own.

Audit my existing site using the web-design-guidelines skill from the platform-design-skills pack. If I have Playwright installed, open the live page at [your URL] and look at it properly. Otherwise read the files in [the folder my site lives in]. Do not redesign anything and do not write any code yet. Report only. For everything I am breaking, give me three things: the rule in plain English, where it breaks, and what a real visitor actually experiences because of it. No jargon and no bare rule numbers. Then rank the findings by what is costing me enquiries, not by what is quickest for you to fix. Contrast, tap target sizes and anything that falls apart at 375 pixels wide goes at the top, because that is where most of my traffic is. Last thing: split the list in two. Findings that come from the web and accessibility rules and genuinely apply to my site, and findings that come from Apple's guidelines for their own apps and do not. I will pick what you fix from the first list.

The catch: it reviews, it does not design. It will tell you your contrast fails, your tap targets are too small and your form fields have no labels, and it will fix any of that once you point at it — but it has no idea what your page should be. Ask it for a concept and nothing comes back. Number one and number five are where ideas come from; this is the one that marks them. The bigger catch is the source: Apple wrote the Human Interface Guidelines for Apple's own platforms, so a fair slice of this pack is about tab bars, the Digital Crown and Vision Pro, and none of that maps onto a marketing website. Use the web skill for your site and treat the Apple ones as background reading. One trap that will bite you: this pack and Vercel's from number two both ship a skill called web-design-guidelines. Install both and you will not know whose rules you just got, so name the pack when you invoke it. See it on GitHub →


None of this is permanent. If you want to start clean, paste this and Claude removes all six and puts your settings back.

Remove the six design add-ons you installed for me and put things back the way they were. Show me a checklist as you go. 1. Remove the design-taste-frontend skill and any sibling skills that came with it from the taste-skill repo. 2. Remove the web-design-guidelines skill and anything else that came in with the vercel-labs agent-skills pack. Tell me what else was in there before you delete it, in case I want to keep something. 3. Remove the design preset that typeui.sh wrote into my .claude folder. Tell me the file path before you delete it. 4. Remove the platform-design-skills pack and all nine skills that came with it. Careful here: Vercel's pack in step 2 also has a skill called web-design-guidelines, so tell me which pack each one belongs to before you delete anything. 5. Remind me to remove playwright and frontend-design from the /plugin menu inside Claude Code myself, since you cannot do that for me. If frontend-design was already installed before today, leave it and tell me so. 6. Do not touch any design work, components or styles that were produced while these were installed. That is my code now. When you are done, tell me in one line whether anything is left over.

Keep whatever changed your output and bin the rest. Most people end up keeping the taste skill and Playwright — one to stop the bad defaults, one to prove the thing actually works. That is a good place to land.


Ready to go deeper?

Where to go from here.