team-ui

Orchestrates ux-designer, ui-programmer, and art-director subagents through a five-phase UI feature pipeline.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill team-ui-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/team-ui
Command: npx skills add https://github.com/onemanking/the-operator --skill team-ui-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a user interface feature requires coordinating UX design, visual design, implementation, and review across multiple disciplines, which is hard to manage in a single pass. This Skill structures that work as a phased pipeline with dedicated subagents and user approval gates at each transition. ## Core Features & Use Cases - Phased UI Pipeline: Runs UX design, visual design, implementation, parallel review, and polish as distinct phases with clear deliverables per phase. - Subagent Delegation: Spawns ux-designer, ui-programmer, and art-director subagents via the Task tool, with parallel execution where the pipeline allows. - User Decision Gates: Presents each subagent's proposals as selectable options through AskUserQuestion so the user approves before the next phase begins. - Use Case: Ask for a new settings screen for a game; the Skill produces wireframes and an interaction map, a visual design spec consistent with the art bible, an implemented UI with localization and gamepad support, and a final review report. ## Quick Start Invoke the team-ui skill with a description of the UI feature you want designed and implemented, then approve each phase's proposals as they are presented.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I coordinate multiple AI agents to build a UI feature?▼

Invoke this Skill with a UI feature description and it delegates work to ux-designer, ui-programmer, and art-director subagents in a five-phase pipeline. Each phase produces a concrete deliverable, and you approve proposals before the pipeline advances.

What does the UI team pipeline produce at each phase?▼

Phase 1 produces a UX spec with wireframes and an interaction map, Phase 2 a visual design spec, Phase 3 the implemented UI, Phase 4 parallel UX and art reviews, and Phase 5 polish fixes. The final output is a summary report covering all statuses.

Does the implemented UI support gamepad and keyboard navigation?▼

Yes, the pipeline explicitly requires both keyboard/mouse and gamepad navigation. The ux-designer defines interaction patterns for both input methods, and the review phase tests keyboard-only and gamepad-only navigation.

Can the UI implementation modify game state directly?▼

No, the Skill enforces that UI never owns or modifies game state. The ui-programmer implements display-only components that emit events for actions, with data binding wired to read game state.

What accessibility requirements does the UI pipeline enforce?▼

The pipeline requires text scaling, contrast and colorblind-safe design, skippable animations respecting motion preferences, and verification at minimum and maximum supported resolutions. Accessibility is specified in Phase 1 and verified in Phase 4.