# ADR-100 Visual Design via shared/theme-v2.css Token Presets, Outside Ponytail's Scope ## Status Accepted, 2026-07-02. ## Status History ```yaml status_history: - date: 2026-07-02 status: Proposed changed_by: hkl reason: All PWAs converged on one look (navy/orange Recce template or flat black); visual design was being stripped as "unrequested complexity" by always-on ponytail changed_via: adr-kit (360lm) - date: 2026-07-02 status: Accepted changed_by: hkl reason: theme-v2.css shipped with 5 presets; Hub pilot (ember-v2) executed with screenshot-critique loop (VCC Phase 5) changed_via: adr-kit (360lm) ``` ## Context Every new PWA inherited the same hard-coded palette from the style guide (navy `#0f172a` + orange `#f97316`, or Hub's flat black), producing a uniform "template" look. Two forces made this worse: (1) the pre-split style guide prescribed exact hex values per §2, so scaffolding copied them verbatim; (2) always-on ponytail (CLAUDE.md) treats unrequested additions as waste, and visual polish was routinely classified as such. PWAs already consume CSS custom properties (`--bg/--card/--accent/--radius/--font` …) consistently, so a token layer can restyle without structural rewrites. Affects: all PWAs, the /new-pwa scaffolding flow, and shared/ (ADR-079). ## Decision - Visual identity comes from **`/shared/theme-v2.css`**: named presets selected per app via ``, linked AFTER the app's inline `