> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yarn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Theme kits

> Define reusable brand systems for typography, color, motion, and overall style behavior.

## Overview

Theme kits are project-wide brand systems, not one-off style tweaks.

Use them when multiple videos need a shared visual identity.

\[insert screenshot of theme kit settings with brand colors, typography, and motion defaults]

## What a theme kit should define

* Primary and secondary typography choices.
* Core color tokens and contrast-safe combinations.
* Default overlay styling behavior.
* Motion and transition baseline.

## Before you start

* Align on brand requirements with your team.
* Choose one reference project that already looks correct.
* Decide what should be global default versus scene-level override.

## Steps

1. Create or open a theme kit.
2. Set typography and color foundations.
3. Configure default overlay and transition behavior.
4. Apply the kit to a sample project and review.
5. Iterate until baseline quality is reliable.
6. Roll out to active projects with clear change communication.

\[insert screenshot of two projects using the same theme kit with consistent visual style]

## Check your result

* Projects share a recognizable brand identity.
* New videos start with usable defaults.
* Overrides are exception-based, not the norm.

## Troubleshooting

### Projects look different despite same kit

Check for local overrides and legacy scene-level style patches.

### Kit update caused regressions

Version theme changes and test on one project before broad rollout.

### Some elements ignore kit defaults

Element-level custom styles can supersede kit behavior; reset where appropriate.

## Next

Finalize readability and accessibility with [Captions](/captions).