brandlisted

# Establish or audit the brand A factory that ships UI without a brand ships templates. This skill gives the product a **deliberate, specific** visual and verbal identity so everything built afterwards looks intentional. It either **audits and extends** an existing brand in its own idiom, or **commits to one direction** — never a vague "clean minimal" default that means nothing. Run it two ways: as a **delivery skill** when a ticket asks for brand work (branch, implement, evidence, submit like any other ticket), or as a **lore seed** when you want the brand to govern future work — `suggest_lore` it so every later ticket inherits it. This skill owns the *identity* (direction, palette, type pairing, voice). The **structural** layer it feeds into — the three-tier token architecture and component state specs — lives in the `design-system` pack; the *visual execution* of surfaces lives in `frontend-design`. Keep `SKILL.md` lean and load the craft depth on demand: | Topic | Reference | |-------|-----------| | Colour system (tiers, 60/30/10, `oklch` tokens, contrast) + typography (pairing, fluid scale) | `references/color-and-typography.md` | | Voice (spectrums, traits, do/don't), messaging hierarchy, consistency/approval checklist | `references/voice-and-messaging.md` | ## Steps 1. **Consult and detect, in parallel.** Call `search_lore` (Memory MCP) for any existing brand, positioning, voice, or design ADRs. In the repo, look for `BRAND.md`, `tokens.css`, a `styles/toke