Frontend Design (anthropics) vs Theme Factory (anthropics)
Frontend Design (anthropics) 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.
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
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.
3 scenarios in the bank answer to it
What is the difference between Frontend Design (anthropics) and Theme Factory (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.
- 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 Frontend Design 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 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 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