What problem does it solve? Frontend stories often get implemented without a clear design specification, causing inconsistent screens, missed states, and divergent UI patterns across multiple frontend repositories. This Skill produces a structured design brief before any UI story is implemented. ## Core Features & Use Cases - Structured Brief Template: Generates a complete design brief covering context, screens, data sources, interactions, states (empty/loading/error/success), design tokens, components, accessibility, and responsive behavior. - Cross-Repo Consistency: Enforces shared UI patterns (such as the Picker rule) across the lore-admin, session-gm, and session-player frontends. - Design Token Governance: Checks whether existing design tokens suffice or new ones are needed, with justification for cross-repo additions. - Use Case: Before implementing STORY-042 (a new encounter picker screen), the designer profile runs this Skill to write a brief in .scrum/repos/<repo>/designs/STORY-042-brief.md, referencing existing tokens and flagging the new <EncounterPicker> component spec. ## Quick Start Ask the designer profile to create a design brief for a specific story, for example: create a design brief for STORY-042 before implementing the encounter picker screen.
