team-ui

Coordinate UI team workflow across the UX pipeline from spec authoring to polish.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill team-ui-solace-ill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/solace-ill/vector-flow --skill team-ui-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the UI team through the full UX pipeline from UX spec authoring to visual polish, enabling coordinated delivery and governance.

Core Features & Use Cases

  • Phase-based UI pipeline orchestration linking UX design, UX review, and art direction with studio templates
  • Delegation to specialized subagents: ux-designer, ui-programmer, art-director, engine UI specialist, accessibility-specialist
  • Reuse of standard templates: ux-spec.md, hud-design.md, interaction-pattern-library.md, accessibility-requirements.md

Quick Start

Start the UI pipeline by spawning the required subagents for each role and initiating Phase 1 with the project design artifacts.

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 UI team workflow across the full UX design pipeline?

You can coordinate a UI team workflow by orchestrating the full UX pipeline from spec authoring to visual polish, delegating specialized tasks like UX design, programming, and art direction to designated subagents while enforcing phase gates.

What is the best way to manage UX design, review, and art direction for UI features?

Managing UX design, review, and art direction is best handled through phase-based UI pipeline orchestration, linking these stages with standard studio templates to ensure coordinated delivery and governance across all UI feature initiatives.

How do I enforce documentation and phase gates during UI feature development?

To enforce documentation and phase gates during UI feature development, you orchestrate the team workflow by requiring specific design artifacts and standard templates like ux-spec.md at each stage before advancing to the next pipeline phase.

Can I reuse standard templates like ux-spec.md and accessibility-requirements.md for UI pipeline orchestration?

Yes, you can reuse standard templates including ux-spec.md, hud-design.md, interaction-pattern-library.md, and accessibility-requirements.md to maintain consistency and governance when orchestrating UI pipeline phases from concept to polish.

Do I need to spawn subagents for roles like accessibility-specialist and art-director to start the UI pipeline?

Yes, starting the UI pipeline requires spawning required subagents for each specialized role, such as ux-designer, ui-programmer, art-director, engine UI specialist, and accessibility-specialist, before initiating Phase 1 with project design artifacts.

Why does my UI team workflow break down between UX spec authoring and visual polish?

UI team workflows break down between spec authoring and polish when there is no orchestration enforcing phase gates and documentation, causing disconnected handoffs between UX design, review, and art direction roles.