gds-ux

Invoke the skill with a request like "lets create game UX" and it runs a Discovery phase capturing your vision through probing questions, then distills decisions into DESIGN.md (visual identity) and EXPERIENCE.md (behavior, flows, accessibility) at Finalize.

DESIGN.md owns how the game looks: color, typography, spacing, and component tokens following the Google Labs spec. EXPERIENCE.md owns how it works: information architecture, HUD behavior, input schemes, game feel, accessibility, and player journeys, cross-referencing DESIGN.md tokens by name.

Yes. When the Foundation section names an engine or UI system such as Unity UI Toolkit, Unreal UMG, or Godot Control nodes, both specification files inherit from it, referencing system defaults and specifying only the behavioral or visual deltas.

Yes. Validate intent runs an opt-in reviewer gate with selectable lenses, including a rubric walker checking flow coverage, token completeness, component and state coverage, plus ad-hoc lenses like accessibility. Findings are synthesized into HTML and Markdown validation reports.

It covers console, handheld, PC, mobile, and VR form factors, with input scheme sections for controller, keyboard and mouse, touch, and motion, including remapping, context-sensitive prompts, and per-platform button glyph adaptation.

Do not use it for PRDs, game architecture, narrative design, or GDD authoring; the skill detects these misroutes and redirects to gds-prd, gds-game-architecture, gds-create-narrative, or gds-gdd respectively.