What problem does it solve? Game teams often jump into building UI without a shared contract for how the game should look and behave, leading to inconsistent HUDs, menus, and input handling. This Skill facilitates a structured discovery process that captures the developer's vision and distills it into two authoritative specification documents. ## Core Features & Use Cases - Dual specification output: Produces DESIGN.md (visual identity tokens per the Google Labs spec: colors, typography, spacing, components) and EXPERIENCE.md (information architecture, HUD behavior, input schemes, game feel, accessibility, player journeys). - Facilitated discovery workflow: Elicits decisions from the developer through brain dumps, creative tools (HTML color themes, design directions, Excalidraw wireframes, key-screen mocks), and named-protagonist player journeys rather than imposing design choices. - Validation and review: Offers an opt-in reviewer gate with parallel subagent lenses (rubric walker, accessibility, HUD legibility) that produce consolidated HTML and Markdown validation reports. - Use Case: A developer says "help me plan the game UX" for a roguelike; the Skill walks them through form factor, input schemes, and HUD diegesis, then delivers final DESIGN.md and EXPERIENCE.md files ready for architecture and story development. ## Quick Start Ask the assistant to help you plan the game UX and design the HUD for your game, then answer its discovery questions about platforms, input schemes, and player journeys.