ux-design

Create structured UX specifications for game screens, flows, HUDs, and interaction patterns.

47|12|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill ux-design-nuoyanruoshui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/ux-design
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill ux-design-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns incomplete game design context into structured, actionable UX specifications for screens, flows, HUDs, and interaction patterns, reducing ambiguity between design and implementation.

Core Features & Use Cases

  • Context-Aware UX Design: Reads game concepts, player journeys, GDD UI requirements, art direction, accessibility requirements, technical preferences, and existing UX specs before proposing designs.
  • Guided Authoring: Leads section-by-section discovery, presents design options, captures decisions, obtains approval, and incrementally writes production-ready documentation.
  • Multiple Design Modes: Creates screen and flow UX specs, HUD designs, or interaction pattern libraries with layouts, states, interactions, events, transitions, data requirements, accessibility, localization, and acceptance criteria.
  • Use Case: Use it to design an inventory screen that aligns with the game's player journey, input methods, existing navigation, accessibility tier, and UI requirements, then validate cross-references before handoff.

Quick Start

Use the ux-design skill with a screen or flow name, hud, or patterns to create the appropriate game UX documentation.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I create structured game UX specifications from incomplete design documents?

To create game UX specifications, you need a context-aware workflow that reads GDD requirements, player journeys, and art direction, then incrementally drafts production-ready UX docs for screens, flows, and HUDs through iterative approval.

What is the best way to design a game HUD that aligns with player journey and accessibility requirements?

Designing a game HUD requires coordinating player journeys, navigation, input methods, and accessibility tiers to produce structured specifications that include layout states, interactions, transitions, and acceptance criteria.

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

Building an interaction pattern library involves defining consistent layouts, states, events, and transitions, then validating cross-references against existing UX documentation and GDD requirements before handoff.

Can I generate UX specs for game screens using Godot and existing UI documentation?

Yes, generating UX specs for game screens works with Godot projects by reading technical preferences and existing UX documentation to create context-aware designs that capture input methods and localization requirements.

Does game UX design require accessibility and localization planning before implementation?

Game UX design requires accessibility and localization planning before implementation to ensure screen flows and HUD designs meet required accessibility tiers and support multi-language data requirements.

Why does my game UX documentation have ambiguity between design and implementation?

Game UX documentation has ambiguity between design and implementation when it lacks structured cross-reference validation, missing acceptance criteria, and incomplete alignment with GDD requirements and technical preferences.