Brand Governance
Use this skill when a repository needs brand, voice, naming, or communication consistency.
Goal
Maintain docs/BRAND.md as the source of truth for product identity and communication.
Fixed Clarification Flow
If the user has not clearly specified brand direction, follow this flow before writing:
- Discover existing signals: README, landing copy, UI labels, docs, screenshots, logos, assets, package metadata, and specs.
- Extract confirmed identity, tone, naming, audience, contradictions, and risky assumptions.
- Ask focused questions for material gaps such as positioning, voice, naming, emotional tone, and logo usage.
- Draft brand rules with concrete examples.
- Cross-check with
docs/PRD.md, docs/DESIGN.md, and docs/assets/brand/*.
- Confirm unresolved brand decisions with the user.
- Create or patch
docs/BRAND.md.
BRAND.md Owns
- Tone
- Identity
- Naming
- Copywriting
- Storytelling
- Illustration direction
- Logo rules
- Communication style
Boundary
Do not merge docs/BRAND.md with docs/DESIGN.md.
BRAND.md explains what the product should feel and sound like.
DESIGN.md explains how the UI should be implemented.
Rules
- Preserve existing product language when it is coherent.
- Avoid generic startup copy.
- Keep brand rules usable by agents writing UI copy, docs, release notes, and landing pages.
- Reference
docs/assets/brand/ when logo or identity assets exist.
- Do not invent positioning when product intent is still unclear.
1---2name: brand-governance3description: Use when creating or maintaining docs/BRAND.md as the brand-facing source of truth for tone, identity, naming, copy, storytelling, and visual direction.4---56# Brand Governance78Use this skill when a repository needs brand, voice, naming, or communication consistency.910## Goal1112Maintain `docs/BRAND.md` as the source of truth for product identity and communication.1314## Fixed Clarification Flow1516If the user has not clearly specified brand direction, follow this flow before writing:17181. Discover existing signals: README, landing copy, UI labels, docs, screenshots, logos, assets, package metadata, and specs.192. Extract confirmed identity, tone, naming, audience, contradictions, and risky assumptions.203. Ask focused questions for material gaps such as positioning, voice, naming, emotional tone, and logo usage.214. Draft brand rules with concrete examples.225. Cross-check with `docs/PRD.md`, `docs/DESIGN.md`, and `docs/assets/brand/*`.236. Confirm unresolved brand decisions with the user.247. Create or patch `docs/BRAND.md`.2526## BRAND.md Owns2728- Tone29- Identity30- Naming31- Copywriting32- Storytelling33- Illustration direction34- Logo rules35- Communication style3637## Boundary3839Do not merge `docs/BRAND.md` with `docs/DESIGN.md`.4041`BRAND.md` explains what the product should feel and sound like.4243`DESIGN.md` explains how the UI should be implemented.4445## Rules4647- Preserve existing product language when it is coherent.48- Avoid generic startup copy.49- Keep brand rules usable by agents writing UI copy, docs, release notes, and landing pages.50- Reference `docs/assets/brand/` when logo or identity assets exist.51- Do not invent positioning when product intent is still unclear.
Yipxiyi