ux-design

Generate context-aware UX specifications for game screens, HUDs, and interaction patterns.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill ux-design-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/ux-design
Command: npx skills add https://github.com/WindXRan/y3td --skill ux-design-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns a game concept into clear, section-by-section UX specifications that align with player journey context and documented GDD UI requirements, reducing guesswork and rework.

Core Features & Use Cases

  • Context-aware UX authoring: Reads game concept, player journey (if available), GDD UI requirements, existing UX specs, interaction pattern catalog, art bible, and accessibility/input platform preferences to guide decisions.
  • Three authoring modes: Produces a screen/flow UX spec, a HUD design doc, or an interaction pattern library spec using the studio templates.
  • Incremental & safe iteration: Detects existing output files, supports retrofit mode (non-destructive edits), and writes approved section content into the target file.

Quick Start

Use ux-design to draft the UX spec for the "main-menu" screen and create design/ux/main-menu.md using the available GDD and journey context.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I generate UX specifications for a game HUD or screen from existing design documents?

Generate game HUD UX specifications by reading existing GDD UI requirements, player journey context, and accessibility preferences to produce section-by-section markdown specs. This reduces guesswork by aligning UX decisions directly with documented game design requirements.

Can I retrofit existing UX specs without overwriting my previous interaction design work?

Retrofitting existing UX specs is supported through a non-destructive mode that detects existing output files and asks for approval before writing each section. This ensures previous interaction design work remains safe while applying incremental updates to your target markdown file.

What is an interaction pattern library catalog and when do I need one for game UI design?

An interaction pattern library catalog standardizes navigation, interaction, and data requirements across game UI screens. You need one when scaling game UI design to ensure consistent player experiences, generated from your existing art bible and input platform preferences into a structured markdown spec.

Does this UX design workflow support accessibility and multiple input platform preferences?

Accessibility and input platform preferences are explicitly supported as context inputs. The workflow reads these parameters alongside your game concept and art bible to ensure generated UX specs meet specific platform requirements and accessibility standards for the target player journey.

What is the best way to draft a main-menu UX spec using GDD and player journey context?

Drafting a main-menu UX spec involves passing the screen argument and available GDD context to generate a structured markdown file. The system reads game concept and player journey data to output a guided, context-aware specification at the correct target file path.