ux-design

Plan and document context-rich UX specs for screens and HUDs.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill ux-design-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/ux-design
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill ux-design-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UX teams often struggle to keep design concepts aligned with engineering implementation, resulting in drift between ideas and delivery. This skill provides a structured, repeatable process to craft context-rich UX specs for screens, flows, and HUDs, anchored in game concepts, player journeys, and design documentation.

Core Features & Use Cases

  • Structured framework for purpose, context, layout, and interaction mapping tailored to game UX.
  • Auto-gathers references from design/gdd, player journey, accessibility, and localization requirements to inform specs.
  • Step-by-step skeleton creation, section-by-section authoring, retrofitting existing specs, and cross-reference checks to ensure consistency and quality.
  • Handoff-ready outputs for production, QA, and design-review workflows across design and engineering teams.
  • Supports HUD and non-HUD screens, with tooling for pattern-library integration.

Quick Start

Start by summarizing the target screen or flow, then draft sections for purpose, arrival context, layout, interactions, states, data, accessibility, localization, and acceptance criteria.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I write UX specs for game screens and HUDs?

To write UX specs for game screens, draft sections for purpose, arrival context, layout, interactions, states, data, accessibility, and localization. This structured approach aligns design intent with implementation through step-by-step skeleton creation and section-by-section authoring.

What is the best way to document game UI flows for engineering handoff?

Documenting game UI flows for engineering handoff requires context-rich UX specs that map layout, interactions, and states. This process generates handoff-ready outputs for production, QA, and design-review workflows, ensuring alignment between design concepts and engineering implementation.

Can I retrofit existing UX documentation for a game design workflow?

Yes, you can retrofit existing UX documentation within a game design workflow. The process supports retrofitting existing specs and performing cross-reference checks to ensure consistency, quality, and alignment with GDD references and player journey constraints.

Does the UX spec process support accessibility and localization requirements?

Yes, the UX spec process explicitly supports accessibility and localization requirements. It auto-gathers references from accessibility and localization requirements to inform specs, integrating these considerations directly into the section-by-section authoring workflow.

How do I keep game concept design aligned with engineering implementation?

To keep game concept design aligned with engineering implementation, use a structured framework to plan context-rich UX specs anchored in game concepts and player journeys. This prevents drift between ideas and delivery by shaping scope and constraints before handoff.