brand-init
01Command
Initialize the brand pack — read the foundation and existing copy, propose a voice pack with reasoning, seed docs/brand/, and sweep the interface into the string registry.
Scenario-driven UX for coding agents: vision, personas, flows, screens, acceptance scenarios, UX audits, brand voice, and product copy.
Command
Initialize the brand pack — read the foundation and existing copy, propose a voice pack with reasoning, seed docs/brand/, and sweep the interface into the string registry.
Command
Run the brand linter over docs/brand/ and the declared sources — contract, terminology, string consistency, facts, channel limits, bot safety, AI markers and locales.
Command
Recalibrate the brand pack after positioning, personas, pricing or naming changed — propagate the change through terminology, strings and every locale in the same edit.
Command
Single entry point for the verbal identity — status across voice, terminology, facts, channels, strings and locales, then a menu of applicable actions (init, calibrate, update, validate, write, audit).
Command
Write, edit, adapt or humanize copy for a named surface — interface strings, landing and pricing pages, blog, changelog, social posts, store listings, ads, lifecycle email — in the product's recorded voice.
Command
Audit the codebase against scenarios and flows in batches (with full JTBD/story context); depths quick/standard/deep add heuristic, practice, and coverage passes.
Command
Diagnose docs/ux against the current contract — mixed or stale contract versions, unmarked artifacts, files the tooling cannot find, audits with no base.
Command
Design, reverse-engineer, update, or improve user flows — task analysis, mermaid flow diagrams, screen states, wireframes, Figma mockups, heuristic UX evaluation.
Command
Build or update the UX foundation — personas, Jobs to Be Done, customer journeys, user stories (the WHY layer scenarios trace to).
Command
Initialize the full UX chain for this project — the vision (optional), then foundation (personas, JTBD, journeys, stories), flows, screens and scenarios derived from it.
Command
Lint docs/ux for integrity and drift — missing Figma frames, unresolved SCR/story traces, orphans, built screens without coverage, index desync, broken links.
Command
Install the scenario-first hard rule into this project's CLAUDE.md and create the docs/ux/ skeleton.
Command
Update the UX chain after a change to user-facing behavior (same-change rule), or validate a new feature idea against the foundation, flows, and scenarios.
Command
Single entry point for all UX work — status across every layer (vision, foundation, flows, screens, scenarios, audits, brand), then a menu of applicable actions (init, design, update, validate, audit, write copy, plan fixes).
Command
Write the product vision (docs/ux/vision.md) and install the alignment rule into this project's instruction file.