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
- chuanglibs/Claude-Code-Game-Studios-Codextheir own version, first seen Nov 15, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Nov 9, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- ShiningPlague/shiningplague-studiotheir own version, first seen Oct 11, 2026
- Swih/godot-foundrytheir own version, first seen Oct 11, 2026
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.
lilangMaxSkillasset-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
lilangMaxSkillcreate-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
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same name
- tranhieutt/software_development_department★ 71same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- hongyuanc/codex-game-studios★ 5same name
- chuanglibs/Claude-Code-Game-Studios-Codex★ 1same name
- dawn840705/claude-code-studios★ 1same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asset-auditSkill
- asset-from-imageSkill
- balance-checkSkill
- brainstormSkill
- bug-reportSkill
- changelogSkill
- code-reviewSkill
- datastore-reviewSkill
- design-reviewSkill
- design-systemSkill
- doctorSkill
- economy-auditSkill
- estimateSkill
- exploit-checkSkill
- gate-checkSkill
- gddSkill
- generate-assetSkill
- hotfixSkill
- launch-checklistSkill
- luau-lintSkill
- map-systemsSkill
- milestone-reviewSkill
- monetization-modelSkill
- onboardSkill
- patch-notesSkill
- perf-profileSkill
- project-stage-detectSkill
- prototypeSkill
- publish-reviewSkill
- release-checklistSkill
- remotes-auditSkill
- retention-analysisSkill
- retrospectiveSkill
- reverse-documentSkill
- scope-checkSkill
- sprint-planSkill
- startSkill
- studio-inspectSkill
- studio-screenshotSkill
- studio-testSkill
- team-combatSkill
- team-economySkill
- team-polishSkill
- team-releaseSkill
- tech-debtSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
- wiki-seedSkill
- wiki-updateSkill
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
- Distinctive: line 23
qa-tester: Test across device sizes (mobile portrait / landscape / tablet / PC / console)
- Distinctive: line 28
game-designer: Verify UI supports intended game flow
- Distinctive: line 63
Update UI style guide if new patterns introduced
“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.
Files
/team-ui — UI Feature Team
Orchestration Flow
Phase 1: Design
- ux-designer: Wireframes and user flows
- art-director: Visual style guidance (colors, icons, font)
- writer: Copy for labels, tooltips, error messages
User reviews and approves design.
Phase 2: Implementation
- ui-programmer: Build the UI in chosen framework (Native / Roact / Fusion)
- remotes-networking-specialist (if needed): Remote contracts for data the UI needs
- accessibility-specialist: Review for contrast, text size, touch targets, screen reader support
Phase 3: Quality
- qa-tester: Test across device sizes (mobile portrait / landscape / tablet / PC / console)
- performance-analyst: Profile UI render cost on mobile
Phase 4: Integration
- ui-programmer: Hook UI into game state
- 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
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
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.

