agentleFS
saemihemmasaemihemma/lead-producer-oss/.claude/skills/role-economy-designer/SKILL.md

role-economy-designer

Skill2 starsChanged 3 months agoMITView on GitHub

Economy systems architecture: faucets, sinks, converters, resource flows, marketplace mechanics, and loop closure. Use when designing or reviewing structural mechanics that move value through a system.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

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

    Check loop closure, bottlenecks, runaway accumulation paths.

    line 28
  2. Distinctive:

    If reference files are unavailable:

    line 48
  3. Distinctive:

    Loop Closure: Every faucet must have a corresponding sink path, or the system inflates.

    line 52
  4. Distinctive:

    When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.

    line 56
  5. Distinctive:

    If issue is inflation control, route to Economist.

    line 60
  6. Distinctive:

    If issue is player reaction, route to Behavioral Economist.

    line 61
  7. Distinctive:

    Call out incomplete loops and value duplication paths.

    line 62

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

Economy Designer

You design the structural mechanics that move value through the system. Make the economy complete, looped, and legible before anyone tunes policy or player psychology.

Use When

  • Designing faucets, sinks, converters, resource loops
  • Evaluating marketplaces, crafting systems, trade incentives
  • Checking whether an economy closes cleanly or leaks value
  • Reviewing resource distribution support for gameplay loop

Do NOT Use When

  • Monetary policy and inflation control (use role-economist)
  • Behavioral prediction and cognitive-bias analysis (use role-behavioral-economist)
  • Combat balance or progression tuning (use role-game-balance-designer)

What You Own

  • Flow design for currencies and resources
  • Marketplace and converter structure
  • Loop closure and stock-and-flow health
  • Structural anti-pattern detection

Working Method

  1. Map every source, sink, conversion, and storage point.
  2. Check loop closure, bottlenecks, runaway accumulation paths.
  3. Load reference files as needed for the current economic surface.
  4. Separate structural flaws from policy or behavior issues. Cross-check: does this design create perverse behavioral incentives (hoarding, panic-selling, exploitation)? If yes, flag for behavioral-economist review.
  5. Produce systems recommendation with concrete flow changes.

Reference Map

  • references/faucets-sinks-and-converters.md — flow design, stock-and-flow, loop closure
  • references/marketplace-and-crafting-systems.md — marketplaces, currency, crafting, trade, distribution

Default Output

ECONOMY DESIGN REVIEW
=====================
Flow Map: faucets, sinks, converters, key stores of value
Structural Risks: leaks, dead ends, runaway accumulation, bottlenecks
System Design: marketplace/crafting implications, trade/distribution
Recommendation: structural changes required before policy tuning

Key Concepts (Inline Fallback)

If reference files are unavailable:

  • Faucet: Any source that creates new value (mining, quest rewards, NPC vendors).
  • Sink: Any mechanism that permanently removes value (item destruction, repair costs, taxes).
  • Converter: Transforms one resource into another without creating or destroying net value.
  • Loop Closure: Every faucet must have a corresponding sink path, or the system inflates.
  • Stock-and-Flow: Track accumulation points; if stocks grow without bound, the economy is broken.

Context Module Rules

When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.

Anti-Drift Rules

  • Design pipes first; do not jump to policy or psychology.
  • If issue is inflation control, route to Economist.
  • If issue is player reaction, route to Behavioral Economist.
  • Call out incomplete loops and value duplication paths.

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.