agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/team-ui/SKILL.md

team-ui

Skill9 starsChanged 7 months agoMITView on GitHub

Multi-agent orchestration for UI features. Coordinates ux-designer, ui-programmer, art-director, accessibility-specialist, and writer to build a new UI feature end-to-end.

15 other projects use a version of this.

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

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

  • 0

    Common

    Most of the 14 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. Distinctive:

    qa-tester: Test across device sizes (mobile portrait / landscape / tablet / PC / console)

    line 23
  2. Distinctive:

    game-designer: Verify UI supports intended game flow

    line 28
  3. Distinctive:

    Update UI style guide if new patterns introduced

    line 63

“Common” is measured: kept by at least 6 in 10 of the 14 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

/team-ui — UI Feature Team

Orchestration Flow

Phase 1: Design

  1. ux-designer: Wireframes and user flows
  2. art-director: Visual style guidance (colors, icons, font)
  3. writer: Copy for labels, tooltips, error messages

User reviews and approves design.

Phase 2: Implementation

  1. ui-programmer: Build the UI in chosen framework (Native / Roact / Fusion)
  2. remotes-networking-specialist (if needed): Remote contracts for data the UI needs
  3. accessibility-specialist: Review for contrast, text size, touch targets, screen reader support

Phase 3: Quality

  1. qa-tester: Test across device sizes (mobile portrait / landscape / tablet / PC / console)
  2. performance-analyst: Profile UI render cost on mobile

Phase 4: Integration

  1. ui-programmer: Hook UI into game state
  2. game-designer: Verify UI supports intended game flow

Steps

1. Gather Context

Ask:

  • "What UI feature?" (new menu, new HUD element, new modal, etc.)
  • "When does the player see it?"
  • "What data does it show?"
  • "What actions can the player take through it?"

2. Design Phase

  • ux-designer presents wireframe (ASCII or described)
  • art-director suggests visual palette
  • writer drafts copy
  • User approves the combined design

3. Implementation Phase

  • ui-programmer implements
  • accessibility-specialist reviews draft
  • ui-programmer applies accessibility fixes
  • Runs the UI in Studio for visual verification

4. Quality Phase

  • qa-tester runs device coverage matrix:
    • Mobile portrait 375x667
    • Mobile landscape 844x390
    • Tablet 1024x768
    • Desktop 1920x1080
    • Console 1920x1080 with gamepad
  • performance-analyst checks FPS impact

5. Integration Phase

  • Hook up state
  • Link to opening/closing triggers
  • Update UI style guide if new patterns introduced

Output

A complete UI feature: wireframe → design → implementation → accessibility pass → device-tested → integrated.

Quality Checks

  • Touch targets ≥ 44×44 px
  • Text contrast ≥ 4.5:1
  • Readable at smallest supported device (375×667)
  • Gamepad navigable
  • Screen reader friendly (AccessibleName set)
  • No regressions on other UI
  • Performance: no FPS drop on mobile

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.