team-ui

Orchestrates an end-to-end game UI production workflow from UX specification to review.

Updated Dec 22, 2024
One-click install
npx skills add https://github.com/imgamer/AILearn --skill team-ui-imgamer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/team-ui
Command: npx skills add https://github.com/imgamer/AILearn --skill team-ui-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates a complete UI production workflow—UX spec, review, visual design, engine guidance, implementation, and polish—so teams can deliver consistent, accessible UI features without skipping critical checks.

Core Features & Use Cases

  • Full UX-to-implementation pipeline: Coordinates ux-designer, ui-programmer, art-director, an engine UI specialist, and an accessibility specialist across sequential and parallel phases.
  • Review-gated quality control: Enforces an approval gate after UX review and consolidates parallel review feedback before polish.
  • Reusable interaction patterns: Reuses existing interaction-patterns when present and updates the pattern library when new patterns are introduced.
  • Configurable review mode: Supports full, lean, and solo review modes (including conditional director-gate skipping rules).
  • Accessibility-aware implementation: Runs input-method and accessibility validation against the committed accessibility tier.

Quick Start

Use the team-ui skill to deliver a full UI feature by running it for your target UI feature description and optionally selecting a review mode.

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 game UI production workflow from UX spec to implementation?

A game UI production workflow can be managed by orchestrating sequential phases from UX specification through visual design, engine-specific implementation guidance, and final review. This ensures consistent, accessible UI features while enforcing critical approval gates.

How does review gating work for game UI features?

Review gating for game UI features works by enforcing an approval gate after the UX review phase and consolidating parallel feedback from art directors and accessibility specialists before the final polish phase. This prevents skipping critical interaction pattern and accessibility checks.

Can I configure the UI review process for solo development versus full team production?

You can configure the UI review process using full, lean, or solo review modes. These modes include conditional director-gating rules that skip specific approval phases, allowing the pipeline to scale from independent development to full multi-agent team production.

Does this game UI pipeline handle accessibility and input method validation?

Yes, the game UI pipeline handles accessibility by running input-method and accessibility validation against your committed accessibility tier. This ensures new UI screens and HUD features meet existing localization, input method, and accessibility commitments before implementation.

What is the best way to ensure new game UI screens follow existing interaction patterns?

The best way to ensure new game UI screens follow existing interaction patterns is to use a pipeline that reuses committed pattern libraries during the UX specification phase. This pipeline automatically updates the library when new patterns are introduced and validated during the review process.

How to get engine-specific implementation guidance for game UI features?

To get engine-specific implementation guidance for game UI features, run a coordinated pipeline that delegates tasks to an engine UI specialist. This specialist provides integration instructions alongside UX specs and visual designs, ensuring the implementation matches engine requirements before coding begins.