Design Taste Frontend (leonxlnx) vs Frontend Design (anthropics)
Design Taste Frontend (leonxlnx) and Frontend Design (anthropics) are both Visual skills, so an agent choosing between them is matching on descriptions that overlap. Here is where they actually diverge.
Design Taste Frontend
leonxlnx
Builds the persuasion surface of a website — a launch page, a personal or studio portfolio, a visual overhaul of a site that already exists — and ships the working page, steered hard away from the templated look a model reaches for by default: a stated aesthetic read of the brief, a committed type and colour language, and motion that has to justify itself. Its scope stops at surfaces meant to be scrolled and read; dashboards, data grids, and multi-step wizards are handed off to a product-UI system rather than restyled.
4 scenarios in the bank answer to it
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.
8 scenarios in the bank answer to it
What is the difference between Design Taste Frontend (leonxlnx) and Frontend Design (anthropics)?
- Design Taste Frontend (leonxlnx)
- Builds the persuasion surface of a website — a launch page, a personal or studio portfolio, a visual overhaul of a site that already exists — and ships the working page, steered hard away from the templated look a model reaches for by default: a stated aesthetic read of the brief, a committed type and colour language, and motion that has to justify itself. Its scope stops at surfaces meant to be scrolled and read; dashboards, data grids, and multi-step wizards are handed off to a product-UI system rather than restyled.
- Frontend Design (anthropics)
- Deciding how a UI should look and feel before you build it: typography, colour, hierarchy, and escaping the default templated appearance.
Should I use Design Taste Frontend or Frontend Design?
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 Design Taste Frontend when
The direction for the studio's new site was agreed weeks ago and written down: editorial, warm greys, a serif display face, almost no motion. Someone now has to build the thing — hero, work grid, about, contact, one long scroll.
The deciding is done, which removes both skills that decide: frontend-design settles look and feel before the build, and design-consultation proposes a whole system from scratch. What is left is the build, on exactly the surface design-taste-frontend is scoped to — a portfolio site that has to hold a committed type and colour language instead of drifting back to the default. web-artifacts-builder also builds, but it is aimed at claude.ai artifacts with real state and routing, and this is one scrolling site.
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.
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