team-economy
Skill9 starsChanged 7 months agoMITView on GitHub
Multi-agent orchestration for economy features. Coordinates economy-designer, monetization-lead, systems-designer, datastore-architect, ui-programmer, and exploit-security-specialist.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ShiningPlague/shiningplague-studiotheir own version, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ShiningPlague/shiningplague-studio★ 0same name
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-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. 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.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
monetization-lead: If Robux is involved, design GamePass/DevProduct
- Distinctive: line 29
analytics-retention-specialist: Add telemetry events to track economy health
- Distinctive: line 32
qa-tester: Test edge cases (zero balance, max balance, race conditions)
- Distinctive: line 45
If monetized, monetization-lead joins
- Very specific: line 63
Run /balance-check on the new feature
- Distinctive: line 68
Test: buy with exact balance, with insufficient balance, with max items
- Distinctive: line 69
Test: rapid repeated purchase (debouncing)
- Distinctive: line 71
Test: trade with another player (if applicable), trade during mid-save
- Distinctive: line 72
Test: transaction while DataStore is slow
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
/team-economy — Economy Feature Team
Orchestration Flow
Economy features have the highest stakes — mistakes can cause inflation, exploits, or monetization disasters.
Phase 1: Design
- economy-designer: Design the feature's currency flow (faucets, sinks, pacing)
- monetization-lead: If Robux is involved, design GamePass/DevProduct
- systems-designer: Spec the feature in detail
Phase 2: Architecture
- datastore-architect: Design the data model changes
- remotes-networking-specialist: Design remote contracts
- exploit-security-specialist: Review for duplication, replay, negative value exploits
- technical-director (escalation): Verify atomicity of any transactions
Phase 3: Implementation
- luau-gameplay-programmer: Implement feature logic
- ui-programmer: Build shop/trade/transaction UI
Phase 4: Balance
- economy-designer: Tune values (prices, drop rates, earn rates)
- analytics-retention-specialist: Add telemetry events to track economy health
Phase 5: Quality
- qa-tester: Test edge cases (zero balance, max balance, race conditions)
- exploit-security-specialist: Final security pass
Steps
1. Gather Context
- "What economy feature?" (new currency, shop, trading, cosmetic, etc.)
- "What's the player value?"
- "What's the intended earn rate / spend rate?"
- "Is this F2P-friendly or does it require Robux?"
2. Design Phase
- economy-designer drafts the feature
- If monetized, monetization-lead joins
- systems-designer details the spec
- User approves before architecture
3. Architecture Phase
- datastore-architect designs data changes (schema update with migration)
- remotes-networking-specialist designs remote contracts
- exploit-security-specialist reviews — THIS IS CRITICAL for economy features
- User approves the architecture (especially the security review)
4. Implementation Phase
- Implement with atomic operations where needed
- Transaction tracking with unique IDs
- Server-side validation on every step
- pcall around DataStore
- Idempotency for MarketplaceService.ProcessReceipt
5. Balance Phase
- Run
/balance-checkon the new feature - Model projected economy impact over 30 days
- Tune values based on projections
6. Quality Phase
- Test: buy with exact balance, with insufficient balance, with max items
- Test: rapid repeated purchase (debouncing)
- Test: disconnect mid-purchase
- Test: trade with another player (if applicable), trade during mid-save
- Test: transaction while DataStore is slow
Output
A complete economy feature: design → data model → atomic implementation → secure → balanced → tested.
Quality Checks
- No duplication vectors
- No negative value exploits
- Atomic transactions
- Idempotent purchase processing
- Schema migration (if needed) tested
/economy-auditpasses/exploit-checkpasses- Telemetry events added
- Balance modeled and reasonable
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.

