ux-design

Guides section-by-section authoring of UX specs, HUD designs, and interaction pattern libraries for games.

13|Updated Jul 30, 2026
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill ux-design-frabcd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-design
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/ux-design
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill ux-design-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Designing game screens, flows, and HUDs without a structured process leads to inconsistent specs, missed accessibility requirements, and navigation mismatches across screens. This Skill walks you through each section of a UX specification interactively, grounding every decision in your game concept, player journey, and GDD requirements. ## Core Features & Use Cases - Three authoring modes: Create a per-screen UX spec (e.g., main-menu, inventory), a full HUD design, or an interaction pattern library, each with its own structured template. - Context-aware guidance: Reads your game concept, player journey map, GDD UI Requirements, art bible, and accessibility requirements before asking questions, so recommendations fit your project. - Retrofit and recovery support: Detects existing spec files and fills only incomplete sections, and resumes interrupted sessions from saved session state without losing approved work. - Use Case: You need to spec your game's inventory screen. The Skill reads your GDD and player journey, asks targeted questions about layout zones and interaction mappings, drafts each section for your approval, and writes the approved content to design/ux/inventory.md with acceptance criteria ready for QA. ## Quick Start Ask the AI to use the ux-design skill to create a UX spec for your game's main menu screen.

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 spec for a game screen?

Invoke the skill with the screen name, such as main-menu or inventory, and it creates a skeleton file at design/ux/[name].md. It then walks you through each section interactively, drafting content for your approval before writing it to the file.

How do I design a game HUD step by step?

Pass hud as the argument to enter HUD design mode. The skill starts with your HUD philosophy, builds a full information inventory from GDD UI Requirements, categorizes items as Must Show, Contextual, On Demand, or Hidden, then designs layout zones and elements.

What documents does the UX design skill need before starting?

It reads design/gdd/game-concept.md as the required foundation, plus optional files like design/player-journey.md, GDD UI Requirements sections, the art bible, and accessibility requirements. Missing files produce warnings with fallback guidance rather than blocking the workflow.

Can I resume an interrupted UX spec authoring session?

Yes. The skill writes each approved section incrementally and records progress in production/session-state/active.md. On resume, it reads the session state and the spec file, then continues from the next incomplete section without redoing finished work.

Does the skill overwrite an existing UX spec file?

No. It detects existing files and enters retrofit mode, presenting a section-by-section status summary. Only sections that are empty or contain placeholders are authored; existing content is preserved and edited in place.

What happens after a UX spec is completed?

The skill runs a cross-reference check covering GDD requirement coverage, pattern library alignment, navigation consistency, accessibility, and empty states. It then recommends running ux-review to validate the spec before it enters the implementation pipeline.