SkillsBot.org

Frontend Design Skill

The frontend design skill is Anthropic's instruction set that makes Claude pick a subject, an audience and a deliberate visual direction before it writes any UI code, so the interface does not come out looking templated.

Compared head to head: Frontend Design Skills Compared.

Part of the Anthropic skills collection.

  • License Apache-2.0
  • Installs 1.1M
  • GitHub stars 195.3K
  • Audits 3 of 3 passed

Our hands-on test, by SkillsBot.org

We asked Claude to build a landing page for a sourdough bakery

The frontend design skill visibly changed the design direction. Without it, Claude produced a polished page in the look most bakery sites share: cream background, terracotta accents, an italic serif headline. With the skill, Claude said it deliberately avoided that look and went for enamel blue, a wide heavy grotesque typeface and a Monday-to-Sunday “how a week works” strip built around the actual subscription. Both pages are complete and work on mobile; the skill's version is the one you would remember.

  • InstallWorked3 s with the skills CLI
  • Picked up on its ownYesinvoked frontend-design
  • Time2 min 56 s3 min 38 s without the skill
  • API cost$0.67$0.80 without the skill
  • Output check31 KB, 3 media queries, 3 external URLsWithout: 44 KB, 15 media queries, 1 external URLs

The task, word for word

Build a landing page for Rise & Crumb, a neighbourhood bakery in Leeds that sells weekly sourdough subscriptions (3 plans: £12, £20, £32 per month). Write it as a single index.html file with inline CSS, no build step, no external images. Don't ask me questions; make reasonable choices and finish.

With the skill

Bakery landing page built with the frontend-design skill: cobalt blue hero with a wide black headline, a drawn loaf and a weekly schedule strip

Without the skill

Bakery landing page built without the skill: cream background, serif headline with italic terracotta accent and a loaf illustration
The top of each page at 1280 px. Same prompt, same model. The skill's run rejected the cream-and-terracotta look by name. Full size: with the skill, without.

With the skill

The frontend-design page at phone width

Without the skill

The page without the skill at phone width
Both pages at 390 px. Both runs checked their own mobile layout with headless Chrome. Full size: with the skill, without.
Claude's description of the design choices it made with the frontend-design skill
Claude's report with the skill: it explains the palette, type choice and the one animation it allowed. Open full size.

What it actually did

  1. Invoked frontend-design unprompted, then chose a concrete visual idea (enamel bakeware) before writing code.
  2. Wrote one index.html with an inline SVG loaf, a dated “next bake / order by” ticket computed from today's date, and plans drawn to scale.
  3. Took headless Chrome screenshots at desktop and mobile widths and adjusted loaf sizes and copy after looking at them.

Where it helped

  • A distinctive, coherent look instead of the category default, which is exactly what the skill promises.
  • Design built on the product's real structure: a weekly bake cycle and order cutoff, not generic feature cards.
  • Restraint: one animation, one typeface family, a short palette.

Limits we hit

  • It loaded Archivo from Google Fonts, an external request, though our brief only ruled out external images.
  • Took 2 min 56 s and $0.67; the run without the skill took longer still (3 min 38 s, $0.80) on a fuller page with 15 media queries.
  • Both runs invented business details for the mock-up (a Hyde Park address, delivery areas, “what most people pick”). Replace them before using either page.
  • A single run: another run with the skill could pick a different direction, so judge the approach, not this exact page.

Use it for

  • Landing pages and marketing sites that should not look AI-generated.
  • Redesigns where the brief is “make it feel like us”.
  • Prototypes you will show to a client or stakeholder.
  • Give it a real brief (product, audience, the page's job) to get the most specific result.

One run with the skill and one without, same prompt, fresh folders, Claude Code 2.1.325 in headless mode. How we test skills. Every skill we have tested.

Last updated . The frontend-design skill is made and maintained by Anthropic; SkillsBot.org is an independent directory and is not affiliated with it.

Use frontend-design in Codex, Cursor and GitHub Copilot

frontend-design is a standard Agent Skills folder, so the same files work in other coding agents. Name the agent when you install:

Parts of a skill that rely on Claude Code features, such as subagents or / commands, may behave differently elsewhere. Paths for each agent are in our install guide.

Frontend Design Skill facts

Author
Anthropic (@anthropics)
Repository
anthropics/skills
License
Apache-2.0
Installs
1.1M
GitHub stars
195.3K
First seen on skills.sh
Jan 19, 2026
SKILL.md length
1,477 words
Other files
1

Security audits on skills.sh:

Installs, stars, first-seen date and audits from skills.sh on November 16, 2026. SKILL.md read from GitHub the same day.

What the frontend-design skill does

frontend-design is a single SKILL.md of about 1,500 words from Anthropic's official skills repository. It does not add components or a CSS framework. It changes how Claude approaches a design:

  • Ground the design in the subject. If the brief does not say what the product is, Claude proposes a concrete subject, audience and main job for the page and confirms it before designing.
  • Make deliberate choices. The skill asks for chosen typefaces rather than defaults, a clear type scale, and line lengths under 80 characters.
  • Plan, review, build, critique. Claude drafts a small token system, checks it against the brief, then builds and critiques the result.

In our hands-on test this changed the outcome visibly: the same bakery brief produced an enamel-blue page instead of the cream-and-terracotta look Claude chose without the skill. You can compare it with the other skills we have run in the tested skills list.

What SKILL.md tells Claude

In short, the file asks Claude to work like the design lead of a studio whose client has already rejected anything templated. Its main rules:

  • Start from the subject's world. The industry, materials and vocabulary of the subject are where distinctive choices come from; a toy for children and a dashboard for analysts should look nothing alike.
  • Make the hero the most characteristic thing about that subject, and treat "big number, small label, gradient accent" as a default to avoid unless it is truly the best fit.
  • Type carries the personality: one or two deliberately chosen families, a clear scale, lines under 80 characters.
  • Know the current AI defaults and do not spend design freedom on them: cream backgrounds with a terracotta accent, near-black with one acid accent, identical rounded cards with soft shadows, all-caps labels above every heading.
  • Structure must carry meaning: numbered markers only for real sequences, motion used once and on purpose.
  • Plan first (4–6 named colours, type roles, an ASCII layout sketch), compare the plan with the brief, then build.
  • Critique with screenshots, keep accessibility and mobile as a floor, and remove one accessory before you finish.

It ends with guidance on interface copy: plain, specific words written from the user's side. This is our summary; the full text is in the anthropics/skills repository under the Apache 2.0 licence.

When Claude uses it

The frontend design skill's description tells Claude to use it when building new UI or reshaping an existing one. In Claude Code you can also run it directly by typing /frontend-design; the install guide explains where skills live and how slash commands get their names.

Frontend-design or another design skill?

Several skills in the design and frontend category touch the same work. They answer different questions:

Skill What it handles Choose it when
frontend-design The overall visual direction of a new page or redesign You need a look that fits this brief, not a template
web-design-guidelines Reviewing UI code against Vercel's Web Interface Guidelines You want an audit of accessibility and UX rules in existing code
ui-ux-pro-max A searchable library of styles, palettes and font pairings You want ready-made options to pick from
emil-design-eng Interaction polish: press states, transitions, timing The layout is set and the details need to feel right
review-animations A strict review of animation and motion code You have animations and want them judged

Use one direction-setting skill at a time. Frontend-design, impeccable and ui-ux-pro-max all try to set the look of a page, and their advice can conflict; pair one of them with a review or motion skill instead.

Good to know

  • The frontend design skill is instructions only: no scripts, nothing to install beyond the folder. You can check the file's frontmatter with our SKILL.md validator.
  • The frontend design skill folder includes its own LICENSE.txt (Apache 2.0).

What is in the frontend-design folder

  • SKILL.mdinstructions
  • LICENSE.txt

Frontend Design Skill: FAQ

How do I install the frontend design skill?

Run npx skills add anthropics/skills --skill frontend-design in your project, or copy the frontend-design folder to ~/.claude/skills/frontend-design/. In the Claude apps, zip the folder and upload it under Customize > Skills.

Does the frontend design skill work with React, Vue or plain HTML?

Yes. The frontend design skill is about design decisions, not a framework, so Claude applies it to whatever stack you ask for.

Is the frontend design skill free?

Yes. It is published by Anthropic in the anthropics/skills repository with an Apache 2.0 license file in the skill folder.

Why does my UI still look generic?

Give Claude a real brief: what the product is, who uses it and what the page must do. The frontend design skill asks Claude to propose these when they are missing, but your own answers lead to more specific designs.