team-ui

Orchestrates a multi-agent UI pipeline from UX spec through implementation and polish.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill team-ui-claretagrapelike32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/team-ui
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill team-ui-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating UX designers, UI programmers, art directors, and accessibility specialists across a game UI feature is error-prone and inconsistent. This Skill runs the full UI pipeline as a structured, gated workflow so every screen goes from spec to polished implementation with review checkpoints. ## Core Features & Use Cases - Phased UI Pipeline: Runs context gathering, UX spec authoring, UX review, visual design, implementation, parallel review, and polish as gated phases with user approval at each transition. - Multi-Agent Delegation: Spawns ux-designer, ui-programmer, art-director, engine UI specialist, and accessibility-specialist subagents with full context. - Review Modes: Supports full, lean, and solo modes to control how many director review gates are spawned. - Use Case: When building a new HUD for a Unity game, invoke the pipeline to produce a UX spec from the hud-design template, get it reviewed, apply art bible styling, implement with engine-specific UI guidance, and verify accessibility compliance before shipping. ## Quick Start Use $ai-game-studio:team-ui to run the full UI pipeline for the settings menu feature and report the results of each phase.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I run a full UI design pipeline for a game feature?▼

Invoke the team-ui skill with the feature name. It gathers context from your GDD and player journey docs, authors a UX spec, runs a review gate, then delegates visual design, implementation, parallel review, and polish to specialized subagents.

What review modes does the UI pipeline support?▼

Three modes: full spawns all director and lead gates, lean skips director gates except phase-gate types, and solo skips all director gates. Set the mode with a --review argument or a production/review-mode.txt file; it defaults to lean.

Does the UI pipeline support Unity, Godot, and Unreal?▼

Yes. During implementation it spawns an engine UI specialist read from .ai-game-studio/project.json to validate framework choices such as UI Toolkit vs UGUI in Unity, Control nodes in Godot, or UMG vs CommonUI in Unreal.

How does the pipeline handle accessibility compliance?▼

An accessibility-specialist subagent audits the implementation in Phase 4 against the committed tier in design/accessibility-requirements.md. Violations are flagged as blockers, and the art director also verifies contrast and non-color state indicators.

What happens if a subagent gets blocked during the pipeline?▼

The error recovery protocol surfaces the blocker immediately, checks downstream dependencies, and offers options to skip with a noted gap, retry with narrower scope, or stop. A partial report of completed work is always produced.