skills.rest
bmad-code-org
bmad-code-orgOFFICIAL
Explore all skills by this author →
GitHub

gds-ux

Generate DESIGN.md and EXPERIENCE.md UX spines for game development projects.

212|23|Updated Jan 15, 2026
Search Tags:#validation#handoff#ux#game-design#design-md#design-spines#experience-md
One-click install
npx skills add https://github.com/bmad-code-org/bmad-module-game-dev-studio --skill gds-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-ux
Source: https://github.com/bmad-code-org/bmad-module-game-dev-studio/tree/main/src/workflows/2-design/gds-ux
Command: npx skills add https://github.com/bmad-code-org/bmad-module-game-dev-studio --skill gds-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document game UX spines that align design vision with stakeholder goals.

Core Features & Use Cases

  • Generate DESIGN.md (visual identity) and EXPERIENCE.md (information architecture, flow, accessibility) frontmatter that anchor design decisions.
  • Provide an activation-ready workflow: customization loading, pre/post steps, and integration with validation/handoffs.
  • Support cross-engine UX planning for menu, HUD, and diegetic interfaces.

Quick Start

Provide DESIGN.md and EXPERIENCE.md spines that reflect the stakeholder vision for the game's UX

Frequently Asked Questions about gds-ux

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

FAQPage Schema
How do I document game UX design spines for stakeholder alignment?▼

Generate structured DESIGN.md and EXPERIENCE.md files to codify visual identity, information architecture, and player journeys. This provides a shared UX blueprint that aligns design vision with stakeholder goals during game development.

What is the best way to plan HUD and menu flows across different game engines?▼

Use engine-agnostic UX planning spines to map out menu, HUD, and diegetic interfaces. By documenting the experience architecture in markdown, you can maintain consistent player journeys across Unity, Unreal, and Godot.

How do I structure UX handoff documentation for a game development project?▼

Create UX handoff documentation by generating DESIGN.md for visual identity and EXPERIENCE.md for accessibility and flow. These files serve as codified blueprints, ensuring developers and designers share a single source of truth.

Do I need specific engine dependencies to generate game UX blueprints?▼

No specific engine dependencies are required to generate these UX blueprints. The workflow is engine-agnostic, applying to Unity, Unreal, and Godot projects during the discovery and handoff phases without needing installed components.

Can I reference external game assets and scripts when generating UX documentation?▼

Yes, you can reference optional resources like scripts, references, and assets for activation. Integrating these external materials enriches the generated DESIGN.md and EXPERIENCE.md spines with existing project context.

Related Skills

Explore More Design & Creative Skills→
noahrashetanoahrasheta
1

director:onboard

Guide vision interviews and generate foundational Vision documents for new projects.

Community
Advanced
LawrenceHwangLawrenceHwang

game-dev

Organize game development workflows with linked WORKFLOW.md, GAME-ENGINE.md, and TESTING.md references.

Community
Intermediate
Euraika-LabsEuraika-Labs
14

team-ui

Orchestrate multi-role UI workflows for game projects from specification to polish.

Official
Advanced
frankbriafrankbria
1

cli-ifying

Convert Claude Code capabilities into standalone cross-platform CLI tools.

Community
Advanced