Frontend Design (anthropics) vs Web Artifacts Builder (anthropics)
Frontend Design (anthropics) and Web Artifacts Builder (anthropics) are both Visual skills, so an agent choosing between them is matching on descriptions that overlap. Here is where they actually diverge.
Frontend Design
anthropics/skills
Deciding how a UI should look and feel before you build it: typography, colour, hierarchy, and escaping the default templated appearance.
7 scenarios in the bank answer to it
Web Artifacts Builder
anthropics/skills
Ambitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
8 scenarios in the bank answer to it
What is the difference between Frontend Design (anthropics) and Web Artifacts Builder (anthropics)?
- Frontend Design (anthropics)
- Deciding how a UI should look and feel before you build it: typography, colour, hierarchy, and escaping the default templated appearance.
- Web Artifacts Builder (anthropics)
- Ambitious claude.ai artifacts with many moving parts: React, Tailwind, component libraries, real state and routing rather than a single static page.
Should I use Frontend Design or Web Artifacts Builder?
The clearest answer is a situation each one is unambiguously right for. Both of these are drawn from the game's question bank.
Reach for Frontend Design when
Your app works fine, but every screen looks like the same generic template every other AI app ships with. You want it to feel designed.
"Doesn't read as templated defaults" is frontend-design's whole reason to exist: aesthetic direction, typography, intentional choices for UI you're building. canvas-design makes art files, not app screens.
Reach for Web Artifacts Builder when
You're building a small claude.ai artifact that needs tabs, a search box, saved state, and three views of the same data.
Multi-component, stateful, routed artifacts are web-artifacts-builder's stated territory (React + Tailwind + shadcn/ui). Simple one-file artifacts don't need it — tabs, state, and views do.
What they have in common
Both are filed under Visual, the axis along which they collide. That shared ground is what makes an agent pick between them on description alone — and what makes it pick wrong.
Nearby comparisons
Reading the difference is not the same as spotting it at speed. That is the game.
Today's session