team-ui

Orchestrate UI/UX delivery from UX specs through implementation and accessibility review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of coordinating a complete UI/UX delivery workflow—so teams can move from UX specs to implementation and polish without skipping reviews, accessibility checks, or engine-specific guidance.

Core Features & Use Cases

  • Full UX pipeline orchestration: Drives the structured sequence from UX spec authoring through UX review, visual design, implementation, and polish.
  • Subagent-based team delegation: Coordinates dedicated subagents for UX design, UI programming, art direction, engine UI validation, and accessibility auditing.
  • Decision gates with user approval: Uses user-facing decision points at phase transitions to ensure the user explicitly approves before proceeding.

Quick Start

Use the team-ui skill to deliver a new UI feature by running the full pipeline: UX spec, UX review, visual design, engine-ready implementation, and accessibility and resolution checks.

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 complete game UI delivery workflow from UX specs to implementation?

Orchestrating a game UI delivery workflow involves delegating UX design, visual direction, engine-specific UI implementation, and accessibility review across structured phases. A subagent pipeline coordinates these dedicated roles, applying gated approvals to ensure iteration control and engine-safe UI structure.

What is the best way to manage UX design, visual direction, and accessibility checks for Godot UI screens?

Managing Godot UI screens effectively requires a subagent-based team delegation approach that coordinates dedicated subagents for UX design, art direction, engine UI validation, and accessibility auditing. This ensures engine-safe UI structure and localization-based text output through controlled iteration.

Can I use a subagent pipeline to add gated approvals between UX spec authoring and visual design phases?

Yes, you can use a subagent pipeline to enforce decision gates with user approval at phase transitions. This ensures you explicitly approve UX specs, visual direction, and implementation steps before the workflow proceeds to the next delivery phase.

How do I build new game UI HUDs and interaction patterns without skipping accessibility reviews?

Building accessible game UI HUDs requires a full UX pipeline orchestration that integrates accessibility review as a mandatory phase. By running dedicated accessibility auditing subagents and /ux-review verdict gates, the workflow prevents skipping critical checks during screen delivery.

Does a full UI/UX delivery workflow require reading GDD and UX sources before generating pattern libraries?

Yes, a full UI/UX delivery workflow requires reading relevant GDD, UX, and accessibility sources before generating or updating UX specs and pattern libraries. This ensures the visual design and engine-ready implementation align with established game design documents.

What are the limitations of using workflow orchestration for engine-specific UI implementation?

Workflow orchestration for engine-specific UI implementation relies heavily on subagent delegation and user-facing decision points, meaning the pipeline pauses for explicit approval at phase transitions. This gated approach ensures controlled iteration but requires active user participation to unblock progress.