ux-design

Generate UX specification skeletons for game screens and HUDs.

14|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill ux-design-euraika-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/ux-design
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill ux-design-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.

Core Features & Use Cases

  • Context-driven UX spec authoring: reads game concept, player journey, and GDDs to tailor guidance for each screen.
  • Skeleton generation: creates ux-spec.md or hud-design.md ready for section-by-section drafting.
  • Template-driven outputs: integrates with studio templates for consistent documentation across screens.
  • Retrofit scaffolding: creates a fresh skeleton when no target file exists and updates progressively.

Quick Start

Provide the screen or flow name to generate a UX spec skeleton and guidance.

Frequently Asked Questions about ux-design

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

FAQPage Schema
How do I write a UX specification for a game screen using an existing GDD?

To write a UX specification for a game screen, provide the screen or flow name to generate a context-aware spec skeleton. The system reads your game concept, player journey, and GDD references to draft section-by-section UX guidance.

What is the best way to document game HUD design and player journey flows?

Document game HUD design and player journeys by generating a structured hud-design.md file. This creates a ready-to-extend skeleton aligned with your studio templates, ensuring structural consistency and accessibility across game progression screens.

Can I generate a UX spec skeleton if I don't have an existing target file?

Yes, you can generate a UX spec skeleton without an existing target file. The system provides retrofit scaffolding to create a fresh ux-spec.md that you update progressively as your game interaction design evolves.

How does context-driven game design documentation improve screen accessibility?

Context-driven game design documentation improves screen accessibility by aligning generated UX specs with existing studio templates and style guidelines. This ensures structure, accessibility, and reuse across all drafted game progression interactions.

Do I need a full game design document to draft UX specifications for game interactions?

You do not need a full game design document but providing GDD references, game concepts, and player journey details allows the system to produce highly context-aware UX specifications and tailored design guidance for your specific game interactions.

Why use template-driven UX specs for game progression instead of drafting manually?

Use template-driven UX specs to ensure consistent documentation across multiple game screens and flows. Integrating with studio templates produces standardized ux-spec.md outputs that are structured for review and extension, reducing manual formatting errors.