team-ui

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating UX designers, UI programmers, art directors, and accessibility reviewers across a game UI feature is error-prone and inconsistent. This Skill structures the entire UI production pipeline into gated phases so specs are reviewed before implementation and accessibility is verified before polish. ## Core Features & Use Cases - Phased UI Pipeline: Runs context gathering, UX spec authoring, UX review, visual design, implementation, parallel review, and polish with user approval gates between phases. - Review Mode Control: Supports full, lean, and solo modes to scale director-level review gates to the team's needs. - Engine-Aware Implementation: Delegates to engine UI specialists (Unity UI Toolkit/UGUI, Godot Control nodes, Unreal UMG/CommonUI) for framework-specific guidance before coding. - Use Case: A team building a game HUD invokes the pipeline to produce a HUD spec from the hud-design template, get it reviewed, implement it with reusable interaction patterns, and pass an accessibility audit against the committed tier. ## Quick Start Ask the agent to run the team-ui pipeline for your feature, for example: orchestrate the full UI pipeline for the inventory screen using the committed accessibility tier.

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 game UI design pipeline with AI agents?

Invoke the team-ui skill with a feature name to run a gated pipeline: context gathering, UX spec authoring, UX review, visual design, implementation, parallel review, and polish. Each phase transition requires user approval before proceeding.

What review modes does the UI pipeline support?

Three modes are supported: full spawns all director and lead gates, lean keeps only phase-gate director reviews, and solo skips all director gates. Set the mode with a --review argument or a production/review-mode.txt file; the default is lean.

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

Yes. Before implementation, an engine UI specialist chosen from the project configuration reviews the spec for framework guidance, such as UI Toolkit versus UGUI in Unity, Control nodes in Godot, or UMG versus CommonUI in Unreal.

How does the pipeline handle accessibility compliance?

An accessibility-specialist agent audits the implementation in the parallel review phase against the committed tier in design/accessibility-requirements.md. Violations are flagged as blockers, and visual design must verify contrast ratios and non-color state indicators.

What happens if a UI pipeline agent gets blocked?

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 and resolve the issue. A partial report of completed work is always produced.