Claude Designer Skills: Frontend, Brand & UI
Get The Claude Starter System
20 prompts, skills, and guides that get finished work out of Claude. Free PDF.
Claude designer skills turn a folder of instructions and reference files into a repeatable design process — a frontend design skill that stops Claude from defaulting to the same three fonts and blue gradient, a brand-voice skill that keeps every artifact on-brand without you re-explaining your palette each time, and a mockup workflow that gets a clickable UI in front of a client before a designer opens Figma. This guide covers all three, plus a complete, copy-paste brand-guidelines skill you can adapt today.
If you have not used skills at all yet, start with our what are Claude Skills primer first — everything below assumes you understand the basic folder-and-instructions model. As of October 2026, skills, artifacts and Claude Design are available on every Claude plan, including Free, so every workflow here runs in the Claude app once code execution and file creation are switched on. Claude Code, the other place design skills earn their keep, needs a paid plan.
One naming note before you start: "Claude Design" is also the name of Anthropic's own design tool, which now lives inside regular Claude chats. Skills and Claude Design work together rather than compete, and the Claude Design section further down explains which one to reach for.
Why design work specifically needs a skill, not just a prompt
A model trained on the statistical center of the internet reproduces the statistical center of design — the same rounded cards, the same Inter font, the same purple-to-blue gradient hero, on every single request. Anthropic's Applied AI team calls this distributional convergence, and it is the reason a bare prompt like "make this look nice" keeps handing you the same forgettable output no matter how many times you ask.
A skill fixes this by loading a point of view before Claude touches any code: banned fonts, a required commitment to one aesthetic direction, a rule that says take one real risk you can justify. That is the entire difference between a claude frontend design skill and a one-off styling prompt — the skill persists the taste, the prompt only persists the request.
Frontend design
Generates working React/Tailwind UI with a deliberate visual direction instead of generic defaults.
Brand-voice systems
Encodes your colors, type, and tone so every artifact matches your brand without re-briefing.
Artifact mockups
Turns a rough idea into a clickable preview you can hand to a client or developer same-day.
Frontend design: a skill, not a single prompt
A Claude frontend design skill gives Claude a design point of view before it writes any UI, and Anthropic publishes two official ones in its public skills repository. The frontend-design skill handles taste. As of October 2026 it describes itself as guidance for "distinctive, intentional visual design when building new UI or reshaping an existing one." It tells Claude to take the visual direction from the subject itself (the industry, materials and vernacular of whatever you are building), to spend its boldness in one place, and to take an aesthetic risk only when the brief justifies it.
The web-artifacts-builder skill handles the build: elaborate, multi-component artifacts made with React, Tailwind CSS and shadcn/ui, for jobs that need state, routing or real components rather than a single HTML file. It carries its own warning against what it says is often called "AI slop": excessive centered layouts, purple gradients, uniform rounded corners and the Inter font.
The frontend-design skill has changed since launch, and the change is worth copying. The version Anthropic described in its November 2025 post told Claude to avoid generic fonts like Arial and Inter and purple gradients on white backgrounds. The current version goes further and names the looks that now read as AI defaults in their own right: a warm cream background with a serif headline and a terracotta accent, a near-black page with one acid-green or vermilion accent, a dense broadsheet layout with hairline rules and square corners, and the SaaS kit of identical rounded cards with soft shadows and gradient washes. Ban one cliché and the model drifts to the next one, so a good design skill keeps its list of defaults to avoid up to date.
In practice, this changes what you get back. Instead of "here is a landing page," you get a page with a specific typographic hierarchy, a palette chosen for the brand rather than pulled from a default theme, and micro-interactions that read as intentional. You can install the official version directly, or write your own with the same philosophy baked into a shorter SKILL.md.
The distinction that matters for non-technical teams: a claude frontend design skill is not a plugin that makes things prettier as a finishing pass. It changes the order of operations. The aesthetic direction gets decided first, before any component gets written, the same way a real design lead would open a brief by picking a point of view rather than starting from a blank component library and hoping something coherent falls out the other end.
| Official skill | What it does | Reach for it when |
|---|---|---|
| frontend-design | Sets the visual direction and a quality floor for new or reshaped UI | Every UI request comes back looking the same |
| web-artifacts-builder | Builds multi-component artifacts with React, Tailwind CSS and shadcn/ui | The mockup needs state, routing or real components |
| brand-guidelines | Applies Anthropic's own brand colors and typography | You want a working pattern to copy for your own brand |
| theme-factory | Styles slides, docs, reports and landing pages with one of 10 preset themes, or a new one | You need a consistent look fast and have no brand system yet |
| canvas-design | Creates original static visuals as PNG or PDF files | You need a poster, cover image or one-page visual |
All five ship together in the example-skills plugin in Anthropic's repository, and the install steps for both the Claude app and Claude Code are in the brand-guidelines section below. If you would rather write your own, the prompt below captures the same philosophy in a form you can use today, with or without an installed skill.
Build this as an artifact using a frontend design skill mindset. Project: [what you're building, one sentence] Audience: [who sees this] Aesthetic direction: [one line, taken from the subject itself: its industry, materials, and vernacular. One direction, no blending.] Rules: - Avoid the looks that read as AI defaults: identical rounded cards with soft shadows and gradient washes, purple gradients, cream + serif + terracotta, near-black with a single neon accent. - No Inter, Roboto, or Arial as the display face. Pick a typeface pairing that supports the direction. - Spend your boldness in one place and be ready to justify it. - Use React + Tailwind. Build it as a working artifact, not a description of one. - Quality floor: responsive, visible focus states, respects reduced motion, readable contrast. Support light and dark mode. Return the artifact, then a short note on the one risk you took and why.
For teams working inside Claude Code specifically — where a skill can be scoped to a repo and reused across every UI task — our Claude Code skills guide covers how to install and structure this so it fires automatically whenever you touch a component file.

Skip writing the skill yourself
- 500+ copy-paste prompts & workflows
- 35 installable Cowork skills
- Role packs for 6 professions
- New prompts & skills every week, forever
Brand-voice design systems: teach Claude your brand once
A brand-voice skill is the reference pattern for encoding an actual brand into something Claude loads automatically instead of something you retype into every prompt. Anthropic's own public brand-guidelines skill does exactly this for its own brand — mapping specific hex codes for a dark and a light base, an orange primary accent with blue and green as secondary and tertiary accents, and pinning a font hierarchy (Poppins for headings, Lora for body copy), so any artifact that could use a brand look picks it up without being asked.
The pattern generalizes cleanly to any business. Instead of pasting your brand guidelines PDF into every chat, you write them once as a skill: colors, type, logo usage rules, tone-of-voice notes, do/don't examples. Claude loads it whenever the task looks like it needs a brand look, and every deck, landing page, or social graphic comes out consistent — no re-briefing, no drift between what marketing ships and what sales ships.
This matters more the bigger the team gets. A solo founder can hold their own brand in their head. A five-person marketing team cannot — someone always reaches for the wrong blue. A skill removes that failure mode because the rule lives in the file, not in whoever happened to write the prompt that day.
A complete brand-guidelines skill you can adapt today
Here is a full, working example. Save this as brand-guidelines/SKILL.md and swap in your own values — it is deliberately generic so you can drop your brand straight in.
---
name: brand-guidelines
description: >
Apply our brand's colors, typography, and voice to any artifact,
document, or design output. Use when creating marketing
materials, presentations, landing pages, or other visual assets.
---
# Brand Guidelines
## Colors
- Primary: #142033 (deep navy) — headers, primary buttons
- Secondary: #f5f7fa (cool off-white) — backgrounds
- Accent: #0f8a6c (deep green) — CTAs, highlights only
- Text: #1a1a1a on light backgrounds, #f5f7fa on dark
## Typography
- Headings: a serif with real character (e.g. Fraunces, Tiempos)
- Body: a clean grotesk (e.g. Söhne, General Sans)
- Never use Inter, Roboto, or Arial as the primary display font
## Voice
- Direct, confident, no hedging ("we think" -> "we")
- Short sentences over long ones. No corporate filler.
- Avoid: "best-in-class," "synergy," "cutting-edge," "leverage"
## Layout rules
- Generous whitespace over dense grids
- One accent color per screen, used sparingly
- Every CTA button uses the accent color, nothing else does
## When applying this skill
1. State the aesthetic direction in one line before building.
2. Use the palette and type rules above without exception.
3. If the request conflicts with these rules, flag it and ask
before proceeding.The placeholder values above deliberately avoid the cream-serif-terracotta combination that Anthropic's current frontend-design skill flags as an AI default. Replace every value with your real brand, and keep the description specific and under 200 characters, the limit for skills you upload in the Claude app. It is the line Claude reads to decide whether the skill applies, which is why the skill fires whenever the task looks visual, with no need to invoke it by name. If you are still deciding which skills are worth building versus installing off the shelf, our best Claude skills roundup ranks the ones worth your time first, and our guide on how to build a Claude skill covers the SKILL.md format in more depth.
How to install a design skill in Claude and Claude Code
Installing a design skill takes a few minutes in either place. These steps follow Anthropic's help pages as of October 2026.
Turn on code execution
On Free, Pro or Max, go to Settings > Capabilities and turn on Code execution and file creation. On Team and Enterprise, an owner enables Skills and code execution under Organization settings > Plugins & skills.
Zip the folder
Package the brand-guidelines folder, with SKILL.md inside it, as a ZIP file. Keep the folder name the same as the skill name, or the upload fails.
Upload it in the Claude app
Go to Customize > Skills, click +, choose Create skill, then Upload a skill. The skill appears in your list with a toggle, and the same screen is where you switch Anthropic's example skills on or off.
Or drop it into Claude Code
Save it as .claude/skills/brand-guidelines/SKILL.md inside a project (commit it so your team gets it), or under ~/.claude/skills/ to use it in every project on your machine. Type /brand-guidelines to call it by name. For Anthropic's official design skills, run /plugin marketplace add anthropics/skills, then /plugin install example-skills@anthropic-agent-skills.
One catch: Claude Code's documentation notes that skills in your personal folder do not load in Cowork or cloud sessions, so if your team works in both the Claude app and Claude Code, upload the same folder in the app as well. The full details are in Anthropic's guides to using skills in Claude and skills in Claude Code.
Artifact mockups: prototyping before the designer opens Figma
Artifacts are the fastest way to turn a vague design idea into something you can actually click through. Ask Claude to build a mockup as an artifact and you get a live, previewable interface — not a static image, not a wireframe description — that you can iterate on in plain English: "make the sidebar collapsible," "try a card layout instead of a table."
The practical use case is the first draft. Before you brief a designer or a developer, build the mockup yourself in an afternoon. It forces you to make decisions about layout and hierarchy that are much cheaper to make in a Claude artifact than in a client meeting, and it gives whoever builds the real thing a concrete starting point instead of a page of adjectives.
Build a clickable mockup as an artifact for [product/feature]. Users: [who uses this and why] Core screens: [list 2-4, e.g. dashboard, settings, detail view] Aesthetic: [reference the brand-guidelines skill if you have one] Requirements: - Use realistic placeholder content, not "Lorem ipsum" - Include empty states and at least one error state - Make it responsive down to mobile width - After building, list 3 open design questions I should decide on before this goes to a developer.
This is also where a brand skill and a frontend design skill compound — reference both in the same prompt and the mockup comes out on-brand and intentionally styled on the first pass, instead of needing three rounds of "more like our brand" feedback.
Treat the artifact as disposable in the best sense. Nobody is precious about a mockup that took twenty minutes to produce, which means you can throw away a direction that is not working without the sunk-cost feeling that comes from a designer having spent a day on it. That freedom to discard bad ideas quickly is the actual productivity gain — not that Claude replaces a designer, but that it makes exploring three directions as cheap as exploring one.
Claude Design or a design skill: which do you need?
Use Claude Design when you want Claude to produce a finished visual, such as a design, prototype, slide deck or one-pager, in your brand. Use a design skill when you want the same taste and brand rules to follow you everywhere else Claude works, including Claude Code, written documents and the API. Most teams end up using both.
Claude Design launched in April 2026 as a separate Anthropic Labs product at claude.ai/design. Since September 16 it also works inside every Claude conversation, where it can draw on your files, context and connectors, and on October 8 Anthropic took Docs, Slides and Design out of beta on every plan, including Free. The standalone site closes on December 14, 2026. After that, claude.ai/design redirects to Claude, and chats and comments left in the standalone version are deleted. If your team built design systems there, Anthropic's migration guide covers moving them over from the Artifacts page.
Design systems are Claude Design's version of a brand skill. At launch, Anthropic said Claude Design builds a design system for your team by reading your codebase and design files, so later projects pick up your colors, typography and components automatically. Inside Claude, you choose a design system from the design system menu when you make a design or deck, and an owner can set an organization default. Finished designs export to PowerPoint, PDF, Canva and standalone HTML. If the deck has to live in your company's PowerPoint template, Claude for PowerPoint builds it inside the file instead.
| Claude Design | Design skill | |
|---|---|---|
| What it is | A design tool inside Claude that makes designs, prototypes and decks as artifacts | A folder with a SKILL.md file that Claude loads when a task matches |
| Where it works | Claude conversations on web, desktop and mobile | The Claude app, Claude Code and the API |
| How it holds your brand | A design system you pick from a menu | Rules, hex codes, fonts and examples written into the file |
| Best for | Visual first drafts, decks and prototypes you share or export | Taste and brand rules that must carry into code, copy and every other output |
| Plans (October 2026) | Every plan, including Free | Every plan in the app; Claude Code needs a paid plan |
The two stack rather than overlap. A design system is something you choose inside Claude Design, while a SKILL.md file travels anywhere you can put a folder, including the code repository your developers work in. Write your brand once as a skill, set up a matching design system, and the deck from Claude Design, the landing page from Claude Code and the email copy from a regular chat all follow the same rules.
Common mistakes that break a design skill before it starts
Most design skills fail for the same handful of reasons, and all of them are fixable in the SKILL.md file itself, not in the prompt you write on top of it.
The first mistake is writing rules with no examples. "Use a bold typographic hierarchy" means nothing to a model without a concrete reference — name actual typefaces, actual hex codes, actual do/don't pairs. The second is cramming everything into one giant skill instead of splitting frontend behavior, brand rules, and mockup conventions into separate files that each load only when relevant — a bloated skill slows Claude down and makes the rules harder to enforce consistently. The third is skipping the "when to use this" description at the top of the file, which is the main thing that decides whether the skill fires automatically at all.
The fourth, and the one that costs teams the most rework, is treating the skill as a one-time write. Brand guidelines change, product screens get added, taste evolves — a design skill that nobody revisits after the first quarter drifts out of date the same way a stale style guide does, except now it is quietly steering every artifact your team produces. Review it on the same cadence you would review an actual brand book, and version it in your repo so changes are visible instead of silent.
Where design skills fit next to your content workflow
Design skills rarely work in isolation. The same brand-voice skill that keeps your landing pages on-brand should also be shaping the copy that goes on them — see our Claude for content creation guide for the writing side of this same consistency problem. Build both skills once, reference them together, and every asset that leaves your team — visual or written — reads like it came from the same place.

Want the skills built for you and updated weekly?
- 1,300+ non-technical professionals learning together
- Claude, Claude Cowork & Claude Code training
- The full 550+ prompt & skill Vault included with Premium
- A weekly live call to get unstuck
Where to start this week
Pick one: if you keep briefing the same visual direction over and over, write the brand-guidelines skill above with your real values. If every UI request comes back generic, install or write a frontend design skill and force one aesthetic decision per project. If what you mostly need is decks and visual first drafts, open Claude Design and set up a design system there first. Whichever you pick, the win is the same — you stop re-explaining taste and start reusing it. For the broader picture of what skills can automate beyond design, our Claude Skills primer is the right next stop.
Frequently Asked Questions
Do Claude design skills work on the free plan?
Yes. As of October 2026, skills, artifacts and Claude Design are available on every Claude plan, including Free, as long as code execution and file creation are turned on in Settings. Claude Code is the exception and needs a paid plan; our Claude pricing guide covers what each plan adds.
What is the best Claude skill for frontend design?
Start with Anthropic's official frontend-design skill, which sets the visual direction before Claude writes any UI. Add web-artifacts-builder when a mockup needs React components, state or routing, and pair both with a brand skill so the output matches your company instead of a generic theme. For community-built options and where to find them, see our guide to the Claude skills marketplace.
Can I turn my company's design system into a Claude skill?
Yes, and it is one of the most useful skills a design or marketing team can build. Put the rules Claude must always follow (colors, type scale, spacing, component do's and don'ts) in SKILL.md, and move long token lists or component specs into a separate reference file in the same folder that the skill points to, so Claude reads them only when a task needs them.
Can Claude design skills replace a designer or Figma?
No. Design skills and Claude Design are strongest at first drafts: getting a clickable mockup, a deck or three competing directions in front of people in an afternoon. A designer still owns the final system, the edge cases and the judgment calls, and a good skill makes their decisions repeatable rather than replacing them.
Join the Academy
1,300+ professionals, the courses, the full Vault, and a weekly live call.
Join the AcademyGrab the playbook
The Claude Starter System — free PDF to your inbox.