Frontend Design
Frontend Design is Anthropic's official agent skill for distinctive visual design. It teaches your agent to plan like a design-studio lead, avoid the tired AI-generated look, and critique its own work before shipping. About 1 million installs on skills.sh.
Install
npx skills add https://github.com/anthropics/skills --skill frontend-design
Skill files (1)
- skills/frontend-design/SKILL.md
Quality and security
Frontend Design Review: Anthropic's Official Skill for Interfaces That Don't Look Generated
Most AI-built web pages look the same. A warm cream background, a serif headline, a terracotta accent. Or a near-black page with one acid-green highlight. Or the same rounded SaaS cards with the same soft shadow, whatever the product is. The defaults are so recognizable now that users can spot an AI-made page in a second.
Frontend Design is Anthropic's official answer to that problem. It is the design skill from the team that builds Claude, published in the official anthropics/skills repository, which holds nearly 190,000 GitHub stars. About one million installs on skills.sh make it one of the most-used skills in the whole ecosystem, and its guidance reads like a working design lead, not a checklist.
What is Frontend Design?
Frontend Design is a single SKILL.md that tells your agent to approach every interface as the design lead of a studio known for giving each client a distinct visual identity. The brief is the boss: the subject matter, the audience, and the job the page has to do decide the palette, the typography, and the layout. Where the brief leaves an axis free, the agent is told to take an aesthetic risk rather than spend that freedom on a generic default.
The skill is unusually honest about what AI-generated design looks like right now. It names the clichés one by one, from the cream-and-terracotta hero to the tracked-out all-caps eyebrow label above every heading, and forbids reaching for them unless the brief genuinely asks for that look.
Key Features
1. A named list of looks to avoid
The skill catalogs the most common AI-design tells: the cream background with terracotta accent, the near-black page with acid green, the broadsheet layout with hairline rules, the identical SaaS card kit, the gradient wash used as decoration. Naming them makes them avoidable.
2. Subject-first design direction
Before any code, the agent must ground the design in the subject matter: what the product is, who it is for, and what the page must do. A toy for children and a dashboard for financial analysts should never receive the same treatment, and the skill says so plainly.
3. A two-pass process: plan, then build
First comes a compact design plan with a token system for color, type, layout, and principles, sketched with short prose and ASCII wireframes. The plan is reviewed against the brief for anything that reads as a generic default, revised, and only then turned into code.
4. Typography as personality
Type carries the personality of the page. The skill gives concrete rules: one or two families, clearly distinct if two; line lengths under 80 characters; no single-word accent coloring in headlines; no unnecessary labels above content. Copy is treated as design content, not decoration.
5. Restraint and self-critique
Spend boldness in one place and keep everything else quiet. Build to a quality floor without announcing it: responsive down to mobile, visible keyboard focus, reduced motion respected, accessible palettes. The agent is told to critique its own work as it builds, taking screenshots to review when the environment allows.
How It Works
Install it with the skills CLI. The command below pulls just this skill from the official Anthropic repository:
npx skills add https://github.com/anthropics/skills --skill frontend-design
After that, describe the page you want in plain words, including what it is for and who will use it. The agent plans the design first, checks the plan against your brief, then builds the page. Give feedback on the result and it revises the plan, not just the code. It also installs as a Claude Code plugin from the same repository.
Who Should Use Frontend Design?
Anyone who asks an agent to build a landing page, dashboard, prototype, or marketing site should install it. It is especially valuable for founders and solo developers shipping pages without a designer, and for teams tired of every AI-built page looking like the same template. Pure backend work will never trigger it, so it costs nothing to keep installed.
Pricing
Frontend Design is free to install and use. The skill itself costs nothing. One condition matters: the anthropics/skills repository is source-available, not open source. Its license file is proprietary, and use falls under your agreement with Anthropic. You may not copy the materials, keep copies outside Anthropic services, make derivative works, or distribute them. Read the license file before reusing the text elsewhere.
Pros and Cons
Pros: written by the team behind Claude, so the advice matches how the model actually works; the anti-cliché list alone is worth installing; a real two-pass process instead of straight-to-code generation; about one million installs, so the guidance is battle-tested.
Cons: the license is proprietary source-available, not MIT or Apache, which limits redistribution; it is Claude-first in spirit, so results on other agents vary; it cannot fix a vague brief, and it will ask questions instead of guessing; the output still depends on the model following the plan.
Final Verdict
Frontend Design is the single highest-leverage skill for anyone who ships web pages with an agent. It does not add a tool. It changes the taste of everything the agent builds. Install it before your next landing page and compare the result with the last one you shipped. Try it on GitHub: anthropics/skills.



