team-ui

Orchestrate game UI workflows from UX specification through engine implementation and accessibility review.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-ui-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill team-ui-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates the full UX-to-implementation UI pipeline to prevent fragmented designs, accessibility regressions, and engine-incompatible implementations by enforcing structured handoffs, reviews, and pattern reuse.

Core Features & Use Cases

  • End-to-end orchestration: Guides context gathering, UX spec authoring, visual design, engine-specific implementation, parallel review, and polish into a single coordinated flow.
  • Multi-agent delegation & gating: Spawns and coordinates specialized subagents (ux-designer, ui-programmer, art-director, engine UI specialist, accessibility-specialist), presents decision points to the user, and requires approvals before phase transitions.
  • Pattern-library and accessibility enforcement: Ensures interaction patterns are tracked in the shared library and verifies accessibility compliance against the committed requirements.
  • Use Case: Deliver a new HUD or settings screen from UX spec through engine-validated implementation with accessibility checks and an updated interaction pattern entry.

Quick Start

Invoke the team-ui skill with a concise feature description, for example: design and implement the game's settings screen with keyboard, mouse, and gamepad support.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I coordinate game UI delivery from UX spec to engine implementation?

Game UI delivery is coordinated through a structured pipeline that enforces sequential phases from UX specification and visual design to engine-specific implementation, ensuring validated handoffs and preventing fragmented designs.

What is the best way to prevent accessibility regressions in game UI development?

Preventing accessibility regressions requires enforcing accessibility reviews and compliance checks against committed requirements within the UI pipeline, ensuring interaction patterns are tracked and validated before phase transitions.

Can I use multi-agent delegation to manage different stages of game UI design?

Multi-agent delegation manages game UI stages by spawning specialized subagents for ux-design, visual art, programming, and accessibility tasks, coordinating their outputs through approval gates before advancing phases.

How does a structured UI workflow handle engine-specific implementation for game features?

A structured UI workflow handles engine-specific implementation by routing design specifications to an engine UI specialist who validates compatibility, updates the interaction-pattern library, and enforces review-driven error recovery.

Do I need approval gates to move between UX design and UI programming phases?

Approval gates are required between UX design and UI programming phases to present decision points to the user, verify pattern-library updates, and ensure accessibility compliance before implementation begins.

When do I need to update the interaction-pattern library during game UI orchestration?

The interaction-pattern library needs updating during game UI orchestration when new UX specifications introduce novel interaction behaviors, ensuring patterns are tracked and reused across engine-validated implementations.