team-ui

When this skill is invoked, orchestrate the UI team through a structured pipeline. **Decision Points:** At each phase transition, use `AskUserQuestion` to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase. ## Team Composition - **ux-designer** — User flows, wireframes, accessibility, input handling - **ui-programmer** — UI framework, screens, widgets, data binding, implementation - **art-director** — Visual style, layout polish, consistency with art bible - **engine UI specialist** — Validates UI implementation patterns against engine-specific best practices (read from `.claude/docs/technical-preferences.md` Engine Specialists → UI Specialist) - **accessibility-specialist** — Audits accessibility compliance at Phase 4 **Templates used by this pipeline:** - `ux-spec.md` — Standard screen/flow UX specification - `hud-design.md` — HUD-specific UX specification - `interaction-pattern-library.md` — Reusable interaction patterns - `accessibility-requirements.md` — Committed accessibility tier and requirements ## How to Delegate Use the Task tool to spawn each team member as a subagent: - `subagent_type: ux-designer` — User flows, wireframes, accessibility, input handling - `subagent_type: ui-programmer` — UI framework, screens, widgets, data binding - `subagent_type: art-director` — Visual style, layout polish...