Style Guide

---
name: style-guide
description: Codify an approved visual language into durable rules, examples, ranges, and exceptions that keep distributed production coherent without freezing creative judgment.
---
# Visual Style Guide

Use when a visual direction must scale across multiple creators, assets, scenes, screens, or Fleet-routed specialists.

## Procedure
1. Inventory recurring visual decisions that need consistency: shape language, palette, value range, materials, lighting, line treatment, typography, iconography, composition, motion, or other project-specific dimensions.
2. Separate hard constraints from preferred ranges and examples so the guide does not turn taste into fake law.
3. Document positive examples and common failure modes for each important rule.
4. Define relationships between systems, such as how environment palette differs from UI palette while still belonging to the same world.
5. Include production constraints such as scale, export formats, naming, resolution, LOD, animation, localization, or engine limits only where they affect visible quality.
6. Record approved exceptions and the principle behind them so unusual work can remain intentional.
7. Make the guide portable and tool-agnostic enough that any eligible Agency profile can apply it on another node without hidden local context.
8. Review the guide against real work and revise rules that cannot distinguish good output from merely compliant output.

## Decision rules
- A style guide should reduce contradictory decisions, not eliminate professional judgment.
- Use examples to clarify principles, not to create templates that every artifact must mimic.
- Do not encode machine-local paths or tool settings unless they are truly part of the production contract.
- Update the guide when the approved visual language evolves; stale rules are worse than missing rules.

## Quality gate
The guide is effective when independent creators can produce recognizably coherent work, hard constraints and flexible ranges are distinguishable, examples clarify rather than constrain, and the document remains usable across tools and Fleet nodes.