Brand

Brand

Own the project's durable human-readable brand meaning and approved identity assets. Existing approved guidance is authoritative unless the user explicitly changes it. Keep implementation tokens and product UI implementation outside this semantic identity result.

Workflow

1. Inspect existing brand guidance, identity assets, product surfaces, language/message evidence, and asset conventions before proposing change. Do not infer a brand from an industry/style catalogue.
2. For a new or materially revised identity, define only what current evidence/approval establishes: audience, positioning, voice/personality, messaging/claims, semantic color roles, typography direction, imagery, logo constraints, icon language when needed, and prohibited treatments. Read language and messaging when that branch is material. Use the minimal brand scaffold only when the project lacks an existing source of truth.
3. For color or typography decisions that require reusable depth, read color palette management or typography specifications only when that branch is active.
4. For logo/corporate-identity work, read only the relevant logo design, corporate identity design, and logo usage rules. Explore from the current brief/evidence rather than a bundled style database.
5. For custom icon language, read icon design and define only the grid, stroke/fill, corners, optical sizing, naming, and export behavior the identity needs.
6. For asset organization/review, preserve the project's existing convention; read asset organization only when organization itself is unresolved. Do not impose generic filenames, dimensions, formats, or size limits.
7. For an on-brand review, use consistency checklist and approval checklist only when their deeper checks are useful. Report evidence and the smallest correction, not taste alone.

Decision rules

• Prefer project/user evidence over generic color psychology, industry stereotypes, trend catalogues, brand-archetype formulas, or AI-prompt keyword lists.
• Use semantic color roles in guidance; exact implementation values belong to the confirmed implementation contract.
• Define accessible foreground/background pairs and supported theme behavior.
• Keep logo lockups, clear space/minimum-size rules, prohibited transformations, and approved variants explicit only when they are actually established for this brand.
• Do not claim an asset, claim, tagline, differentiator, or message is approved without evidence/approval.
• Derive visual exploration from the confirmed brief; do not maintain a parallel prompt/style catalogue.

Durable destination

Preserve the project's existing brand source-of-truth location and asset conventions when they exist. Do not invent a default docs path, registry, manifest, or repository layout merely because Brand needs durable guidance.

When no durable destination exists, return the proposed brand source plus the unresolved destination/authority boundary rather than silently choosing one. Persistence mechanics do not own Brand semantics.