brandlisted

# brand: a per-project skin for cards and reports Output = a small committable `.readable/` dir at the project root (ONLY at a project root, never `~/.claude` or `$HOME`: config dirs are not projects). From then on `/report` reskins automatically, and chat cards do too (the session hook announces the dir at session start; an app restart lets other sessions pick up a brand created mid-session). Since 4.13.1 the card server never guesses a brand across open projects: a call without an announced `brand` renders stock, so parallel branded projects cannot leak into each other. ## 1. Detect before asking Search the repo for an existing identity, in this order; quote what you find to the user before generating: 1. Design tokens: `**/tokens.css`, `**/design-system/**`, CSS custom props in the main stylesheet, `tailwind.config.*` color scales. 2. `DESIGN.md` / `BRAND.md` / brand guidelines docs. 3. Logos: `media/brand/`, `public/*.svg`, favicon SVGs. Prefer a mark that uses `currentColor` (theme-flips for free). 4. Fonts: `@font-face` files in the repo, or the families the site loads. If ≥ a primary/accent color and a light-or-dark character are found, generate directly. Otherwise interview with AskUserQuestion, ONE batch: accent color (offer 3 sensible hues + custom hex), light surface character (pure white / warm cream / cool gray), dark base (ink navy / graphite / near-black), wordmark text + optional logo path, one tone word (serious/friendly/technical — store it, it guides f