# How do you make ten generated pages look like one product?

Canonical URL: https://bestskillsforclaude.com/en/skills/theme-factory
Language: en
Skill: theme-factory
Publisher: Anthropic (https://github.com/anthropics)
Source: https://github.com/anthropics/skills/tree/main/skills/theme-factory
License as stated by the publisher: Apache 2.0
Runtime: Claude apps and Claude Code
Category: Design and interface
Last reviewed: 2026-08-05

Generate the theme once, then apply it, instead of describing the style ten times.

## Short answer
The theme-factory skill produces reusable themes, such as colour, type and component styling, that can be applied consistently across generated work. It solves the problem where every new page or artifact is individually attractive and collectively incoherent.

Best for: Anyone generating several related interfaces, artifacts or documents that must feel like one system.
Skip it if: You are producing exactly one thing, where a theme is overhead with no payoff.

## What to remember
- Themes make consistency mechanical instead of a matter of remembering.
- Deciding the theme once is faster than describing the style in every prompt.
- It sits below brand-guidelines: the brand states the rules, the theme implements them.
- Check a theme against two very different layouts, because that is where it breaks.

## What it changes in practice
Generated work drifts because each session re-decides the styling. A theme moves that decision out of the prompt and into an artifact that can be reused and corrected.
It also makes review cheaper. Reviewing a theme once is faster than reviewing the styling of every page that will ever use it.

## Where it disappoints
A theme derived from one screenshot tends to be shallow, capturing colours but missing spacing and rhythm, which are what actually make a product feel coherent.
Complex component libraries with many states still need manual work, because a generated theme rarely covers hover, disabled and error states consistently.

## Install and first run
1. Install it from anthropics/skills under Apache 2.0.
2. Create a theme from an existing product or a described direction, and name it.
3. Build two different pages with the same theme, and compare them side by side before going further.

## Questions
### How is this different from brand-guidelines?
Brand guidelines state the rules for humans and models. A theme is the implementation those rules produce.

### Can I build a theme from an existing site?
Yes, and it is a common starting point, but check spacing and states, which are usually captured poorly.

### Do themes work across documents and interfaces?
Partially. Interfaces benefit most, while document formats still need their own templates.

## Sources
- anthropics/skills on GitHub: https://github.com/anthropics/skills
- anthropics/skills, theme-factory skill directory: https://github.com/anthropics/skills/tree/main/skills/theme-factory

## Other languages
- Spanish: https://bestskillsforclaude.com/es/skills/theme-factory
- Brazilian Portuguese: https://bestskillsforclaude.com/pt-br/skills/theme-factory
- Japanese: https://bestskillsforclaude.com/ja/skills/theme-factory