One-click install
npx skills add https://github.com/WindXRan/y3td --skill team-ui-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/WindXRan/y3td --skill team-ui-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Team-ui removes the chaos of designing and implementing a UI feature by orchestrating the full UX-to-implementation workflow with clear gates, consistent patterns, visual direction, and accessibility checks.

Core Features & Use Cases

  • Structured UX-to-UI workflow: Coordinates UX spec authoring, UX review, visual design, engine-specific guidance, implementation, multi-stream review, and polish.
  • Team-based specialization: Delegates to ux-designer, ui-programmer, art-director, engine UI specialist, and accessibility-specialist to cover flow, widgets/data binding, visuals, engine constraints, and compliance.
  • Pattern-library enforcement: Reuses design/ux/interaction-patterns.md and supports controlled expansion when new interaction patterns are introduced.
  • Review-mode control: Supports --review full|lean|solo (or falls back to production/review-mode.txt / default lean) to control which director gates run.

Quick Start

Run team-ui for your UI feature by invoking: /team-ui "Inventory screen redesign" and optionally add --review lean, so the system produces the UX spec, visual spec, implementation, and review/polish summary.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I orchestrate a UI delivery pipeline from UX specification to final implementation?

A UI delivery pipeline orchestrates UX spec authoring, visual design, engine-specific implementation guidance, development, and multi-stream reviews. It coordinates specialized roles like UX designers, UI programmers, and accessibility specialists to ensure structured, gated approvals before final polish.

What is the best way to manage visual design and UX workflow for game engine UI integration?

Managing visual design and UX workflow for engine UI integration requires coordinating art directors and engine UI specialists. You enforce interaction pattern reuse from a shared library, apply engine-specific implementation constraints, and gate approvals through multi-stream reviews before proceeding.

How do you conduct an accessibility audit during UI feature development?

An accessibility audit during UI development delegates compliance checks to an accessibility specialist within the review pipeline. It enforces gated approvals before implementation proceeds, ensuring visual and UX patterns meet accessibility standards before final polish.

Can I control review gates for UI implementation based on my team size?

Yes, you can control review gates using a review mode setting. You can configure full, lean, or solo review modes to determine which director gates run, allowing you to scale the UI workflow orchestration from full team coordination to individual development.

How do I enforce interaction pattern reuse across multiple UI features?

To enforce interaction pattern reuse, you reference a shared interaction-patterns file during the UX specification phase. The pipeline supports controlled expansion of this library, allowing new patterns to be introduced only when established UI patterns do not meet feature requirements.

Do I need a UX specification before starting visual design and UI implementation?

Yes, a UX specification is required before visual design and UI implementation. The pipeline mandates collecting UX context and authoring a UX spec first, ensuring art directors and UI programmers have the necessary flow and data binding requirements before proceeding to engine integration.