ux-design

Generate section-by-section UX documentation for game screens using studio design inputs.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill ux-design-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/ux-design
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill ux-design-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ux-design turns fragmented game design materials (concept, player journey, and GDD UI requirements) into a clear, screen-ready UX specification without forcing you to manually reconcile constraints and navigation details.

Core Features & Use Cases

  • Guided UX authoring by mode: create a UX spec for a screen/flow, produce HUD design documentation, or build an interaction pattern library.
  • Context-aware drafting: reads GDD UI Requirements, existing UX specs, player journey, accessibility requirements, and art direction to reduce inconsistencies and rework.
  • Incremental, structured outputs: generates a properly scaffolded file in the studio’s design/ux/ structure and then fills each section with approvals to avoid overwriting good content.

Quick Start

Start a UX spec by invoking the skill with the screen name you want, for example: "Design the main-menu screen UX spec."

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I generate a UX specification from game design document requirements?

Generate a UX specification by providing a screen name alongside existing concept, player journey, and GDD UI requirements. The skill reads these inputs to draft a structured, screen-ready UX spec incrementally without manual reconciliation.

What is the best way to document game HUD interaction states and navigation flows?

Documenting game HUD interaction states requires mapping navigation, interaction states, and accessibility criteria. This approach produces guided, section-by-section HUD design documentation using your existing art bible and platform preferences.

How do I build an interaction pattern library for a game UI?

Build an interaction pattern library by authoring UX specs that catalog standardized navigation and interaction states. The process reads your existing UX catalog and GDD UI requirements to generate deterministic markdown outputs in your studio structure.

Can I use existing art direction and accessibility requirements to draft UX documentation?

Yes, you can use existing art direction and accessibility requirements to draft UX documentation. The skill performs context-aware reads of these inputs to reduce inconsistencies and rework when authoring new specs or retrofitting existing ones.

Does generating UX documentation require manually formatting markdown files?

Generating UX documentation does not require manually formatting markdown files. The skill performs deterministic writes to scaffold a properly structured file in your studio's design directory and fills each section incrementally with approvals.