Algorithmic Art (anthropics) vs Theme Factory (anthropics)
Algorithmic Art (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.
Algorithmic Art
anthropics/skills
Art that is generated rather than drawn: flow fields, particle systems, seeded randomness you can re-roll and tune. Code is the medium.
2 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 Algorithmic Art (anthropics) and Theme Factory (anthropics)?
- Algorithmic Art (anthropics)
- Art that is generated rather than drawn: flow fields, particle systems, seeded randomness you can re-roll and tune. Code is the medium.
- 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 Algorithmic Art 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 Algorithmic Art when
You want a header image for your blog that is different on every page load, generated from a seed you can re-roll until you like one.
canvas-design is the close call, because it also produces images. The difference is authored versus generated: 'different every load, from a seed you can re-roll' describes a system that makes images, not one composed image. That is algorithmic-art. Ask for exactly one poster and canvas-design wins instead.
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