gds-ux

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

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-ux-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-ux
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-ux
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-ux-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

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.

Frequently Asked Questions about gds-ux

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

FAQPage Schema
How do I create a game UX design specification?

Invoke the skill with a request like "lets create game UX" and it runs a discovery workflow covering form factor, input schemes, HUD hierarchy, and player journeys. It then distills decisions into DESIGN.md and EXPERIENCE.md files in a run folder under your planning artifacts directory.

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 spec. EXPERIENCE.md owns how it works: information architecture, HUD behavior, states, input schemes, game feel, and accessibility, cross-referencing DESIGN.md tokens by name.

Does the skill support game HUD and diegetic UI planning?

Yes. EXPERIENCE.md includes a HUD and Diegetic UI section covering what is non-diegetic overlay versus in-world UI, HUD information hierarchy, and what fades during play. It also covers input schemes with platform-adaptive button glyphs and game feel like hit-stop and haptics.

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

Yes. The Validate intent critiques an existing DESIGN.md and EXPERIENCE.md pair without changing it, dispatching reviewer lenses that check flow coverage, token completeness, component and state coverage, and shape fit, then writing HTML and Markdown validation reports.

Does the skill work in headless or automated pipelines?

Yes. Headless mode accepts a structured payload with intent (create, update, or validate) and inputs, skips greetings and creative tools by default, and ends with a JSON status payload following the schemas in assets/headless-schemas.md.