team-ui

Coordinate UI teams through the full UX pipeline with phase gates.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill team-ui-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill team-ui-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The UI team orchestration skill coordinates a cross-functional group through the full UX pipeline to ensure timely delivery, alignment, and quality across design, implementation, and polish stages.

Core Features & Use Cases

  • Phase-driven orchestration across the UX pipeline: design spec authoring, reviews, asset planning, and handoffs to implementation.
  • Clear team roles: ux-designer, ui-programmer, art-director, engine UI specialist, accessibility-specialist.
  • Templates and artifacts: ux-spec.md, hud-design.md, interaction-pattern-library.md, accessibility-requirements.md.
  • Delegation and parallel execution: spawn subagents via Task and run independent work streams in parallel when possible.

Quick Start

Invoke the team-ui skill to start coordinating the UI pipeline from concept to polished release.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I coordinate a UX pipeline across multiple UI roles from concept to release?

You can coordinate a UX pipeline by orchestrating cross-functional UI roles through phase-driven gates covering design spec authoring, asset planning, implementation, and accessibility checks to ensure end-to-end UI delivery.

What is the best way to manage parallel design and implementation work streams for UI features?

Managing parallel work streams involves spawning subagents to run independent design and implementation tasks simultaneously, while enforcing phase gates to maintain alignment and quality across the UI pipeline.

How do I ensure accessibility checks and asset planning are included in UI design handoffs?

Accessibility and asset planning are integrated into UI design handoffs by enforcing phase gates that require specific artifacts like accessibility-requirements.md and interaction-pattern-library.md before proceeding to implementation.

Can I use agent orchestration to manage UI team roles like ux-designer and ui-programmer?

Yes, agent orchestration can manage defined UI team roles including ux-designer, ui-programmer, art-director, and accessibility-specialist by delegating tasks and surfacing proposals via interactive prompts for coordinated execution.

What templates and artifacts are needed to document decisions across the UX pipeline?

Documenting UX pipeline decisions requires templates such as ux-spec.md, hud-design.md, and accessibility-requirements.md to record full context, enabling auditability and repeatability across UI feature workflows.

Why does a UI feature workflow require phase gates between design, review, and implementation?

UI feature workflows require phase gates to enforce quality and alignment across sequential stages, preventing progression from design to implementation until reviews, asset planning, and accessibility checks are fully satisfied.