Theme Factory (anthropics) vs Web Artifacts Builder (anthropics)
Theme Factory (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.
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
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 Theme Factory (anthropics) and Web Artifacts Builder (anthropics)?
- 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.
- 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 Theme Factory 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 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.
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