agentleFS
Sign inStart free
scotidevscotidev/GameDevStudio/.agents/skills/team-ui/SKILL.md

team-ui

Skill1 starsChanged 8 months agoMITView on GitHub

Orchestrate the UI team: coordinates ux-designer, ui-programmer, and art-director to design, implement, and polish a user interface feature from wireframe to final.

14 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use asset-spec, create-control-manifest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • lilangMaxSkill

    asset-spec

    Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.

    Also in 9 projects that use this

  • lilangMaxSkill

    create-control-manifest

    After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).

    Also in 9 projects that use this

  • +10 more from lilangMax

The file

We split this skill into the rules it gives an agent

11 rules. 8 are common, 3 are distinctive, and 0 are very specific to this project.

  • 8

    Common

    Most of the 12 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    When this skill is invoked, orchestrate the UI team through a structured pipeline.

    line 8
  2. Common:

    Use the Task tool to spawn each team member as a subagent:

    line 22
  3. Distinctive:

    Always provide full context in each agent's prompt (feature requirements, existing UI patterns, platform targets).

    line 27
  4. Distinctive:

    Create wireframes for each screen/state

    line 34
  5. Common:

    Ensure consistency with existing UI screens

    line 45
  6. Distinctive:

    Ensure UI NEVER owns or modifies game state — display only, events for actions

    line 51
  7. Common:

    All text through localization system — no hardcoded strings

    line 52
  8. Common:

    ux-designer: Verify implementation matches wireframes and interaction spec.

    line 60
  9. Common:

    art-director: Verify visual consistency with art bible.

    line 61
  10. Common:

    Verify animations are skippable and respect motion preferences

    line 65
  11. Common:

    Test at all supported resolutions and aspect ratios

    line 67

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When this skill is invoked, orchestrate the UI team through a structured pipeline.

Decision Points: At each phase transition, use AskUserQuestion to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase.

Team Composition

  • ux-designer — User flows, wireframes, accessibility, input handling
  • ui-programmer — UI framework, screens, widgets, data binding, implementation
  • art-director — Visual style, layout polish, consistency with art bible

How to Delegate

Use the Task tool to spawn each team member as a subagent:

  • subagent_type: ux-designer — User flows, wireframes, accessibility, input handling
  • subagent_type: ui-programmer — UI framework, screens, widgets, data binding
  • subagent_type: art-director — Visual style, layout polish, art bible consistency

Always provide full context in each agent's prompt (feature requirements, existing UI patterns, platform targets). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 4 review agents can run simultaneously).

Pipeline

Phase 1: UX Design

Delegate to ux-designer:

  • Define the user flow for this feature (entry points, states, exit points)
  • Create wireframes for each screen/state
  • Specify interaction patterns: how does keyboard/mouse AND gamepad navigate this?
  • Define accessibility requirements: text sizes, contrast, colorblind safety
  • Identify data the UI needs to display (what game state does it read?)
  • Output: UX spec with wireframes and interaction map

Phase 2: Visual Design

Delegate to art-director:

  • Review wireframes against the art bible
  • Define visual treatment: colors, typography, spacing, animations
  • Specify asset requirements (icons, backgrounds, decorative elements)
  • Ensure consistency with existing UI screens
  • Output: visual design spec with style notes

Phase 3: Implementation

Delegate to ui-programmer:

  • Implement the UI following the UX spec and visual design
  • Ensure UI NEVER owns or modifies game state — display only, events for actions
  • All text through localization system — no hardcoded strings
  • Support both input methods (keyboard/mouse + gamepad)
  • Implement accessibility features (text scaling, colorblind mode support)
  • Wire up data binding to game state
  • Output: implemented UI feature

Phase 4: Review (parallel)

Delegate in parallel:

  • ux-designer: Verify implementation matches wireframes and interaction spec. Test keyboard-only and gamepad-only navigation. Check accessibility.
  • art-director: Verify visual consistency with art bible. Check at minimum and maximum supported resolutions.

Phase 5: Polish

  • Address review feedback
  • Verify animations are skippable and respect motion preferences
  • Confirm UI sounds trigger through audio event system
  • Test at all supported resolutions and aspect ratios

Output

A summary report covering: UX spec status, visual design status, implementation status, accessibility compliance, input method support, and any outstanding issues.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free