What problem does it solve?
Game UX and HUD design often suffers from inconsistency and misalignment with existing project assets like game design documents, player journey maps, and accessibility requirements, as designers must manually cross-reference scattered resources to create compliant, context-aware designs.
Core Features & Use Cases
- Multi-mode authoring: Create per-screen/flow UX specifications, full HUD design documents, or a centralized interaction pattern library depending on your needs.
- Automated context gathering: Automatically pulls relevant context from game concept docs, player journey maps, GDD UI requirements, existing UX specs, art bibles, and accessibility requirements to eliminate manual research.
- Use Case: A game designer working on a new inventory screen can invoke this skill to automatically pull all relevant GDD requirements and player journey context, then walk through a structured, approval-based authoring process to produce a complete UX spec that aligns with the project's existing design standards.
Quick Start
Invoke the ux-design skill with a screen or flow name, "hud", or "patterns" to start a guided, context-aware design authoring session.