agentleFS
CodePhobiiaCodePhobiia/claude-roblox-game-studio/.claude/skills/team-economy/SKILL.md

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

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
  1. Distinctive:

    monetization-lead: If Robux is involved, design GamePass/DevProduct

    line 14
  2. Distinctive:

    analytics-retention-specialist: Add telemetry events to track economy health

    line 29
  3. Distinctive:

    qa-tester: Test edge cases (zero balance, max balance, race conditions)

    line 32
  4. Distinctive:

    If monetized, monetization-lead joins

    line 45
  5. Very specific:

    Run /balance-check on the new feature

    line 63
  6. Distinctive:

    Test: buy with exact balance, with insufficient balance, with max items

    line 68
  7. Distinctive:

    Test: rapid repeated purchase (debouncing)

    line 69
  8. Distinctive:

    Test: trade with another player (if applicable), trade during mid-save

    line 71
  9. Distinctive:

    Test: transaction while DataStore is slow

    line 72

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/team-economy — Economy Feature Team

Orchestration Flow

Economy features have the highest stakes — mistakes can cause inflation, exploits, or monetization disasters.

Phase 1: Design

  1. economy-designer: Design the feature's currency flow (faucets, sinks, pacing)
  2. monetization-lead: If Robux is involved, design GamePass/DevProduct
  3. systems-designer: Spec the feature in detail

Phase 2: Architecture

  1. datastore-architect: Design the data model changes
  2. remotes-networking-specialist: Design remote contracts
  3. exploit-security-specialist: Review for duplication, replay, negative value exploits
  4. technical-director (escalation): Verify atomicity of any transactions

Phase 3: Implementation

  1. luau-gameplay-programmer: Implement feature logic
  2. ui-programmer: Build shop/trade/transaction UI

Phase 4: Balance

  1. economy-designer: Tune values (prices, drop rates, earn rates)
  2. analytics-retention-specialist: Add telemetry events to track economy health

Phase 5: Quality

  1. qa-tester: Test edge cases (zero balance, max balance, race conditions)
  2. 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-check on 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-audit passes
  • /exploit-check passes
  • Telemetry events added
  • Balance modeled and reasonable

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.