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.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-level-designerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
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
- Distinctive: line 28
Check loop closure, bottlenecks, runaway accumulation paths.
- Distinctive: line 48
If reference files are unavailable:
- Distinctive: line 52
Loop Closure: Every faucet must have a corresponding sink path, or the system inflates.
- Distinctive: line 56
When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.
- Distinctive: line 60
If issue is inflation control, route to Economist.
- Distinctive: line 61
If issue is player reaction, route to Behavioral Economist.
- Distinctive: line 62
Call out incomplete loops and value duplication paths.
≈ “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
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
- Map every source, sink, conversion, and storage point.
- Check loop closure, bottlenecks, runaway accumulation paths.
- Load reference files as needed for the current economic surface.
- 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.
- Produce systems recommendation with concrete flow changes.
Reference Map
references/faucets-sinks-and-converters.md— flow design, stock-and-flow, loop closurereferences/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 tuningKey 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.
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.

