gds-ux

Plan game UX, UI, and HUD design specifications as DESIGN.md and EXPERIENCE.md documents.

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-ux-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-ux
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-ux
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-ux-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Game teams often lack a structured way to capture UX, UI, and HUD decisions, leaving visual identity and interaction behavior scattered across chats, mockups, and memory. This Skill elicits the developer's vision through guided discovery and distills it into two authoritative contract documents. ## Core Features & Use Cases - Dual design contracts: Produces DESIGN.md (visual identity tokens per the Google Labs spec) and EXPERIENCE.md (information architecture, HUD behavior, input schemes, game feel, accessibility, player journeys). - Three modes: Create a new UX workspace, Update an existing spine pair, or Validate spines with an opt-in multi-lens reviewer gate and consolidated HTML/Markdown report. - Creative tooling: Renders HTML color themes, design directions, Excalidraw wireframes, and key-screen mockups to support decisions during discovery and finalization. - 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 delivers final DESIGN.md and EXPERIENCE.md files ready for architecture and story development. ## Quick Start Ask the AI to help you plan the game UX and HUD design for your game project.

Frequently Asked Questions about gds-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create game UX and HUD design specifications with AI?

Invoke the skill with a request like "lets create game UX" or "design the HUD". It runs a discovery interview about platforms, input schemes, and player journeys, then distills decisions into DESIGN.md and EXPERIENCE.md contract files.

What is the difference between DESIGN.md and EXPERIENCE.md?

DESIGN.md owns how the game looks: color, typography, spacing, and component tokens per the Google Labs design.md spec. EXPERIENCE.md owns how it works: information architecture, HUD behavior, states, input schemes, accessibility, and key player flows.

Does the skill support game engines like Unity or Unreal?

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

Can I validate an existing UX specification instead of creating one?

Yes. The Validate intent critiques an existing DESIGN.md and EXPERIENCE.md pair using a rubric walker plus optional reviewer lenses, then writes consolidated validation-report.html and validation-report.md files without modifying the spines.

What accessibility concerns does game UX planning cover?

The EXPERIENCE.md spine includes an Accessibility Floor covering remappable controls, colorblind modes, subtitles and captions, reduced-motion toggles, HUD scaling, and hold-vs-toggle options, informed by AbleGamers and Xbox accessibility guidelines.