team-ui

Orchestrate cross-disciplinary UI work from wireframes to polished interface.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill team-ui-jtvaris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: team-ui
Source: https://github.com/jtvaris/sunday-night-dynasty/tree/main/.agents/skills/team-ui
Command: npx skills add https://github.com/jtvaris/sunday-night-dynasty --skill team-ui-jtvaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates cross-disciplinary UI work to ensure a UI feature moves from wireframes to a polished final product, reducing handoff friction and misalignment.

Core Features & Use Cases

  • End-to-end UI feature orchestration across UX designer, UI programmer, and art director.
  • Phase-driven workflow with explicit decision points and parallel reviews.
  • Keeps UI implementation separate from game state logic, with localization and accessibility considerations.

Quick Start

Instruct the subagents to begin the UX design, create wireframes, and start the phase-driven pipeline.

Frequently Asked Questions about team-ui

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

FAQPage Schema
How do I coordinate UI teams to move a feature from wireframes to a polished interface?

Cross-disciplinary UI coordination is handled through a phase-driven workflow that orchestrates UX designers, UI programmers, and art directors with explicit decision points, parallel reviews, and clear handoffs to produce a polished final interface.

What is the best way to manage handoffs between UX designers and UI programmers?

Managing handoffs between UX designers and UI programmers requires a phase-driven pipeline with explicit decision points and parallel reviews, ensuring alignment and reducing friction when moving from wireframes to implementation.

How do I keep UI implementation separate from game state logic during art direction?

To keep UI implementation separate from game state logic during art direction, use a coordinated workflow that isolates interface polish and localization considerations from core state mechanics through structured handoffs.

Can I include localization and accessibility considerations in a phase-driven UI workflow?

Yes, localization and accessibility considerations are explicitly integrated into the phase-driven UI workflow, ensuring these requirements are addressed during the coordinated progression from wireframes to the final interface.

When do I need a dedicated UI team coordination workflow instead of a single designer?

A dedicated UI team coordination workflow is needed when a project requires parallel effort from a UX designer, UI programmer, and art director to move a feature from concept through implementation and polish without misalignment.