Comparison
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 company site is eight years old. The logo, the blue, and the page structure all stay - leadership has been clear about that. Everything else about how it looks is being replaced, and the new pages have to ship.A redesign that preserves the brand, replaces the visual language, and ends in shipped pages is design-taste-frontend's redesign mode: audit the existing tokens and page tree first, then rebuild on top of them. design-review is the near miss - it also works on something already built, but its job is to critique and repair what is there, and here what is there is being thrown away. design-consultation proposes a fresh system and stops before any page exists. frontend-design decides the look without shipping the site.
Reach for Frontend Design when
You are building a settings area with four linked panels from scratch, and you already hate how every AI-built settings page looks.Two genuinely separate jobs. frontend-design first, because 'I hate how they all look' is a question about aesthetic direction and typography that has to be answered before any component exists. web-artifacts-builder second, to assemble four linked panels with shared state. Build first and you will be retrofitting taste onto structure.
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