balance-check
Skill9 starsChanged 7 months agoMITView on GitHub
Check game balance — damage formulas, XP curves, drop rates, difficulty scaling. Verifies formulas are explicit and values are in config, not magic numbers.
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
- Swih/godot-foundrytheir own version, first seen Oct 11, 2026
- scotidev/GameDevStudiotheir own version, first seen Oct 9, 2026
Used with
Projects with it also use soak-test, team-live-ops 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.
lilangMaxSkillsoak-test
Generate a soak test protocol for extended play sessions. Defines what to observe, measure, and log during long play sessions to surface slow leaks, fatigue effects, and edge cases that only appear after sustained play. Primarily used in Polish and Release phases.
Also in 5 projects that use this
lilangMaxSkillteam-live-ops
Orchestrate the live-ops team for post-launch content planning: coordinates live-ops-designer, economy-designer, analytics-engineer, community-manager, writer, and narrative-director to design and plan a season, event, or live content update.
Also in 5 projects that use this
- +10 more from lilangMax
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
- cenconq25/claude-code-app-studio★ 40same 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
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
- 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
- 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
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 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 13
Ask: "Which system or formula are we checking?"
- Distinctive: line 14
Default: All tunable systems (combat, progression, economy)
- Distinctive: line 17
Search for relevant code:
“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
/balance-check — Game Balance Verification
Delegate to: game-designer (with systems-designer for formula review)
Steps
1. Identify What to Check
Ask: "Which system or formula are we checking?"
- Default: All tunable systems (combat, progression, economy)
2. Locate Formulas
Search for relevant code:
grep -rn "damage\|XP\|drop\|spawn" src/ --include="*.lua" --include="*.luau"
grep -rn "config\|CONFIG\|Config" src/ReplicatedStorage/3. Verify Each Formula
Checklist per formula:
- Formula explicitly written (not buried in complex code)
- Constants externalized to config module
- Formula documented in relevant GDD
- Formula result bounded (no infinite scaling without cap)
- Edge cases handled (zero inputs, negative, max)
4. Simulate the Curve
For each formula, tabulate values across the expected input range:
Damage example:
Level | Base ATK | Weapon | Total Damage (avg)
------|----------|--------|--------------------
1 | 10 | 5 | 15
5 | 20 | 15 | 35
10 | 35 | 30 | 65
20 | 60 | 60 | 120
50 | 150 | 150 | 300
100 | 300 | 300 | 600XP curve example:
Level | XP to next | Cumulative XP | Hours to reach (at 500 XP/hr)
------|------------|---------------|------------------------------
1 → 2 | 100 | 100 | 0.2
5 → 6 | 500 | 1500 | 3
10 → 11 | 2000 | 9500 | 19
20 → 21 | 10000 | 75000 | 150
50 → 51 | 100000 | 2000000 | 40005. Flag Balance Issues
- Too steep: Grind feels unfair (target: fun, not punishing)
- Too shallow: Player outgrows content too fast
- Discontinuities: Sudden difficulty spikes
- Unbounded: Values that can grow infinitely without cap
- Undefined edges: What happens at max level / zero input?
6. Recommend Adjustments
For each issue, propose concrete changes:
Issue: XP curve at level 50 requires 4000 hours
Recommendation: Cap XP requirement at 50000 per level (reduces to 100 hours)
Impact: Whale players won't grind forever; retention curve healthier7. Generate Balance Report
# Balance Check: [System Name]
## Formulas Reviewed
1. [Formula 1] — status
2. [Formula 2] — status
## Curve Analysis
[Tables showing curves]
## Issues Found
### Critical
1. [Issue with recommendation]
### Important
1. ...
### Minor
1. ...
## Recommendations
1. [Concrete change 1]
2. [Concrete change 2]
## Not Yet Verified
- [Systems that need play testing to confirm balance]Present the report. Offer to delegate fixes to systems-designer.
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.

