skills.rest
imclab
imclabOFFICIAL
Explore all skills by this author →
Website𝕏@TheIMCLabGitHub

team-ui

Orchestrate UI production from UX spec authoring through implementation and QA reviews.

1|Updated May 3, 2026
Search Tags:#accessibility#localization#design review#interaction patterns#ui implementation#engine ui#ux pipeline
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill team-ui-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/team-ui
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill team-ui-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the chaos of ad-hoc UI development by orchestrating a full, spec-driven UX pipeline with explicit reviews, accessibility checks, and user-approved phase gates so the UI is correct before polish.

Core Features & Use Cases

  • UX spec authoring: Produces design/ux/[feature-name].md (or HUD-specific hud-design.md) from GDD requirements, player journey context, and reusable interaction patterns.
  • Structured multi-stream review: Runs UX review for approval, plus parallel visual-design and accessibility compliance validation before implementation continues.
  • Engine-aware implementation handoff: Optionally gathers engine-specific UI guidance (from the Engine Specialists UI Specialist) and delegates implementation to a UI programmer that supports patterns, localization, input methods, and data binding.
  • Interaction pattern governance: Prevents reinventing patterns by enforcing use of design/ux/interaction-patterns.md, while updating it when new patterns are introduced.
  • Use Case: Build a new screen (or HUD) end-to-end, from UX spec through implementation and accessibility/compliance review, without losing alignment across designers and developers.

Quick Start

Ask the system to run team-ui for your UI feature by providing a short UI feature description, and then approve each phase transition when prompted.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I manage a UX to UI implementation pipeline for game features?▼

A complete UX-to-UI pipeline orchestrates end-to-end UI production by turning proposed features into implemented and reviewed interfaces. It requires phase-gated user decisions and strict delegation to subagents for UX spec authoring, visual design, implementation, and accessibility compliance checks.

What is the best way to ensure UI accessibility compliance during game development?▼

UI accessibility compliance is achieved by running parallel visual-design and accessibility validation checks against design requirements before implementation. This includes enforcing keyboard and gamepad input support and localization checks during structured multi-stream reviews.

How do I structure UX spec authoring for a new game HUD or screen?▼

UX spec authoring for a new HUD or screen produces structured markdown files from GDD requirements, player journey context, and reusable interaction patterns. This spec output drives structured multi-stream reviews and engine-aware implementation handoff.

Does this UI pipeline support engine-specific implementation and coding handoff?▼

Yes, the pipeline supports engine-specific implementation by optionally gathering engine-specific UI guidance and delegating coding to a UI programmer. This ensures implementation supports established interaction patterns, localization, input methods, and data binding.

How do I prevent reinventing interaction patterns across different UI features?▼

Preventing reinvented interaction patterns requires enforcing the use of a shared interaction patterns file during UX spec authoring and UI implementation. This governance approach ensures consistency and updates the pattern library automatically when new patterns are introduced.

Can I use this pipeline for both HUD design and full-screen menu interfaces?▼

Yes, the pipeline applies to both HUD design and full-screen menu interfaces by producing either hud-specific or feature-specific UX specs. Both interface types undergo structured multi-stream reviews, engine-aware handoff, and accessibility compliance checks.

Related Skills

Explore More Design & Creative Skills→
kay6198835kay6198835

ux-design

Create structured UX specifications for game screens, flows, and HUDs.

Community
Advanced
Tristan578Tristan578
5

builder

Translate feature specs into Rust, UI, MCP, and test code.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

team-ui

Coordinate UI feature design, implementation, review, and polish across a UX pipeline.

Community
Advanced
tomada1114tomada1114
4

ui-ux-designing

Creates design-concept documents for app and web service UI/UX.

Community
Intermediate