PlugWiki

frontend-design: Anthropic's Claude skill for less generic UI

Anthropic's design skill. It makes Claude plan a look for your page, check it against stock AI styles, then build and critique it.

Installs
1.1M
on skills.sh
Stars
186.4K
on GitHub
Files
1
besides SKILL.md
Updated
Oct 2026
last repo commit

frontend-design makes Claude work like a design lead. It picks a palette, type and layout from your subject, checks that plan against a list of stock AI looks, and only then writes the code.

The current text is a September 2026 rewrite. It no longer bans Inter or purple gradients, as the 2025 version did. It now names five looks to avoid unless your brief asks for them, such as cream with terracotta accents, near-black with one acid accent, and rows of identical rounded cards. It also asks Claude to screenshot and critique its own work when it can.

There are two copies of the same file. In Claude Code, install the plugin from claude-plugins-official with the command in the install box. The anthropics/skills copy suits the skills CLI, Codex, Cursor, Claude.ai upload or the API. Do not install both in Claude Code, or you load the skill twice.

The skill is one Markdown file with no scripts. It guides taste, but it does not guarantee it: Claude still invents copy, and users report new habits such as pill-shaped buttons. See UI UX Pro Max, Impeccable or Taste Skill for other approaches.

Good for

  • Developers who ask Claude Code for landing pages, dashboards or settings screens
  • Founders and solo builders shipping a UI without a designer
  • Designers who want Claude to follow a brief instead of its usual defaults
  • Teams that want an Anthropic-maintained design prompt with no scripts to review

Install frontend-design

Claude Code

  1. 1

    Copy this prompt.

    Install the frontend-design skill in Claude Code. Run this command:
    
    claude plugin install frontend-design@claude-plugins-official
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one method. The plugin and the example-skills bundle both contain frontend-design, so installing both loads it twice. Inside a session, /plugin install asks which scope to use. The skills CLI installs into the project by default and takes -g for a global install.

From the vendor's docs. Source.

What's in the skill

When it loads

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Sections in SKILL.md

  1. Ground your designs in the subject matter
  2. Design principles
  3. Process: plan, review against the brief, build, critique
  4. Restraint and self-critique
  5. More on writing in design

Key facts

Author
Anthropic
Skill folder last changed
2026-09-03 (September 2026 rewrite)
Installs on skills.sh
1,062,006 as of 2026-11-01

What it includes

  • Claude acts as the lead at a studio known for distinct work

    The skill opens by casting Claude as a design lead whose client rejected templated proposals. It asks for deliberate, opinionated choices on palette, type and layout.

    Try: “Build a landing page for a ceramics studio.”

    Role: studio design lead

  • Starts from your subject, audience and real content

    If your brief does not say what the product is, Claude proposes a subject, audience and main job and confirms it. It takes visual cues from the industry's materials and vernacular, and uses real content instead of filler.

    Try: “Design a booking page for a vet clinic.”

    Ground the design in the subject

  • Rules for the hero, type, structure and motion

    Open the hero with the most characteristic thing in the subject's world. Use one or two clearly different type families, lines under about 80 characters, and motion sparingly. Skip headline accent words, ALL-CAPS labels and 01/02/03 markers unless they carry meaning.

    Try: “Make the hero feel specific to a bike repair shop.”

    Design principles

  • Plan tokens and layout, check for AI looks, then code

    Claude writes a plan with 4 to 6 named hex colors, typefaces and roles, and an ASCII wireframe. It checks the plan against five named AI looks and revises anything generic, then codes. Your brief's own words always win.

    Try: “Plan the design first, then build the dashboard.”

    Process: plan, review, build, critique

  • One bold element, a quality floor, and a screenshot review

    Claude keeps one bold element and the rest quiet. The quality floor is responsive layout, visible keyboard focus, reduced motion, accessibility and a harmonious palette. It screenshots and critiques its work if the environment allows, and removes one accessory.

    Try: “Review your page at phone width and fix what looks off.”

    Restraint and self-critique

  • Treat copy as design content

    Copy uses the user's vocabulary, not the system's. Buttons use active verbs such as Save changes, the same action keeps one name through a flow, errors explain without apologizing, and empty states invite action.

    Try: “Write the empty state and error messages for the billing screen.”

    Writing in design

From the official docs

What people say

People like that it plans a distinct look first, and complain that it leaves new tells of its own.

What people like

  • A side-by-side test found it plans a product-specific look instead of the model's default.
  • A prompt reviewer called its list of named defaults the form that works on current models.
  • It adds a quality floor: responsive layout, keyboard focus and reduced motion.

Common complaints

  • It leaves its own tells, such as sans titles mixed with serif italics.
  • Pill-shaped buttons still showed up on about half of generated pages in one user's eval.
  • It still invents copy, clients and prices.
  • Some readers find the prose vague, and it does not name the default typefaces to avoid.

In their words

1 more quote

Examples

  • Dashboard for a consumer app (plugin README example).

    Create a dashboard for a music streaming app

    Source
  • Startup landing page (plugin README example).

    Build a landing page for an AI security startup

    Source
  • Settings screen (plugin README example).

    Design a settings panel with dark mode

    Source
  • Single-file page from Paralect's side-by-side skills test.

    Build a landing page for Hourglass, a time tracker for freelance designers. One index.html file, no build step.

    Paralect reports the skill planned a product-specific look, chose a condensed typeface, and fixed a headline bug and mobile overflow after screenshots.

    Source
  • Steer away from known defaults, from Anthropic's Opus 5.5 guide pattern. Works alongside the skill.

    Output a vanilla HTML/CSS personal website with placeholder data. Do not use a cream or off-white background, italic accent words in headlines, numbered "01/02/03" section labels, monospace labels, or pill-shaped buttons.

    Source
  • Give the skill a real brief so it can ground the design in your subject.

    Use the frontend-design skill. Build a pricing page for a ceramics studio's weekend workshops. Audience: beginners. Keep it to plain HTML and CSS, and check it on a phone-width screen.

Releases

active The skill was rewritten twice in 2026, most recently on 2026-09-03, and the plugin manifest changed on 2026-10-26.

  • Original text 2025-11-12: Published with Anthropic's launch post as a plugin. A short prompt on typography, color, motion and backgrounds that steered away from Inter fonts and purple gradients.
  • June 2026 rewrite 2026-06-09: Rewritten with new headings (PR 1293), about 1,336 words. The plugin copy followed on 2026-06-15 and the plugin reached 1.1.0 on 2026-06-18.
  • September 2026 rewrite 2026-09-03: PR 1713, avoid generic design defaults. The current text, about 1,500 words, with a plan step and five named AI looks to avoid. The plugin copy matched it on 2026-09-01.
  • Plugin 1.1.1 2026-10-26: The plugin manifest got an explicit version. The same day the claude-code copy was deleted, and its marketplace now installs from claude-plugins-official.

Questions

How do I install frontend-design in Claude Code?

Use the plugin: run /plugin install frontend-design@claude-plugins-official in a session and pick a scope. Claude Code adds the official marketplace itself on its first interactive start. In a script, run claude plugin install frontend-design@claude-plugins-official, and add the marketplace first with claude plugin marketplace add anthropics/claude-plugins-official on a fresh machine.

The older id frontend-design@claude-code-plugins still works. That copy was deleted on 2026-10-26 and now installs from claude-plugins-official.

Skill or plugin: which copy should I install?

In Claude Code, install the plugin. It is the same SKILL.md, wrapped with a manifest (version 1.1.1) so Claude Code can update it. The anthropics/skills folder is the plain skill for the skills CLI, other agents, Claude.ai upload and the API.

The two SKILL.md files were byte-identical on 2026-11-02, but they are separate copies and can drift. Our plugin page covers the package.

Can I install it two ways by mistake?

Yes, and you should avoid it. The example-skills plugin from anthropics/skills bundles 12 skills including frontend-design, so installing it next to the official plugin loads the skill twice. Open issues on anthropics/skills report that bundles duplicate skills and context.

Pick one route. If you only want this skill, use the official plugin or the skills CLI command, not example-skills.

Does it work in Claude.ai?

Possibly already. Anthropic's skills README says its example skills are available on paid Claude.ai plans, but Anthropic's help pages only name the document skills by name, so check Customize > Skills first. If frontend-design is missing, zip the frontend-design folder and upload it there, with code execution turned on in Settings > Capabilities.

Skills you add do not sync between Claude.ai, Claude Code and the API. Add it on each one.

Does it work with the Claude API, Codex or Cursor?

With the API, upload it as a custom skill through /v1/skills and call it with the code execution tool. It is not one of the built-in API skills, which are pptx, xlsx, docx and pdf.

For Codex, Cursor and many other agents, the skills CLI command in the install box installs the anthropics/skills copy. Anthropic documents only its own products, so treat other agents as supported by the CLI, not by Anthropic.

Is it safe to install?

Yes, as far as the files go. The folder holds a Markdown file and an Apache 2.0 license, with no scripts and no network calls. skills.sh shows Gen Agent Trust Hub, Socket and Snyk audits as pass, and no security advisories are published for the repos.

The skill can only steer what Claude writes. Claude still edits files under your client's normal permission prompts. Anthropic's README adds that these skills are for demonstration, so test before you rely on them.

Does it really change what Claude builds?

Yes, but the evidence is thin. Anthropic's launch post shows before and after screenshots and no metrics. In one side-by-side test, Paralect reports that Claude without the skill produced the default look almost exactly, and with the skill planned a product-specific one. The test used the same brief for 8 skill packs and did not state the model.

The same test found the agent still invents copy, clients and prices. One user's small eval found pill-shaped buttons on 10 of 21 pages. Read the result before you ship it.

What changed in the 2026 rewrite?

The November 2025 text, about 400 tokens, told Claude to avoid Inter, Roboto and purple gradients and to pick a bold direction. The September 2026 rewrite (PR #1713) is about 1,500 words. It asks Claude to ground the design in your subject, write a plan before coding, and avoid five named AI looks.

It also sets a quality floor: responsive layout, visible keyboard focus, reduced motion and accessibility. The plugin README and marketplace description still use the 2025 wording, so they no longer match the skill.

frontend-design vs ui-ux-pro-max, Impeccable and Taste Skill?

frontend-design is a single prompt with no data or tools. UI UX Pro Max looks up styles and palettes in a database with Python scripts. Impeccable describes itself as a design vocabulary with commands such as polish, critique and audit. Taste Skill describes itself as art direction with reference images and a browser check.

In Paralect's test, UI UX Pro Max is pitched for a consistent, accessible system quickly, Taste Skill for landing pages and portfolios, and Impeccable for use before you ship. web-design-guidelines is a review skill for existing UI code.

Information

updated Nov 2, 2026

Folder
skills/frontend-design

anthropics/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 21
  1. Using Skills in Claude · support.claude.com
  2. anthropics/skills README · github.com
  3. Agent Skills overview · platform.claude.com
  4. Discover and install plugins · code.claude.com
  5. frontend-design on skills.sh · skills.sh
  6. frontend-design | Claude by Anthropic · claude.com
  7. frontend-design plugin README · github.com
  8. frontend-design SKILL.md · github.com
  9. claude-plugins-official frontend-design plugin · github.com
  10. Top design skills for Claude Code in 2026, tested side by side · paralect.com
  11. frontend-design: pill-shaped buttons on about half of generated pages · github.com
  12. anthropics/skills frontend-design folder · github.com
  13. frontend-design commit history · github.com
  14. frontend-design LICENSE.txt · github.com
  15. claude-code commit 10a5141 · github.com
  16. vercel-labs/skills README · github.com
  17. Improving frontend design through Skills · claude.com
  18. frontend-design: avoid generic design defaults (PR 1713) · github.com
  19. Hacker News comment on frontend-design · news.ycombinator.com
  20. frontend-design: name the default typefaces; drop the plan-then-gate script · github.com
  21. Prompting Claude Opus 5.5 · platform.claude.com

Updated Nov 2, 2026.