team-combat
Skill9 starsChanged 7 months agoMITView on GitHub
Multi-agent orchestration for combat features. Coordinates game-designer, systems-designer, luau-gameplay-programmer, technical-artist, sound-designer, and exploit-security-specialist to tackle a combat feature end-to-end.
14 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
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- Donchitos/Claude-Code-Game-Studios★ 39ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 124same 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
- HunLuanZhiZhu/Game-Studios-Plugin★ 1same name
4 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-economySkill
- team-polishSkill
- team-releaseSkill
- team-uiSkill
- 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
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
ui-programmer: Update HUD / damage numbers / health bar
- Distinctive: line 34
qa-tester: Write test plan and execute
- Distinctive: line 40
producer: Update sprint plan, systems-index
- Distinctive: line 59
If a phase reveals a blocker (e.g., exploit-security-specialist says the design is unsafe):
- Distinctive: line 62
Wait for user to resolve
- Very specific: line 67
Update the combat GDD (design/gdd/combat-gdd.md)
- Distinctive: line 68
Update the remotes manifest
- Distinctive: line 69
Update the systems-index status
- Distinctive: line 70
Add an entry to the changelog
“Common” is measured: kept by at least 6 in 10 of the 13 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-combat — Combat Feature Team
Orchestration Flow
Combat features touch many specialists. This skill coordinates them.
Phase 1: Design
- game-designer: Define the feature — what mechanic, what player intent, how it feels
- systems-designer: Translate into detailed spec with formulas, edge cases, data schema
User reviews and approves the design before moving to Phase 2.
Phase 2: Architecture
- lead-programmer: Plan the implementation architecture
- remotes-networking-specialist: Design the client-server contract
- exploit-security-specialist: Review for attack surface (speed hacks, damage exploits, duplication)
User reviews the architecture before Phase 3.
Phase 3: Implementation
- luau-gameplay-programmer: Implement the combat logic
- technical-artist: Implement VFX (particles, beams, trails)
- sound-designer: Implement audio triggers
- ui-programmer: Update HUD / damage numbers / health bar
Each sub-step goes through the Question → Options → Decision → Draft → Approval flow.
Phase 4: Quality
- qa-tester: Write test plan and execute
- performance-analyst: Profile the feature on mobile
- exploit-security-specialist: Final security pass
Phase 5: Integration
- game-designer: Balance tuning (damage, cooldowns, etc.)
- producer: Update sprint plan, systems-index
Steps
1. Gather Context
Ask:
- "What combat feature are we building?" (new weapon, new ability, new enemy, etc.)
- "What's the intended player experience?"
- "What systems does this touch?" (just combat, or also inventory/progression/UI?)
- "What's the scope?" (afternoon prototype, full sprint feature, multi-sprint feature)
2. Delegate Through Each Phase
For each phase:
- Announce which specialist is about to work
- Have that specialist produce a draft
- Present to user for approval
- On approval, move to next phase
3. Handle Blockers
If a phase reveals a blocker (e.g., exploit-security-specialist says the design is unsafe):
- Pause the flow
- Escalate to the director (technical-director for tech blockers, creative-director for design blockers)
- Wait for user to resolve
- Resume the flow
4. Document the Feature
After completion:
- Update the combat GDD (
design/gdd/combat-gdd.md) - Update the remotes manifest
- Update the systems-index status
- Add an entry to the changelog
Output
A complete combat feature: design doc + code + VFX + audio + tests + security review.
Example Use
User: "Let's add a parry mechanic to combat" Flow:
- game-designer drafts the parry concept
- systems-designer specifies windows, timing, counter-attack damage
- remotes-networking-specialist adds ParryRemoteEvent with validation
- exploit-security-specialist checks for timing exploits
- luau-gameplay-programmer implements
- technical-artist adds the parry flash VFX
- sound-designer adds the parry sound
- ui-programmer updates HUD to show parry window indicator
- qa-tester writes test plan, tests edge cases
- performance-analyst verifies no FPS impact
- game-designer tunes timing windows based on playtest
- producer updates sprint plan
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.

