team-ui

Orchestrate cross-functional UI roles through a phased UX pipeline.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill team-ui-naxoruto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/naxoruto/TE-limonchero-3d/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/naxoruto/TE-limonchero-3d --skill team-ui-naxoruto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the UI team through a structured UX pipeline, guiding cross-functional roles from initial UX spec to final visual polish and release-ready implementation.

Core Features & Use Cases

  • Coordinates a multidisciplinary UI squad (ux-designer, ui-programmer, art-director, engine UI specialist, accessibility-specialist) to deliver cohesive interfaces.
  • Defines a repeatable pipeline with phases for context gathering, design, review, implementation, and polish, using centralized templates and best practices.
  • Enables delegation via subagents and parallel workstreams, ensuring artifacts (specs, patterns, and assets) stay aligned with the art bible and accessibility requirements.

Quick Start

Start the team-ui pipeline for a new feature by initiating the full UX-to-polish workflow and delegating roles to the specialists.

Frequently Asked Questions about team-ui

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

FAQPage Schema
What is a cross-functional UI workflow pipeline for feature development?

A cross-functional UI workflow pipeline coordinates multidisciplinary roles—UX designers, UI programmers, art directors, and accessibility specialists—from initial spec authoring through visual design, implementation, review, and final polish to deliver cohesive interfaces.

How do I orchestrate a UI team from spec authoring to final visual polish?

You orchestrate a UI team by initiating a structured UX pipeline that defines phases for context gathering, design, review, implementation, and polish, delegating specific tasks to cross-functional subagents to keep artifacts aligned with the art bible.

Can I delegate UX and UI design tasks to different specialists in parallel?

Yes, the pipeline enables delegation via subagents and parallel workstreams, allowing UX designers, UI programmers, and accessibility specialists to work concurrently while keeping shared artifacts and patterns aligned.

Does this UI pipeline approach support accessibility compliance and art bible alignment?

Yes, the workflow integrates accessibility compliance and engine-specific checks throughout its phases, ensuring that all generated UI patterns and assets remain aligned with the overarching art bible and accessibility requirements.

What's the best way to track phase-based progress across a multidisciplinary UI squad?

The best way to track progress is using a centralized pipeline with structured phases for context gathering, design, implementation, and polish, applying multi-agent delegation via task tools to monitor cross-role collaboration and artifact completion.

When should I not use a full UX-to-polish pipeline for UI design?

You should avoid a full UX-to-polish pipeline for isolated UI tweaks or single-role tasks that do not require cross-functional collaboration, as the overhead of multi-agent delegation and phase-based tracking outweighs the benefits for simple updates.