ux-design

To generate UX specs for game screens and HUDs, provide a target screen name along with your game concept and player journey. The skill reads these inputs to produce a context-aware, ready-to-edit ux-spec.md scaffold tailored to that specific interaction.

A UX specification for a game interface details the purpose, player flow, and acceptance criteria for screens and HUDs. It translates the game concept and GDD into structured documentation that satisfies design and accessibility constraints section by section.

Document game design flows by guiding section-by-section authoring from purpose to acceptance criteria. The skill outputs a structured ux-spec.md or hud-design.md file based on studio templates, ensuring all design and accessibility constraints are addressed.

Yes, you can tailor UX documentation to your game concept and player journey. The skill reads these inputs alongside GDDs to customize the specification for each individual screen or interaction, outputting a scaffold that fits your specific game mechanics.

Game UX documentation should include accessibility constraints to ensure playable experiences. The generated UX specs explicitly satisfy design and accessibility constraints, integrating them directly into the section-by-section authoring process from purpose to acceptance criteria.

The best way to start writing a HUD design document is to invoke the generation process with a target screen name. It scaffolds a complete hud-design.md file using studio templates, allowing you to edit and refine the context-aware specifications immediately.