create-brandlisted

# Brand Identity & Design System — Orchestrator Coordinates 8 specialized agents to transform product context into a brand narrative + AI-readable design system. Capability metadata (routes, prerequisites, load map, artifact contract) lives in [`routing.yaml`](routing.yaml). Agent table + per-route dispatch graphs + pattern-catalog map: [`references/agent-manifest.md`](references/agent-manifest.md). Methodology and history: [`references/playbook.md`](references/playbook.md). **Core question:** Does every visual decision trace back to who we are? ## Critical Gates — load first - **No colors/fonts before strategy.** Visual-agent runs parallel with strategy-agent; orchestrator verifies coherence at merge. - **No Layer 2 before Layer 1 completes.** Token-architect needs visual-agent output; component-token needs token-architect output. - **Critic's cross-element coherence is mandatory.** Radius↔archetype, type↔personality, color↔emotion — the matrix no individual agent can see. - **Stale upstream (>30 days) → generic archetypes.** Recommend re-running `research-icp` if artifact dates are old. - **BRAND.md is prose, DESIGN.md is specification.** Never mix registers. ## Output | File | Audience | Register | Route | |---|---|---|---| | `brand/BRAND.md` | Founders, marketers, copywriters, designers | Prose — brand book | A + B | | `brand/DESIGN.md` | AI coding agents, frontend engineers, design-system consumers | Specification — tables, formulas, exact values | B only | | `bran