ux-design

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill ux-design-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/ux-design
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill ux-design-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many game projects lack structured, context-aware UX documentation that ties screens and HUDs to the game concept, GDD requirements, player journey, and technical input methods. This Skill guides a designer step-by-step to gather project context, create or retrofit a UX spec skeleton, and author each section incrementally while updating session state so work survives interruptions.

Core Features & Use Cases

  • Context-first spec generation: Reads game concept, player journey, GDD UI requirements, pattern library, art bible, and technical preferences to ground every UX decision.
  • Three authoring modes: Produce screen/flow UX specs, HUD designs, or an interaction pattern library with retrofit support for existing files.
  • Incremental, collaborative workflow: Creates skeleton files immediately, asks targeted questions per section, writes approved content, and updates production/session-state for recoverability and handoff.
  • Acceptance & cross-reference checks: Ensures GDD coverage, pattern alignment, navigation consistency, and accessibility considerations before marking a spec ready for review.

Quick Start

Use the ux-design skill to create a UX spec for the "inventory" screen.

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 UX specifications for game screens from a GDD?

To create UX specifications for game screens, this Skill reads your game design documents, player journey, and art bible to generate context-aware spec skeletons. It then incrementally writes approved sections into design/ux/*.md files while updating session state for recoverability.

What is the best way to document HUD designs and interaction patterns for a game?

The best way to document HUD designs and interaction patterns is using a structured authoring workflow that retrofits existing files or creates new ones. This Skill aggregates HUD elements across systems and aligns them with your game's pattern library and technical input methods.

Can I retrofit existing UX documentation files into a new interaction pattern library?

Yes, you can retrofit existing UX documentation files into an interaction pattern library. The Skill supports three authoring modes including retrofit support, allowing you to read current files and append or restructure content into standardized design/ux/*.md specifications.

How does a context-aware UX spec ensure GDD coverage and accessibility?

Context-aware UX specs ensure GDD coverage and accessibility by running cross-reference checks before marking a spec ready for review. The Skill verifies that game design requirements, navigation consistency, pattern alignment, and accessibility considerations are all addressed in the final output.

Do I need a specific session state file to manage incremental UX spec generation?

You need a production/session-state/active.md file to manage incremental UX spec generation. The Skill updates this session state after each approved write, ensuring your design progress survives interruptions and can be handed off cleanly.

What technical inputs are required to generate game UX specs that match my project?

Generating game UX specs requires technical inputs like game concept files, GDD UI requirements, player journey maps, pattern libraries, and art bibles. The Skill reads these project documents via file glob and grep capabilities to ground every UX decision in your existing context.