What problem does it solve? Game teams often jump into building UI and HUDs without a written contract for how the game should look and behave, causing inconsistent screens, rework, and misalignment between design and engineering. This Skill runs a structured elicitation workflow with the developer and produces two canonical specification documents that downstream architecture and story work can consume. ## Core Features & Use Cases - Dual specification output: Produces DESIGN.md (visual identity tokens per the Google Labs design.md spec) and EXPERIENCE.md (information architecture, HUD behavior, input schemes, game feel, accessibility, player journeys) that cross-reference each other by token name. - Guided discovery with creative tools: Elicits decisions from the developer without imposing taste, rendering HTML color themes, design directions, Excalidraw wireframes, and key-screen mockups on demand. - Validation and review: Offers an opt-in reviewer gate with parallel subagent lenses and a rubric walker that checks flow, token, component, and state coverage, emitting HTML and Markdown validation reports. - Use Case: A developer says "help me plan the game UX" for a roguelike; the Skill interviews them about platforms, input schemes, and HUD diegesis, then distills a final DESIGN.md and EXPERIENCE.md ready for the game architecture skill. ## Quick Start Ask the assistant to help you plan the game UX and HUD design for your game, and answer its discovery questions about platforms, inputs, and player journeys.
