Design Taste Frontend (leonxlnx) vs Theme Factory (anthropics)
Design Taste Frontend (leonxlnx) and Theme Factory (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
Theme Factory
anthropics/skills
Put a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.
4 scenarios in the bank answer to it
What is the difference between Design Taste Frontend (leonxlnx) and Theme Factory (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.
- Theme Factory (anthropics)
- Put a consistent look on something already built: pick or generate a colour-and-font theme and apply it across slides, docs, or a page.
Should I use Design Taste Frontend or Theme Factory?
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 Theme Factory when
A small company has a dozen pages and slide decks that look inconsistent; they need someone to quickly give everything the same palette, heading sizes and button looks so the existing materials read like a single brand.
This is theme-factory because the job is to create and apply a consistent visual skin across already-built pages and documents rather than rethinking layouts or crafting new components. The closest wrong option, frontend-design, loses because you’re not inventing a new UI from scratch or deciding structural visual systems for future builds—you’re unifying what already exists. Web-artifacts-builder is incorrect because there’s no new engineering work, component wiring, or routing to implement; it’s purely styling existing assets. Webapp-testing is wrong because the task isn’t about driving or verifying a running application—there’s nothing to test, just a need for cohesive styling.
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