Theme Factory

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.

A situation it fits

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.
Theme Factory. 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.

3 scenarios in the bank answer to Theme Factory. The rest are in the game.

Skills it gets confused with

These share a family with Theme Factory, which is another way of saying they are the ones you might reach for by mistake.

Knowing what Theme Factory does is the easy half. Telling it apart from the others under time pressure is the game.

Today's session

Theme Factory is part of anthropics/skills. Licence: Apache-2.0. The description above was written for this game, not taken from the skill.

← All skills