game-meta
Skill0 starsChanged 33 days agoLicence not identifiedView on GitHub
Design and tune a game's meta and monetization from real data. Covers loot boxes, chests and drop tables (rarity tiers, expected value, soft and hard pity, the 50/50 featured guarantee, duplicates), gacha odds disclosure, the shop, starter packs and offers, the season pass, subscriptions and rewarded ads, soft, hard and event currencies with a faucet and sink ledger, price ladders, premium budgets, progression and the difficulty curve across sessions, rescue gifts only after a fall, retention loops, and ethical guardrails (odds laws, no dark patterns, minors). Ships a drop-table calculator and an economy ledger checker. Use when the user says "design the loot boxes", "add a gacha", "is this gacha fair", "add a pity system", "too many coins", "nothing to spend coins on", "add a season pass", "price the starter pack", "players quit on day 2", "the gift shows up for players who win", or asks about currencies, sinks, offers, monetization or retention.
- Deletes or force-pushes
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-orchestrationSkill
- design-boardsSkill
- feature-designSkill
- game-balanceSkill
- game-feel-audioSkill
- game-metaSkill
- game-qaSkill
- game-trailerSkill
- game-ui-kitSkill
- game-vfxSkill
- progressSkill
- studioSkill
- agent-orchestrationSkill
- design-boardsSkill
- feature-designSkill
- game-balanceSkill
- game-feel-audioSkill
- game-metaSkill
- game-qaSkill
- game-trailerSkill
- game-ui-kitSkill
- game-vfxSkill
- progressSkill
- studioSkill
- agent-orchestrationSkill
- design-boardsSkill
- feature-designSkill
- game-balanceSkill
- game-feel-audioSkill
- game-qaSkill
- game-trailerSkill
- game-ui-kitSkill
- game-vfxSkill
- progressSkill
- studioSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.