monetization-guardrails

name	monetization-guardrails
description	Review monetization design for fairness, player trust, platform constraints, and ethical guardrails. Use for F2P offers, bundles, ads, battle passes, or economy pressure.

Monetization Guardrails

When to use

Review monetization design for fairness, player trust, platform constraints, and ethical guardrails. Use for F2P offers, bundles, ads, battle passes, or economy pressure.

Inputs to gather

• monetization concept
• target platform
• economy context
• revenue constraints

Recommended roles

• monetization_guardian
• economy_designer
• community_manager

Primary docs / outputs

• studio/docs/templates/monetization-guardrails.md
• studio/docs/templates/storefront-checklist.md

Workflow

1. Inspect the current repo/docs state first and cite concrete evidence.
2. Choose the smallest useful output that moves the project forward.
3. Express the work as a feature, mechanic, or content contract that engineering and QA can consume.
4. Update or create durable docs when the result should persist.
5. Recommend the next best role or skill if more work remains.

Category rules

• Lead with player outcome, then define scope, acceptance criteria, and edge cases.
• Keep mechanics and content contracts buildable by engineering and testable by QA.
• Surface tradeoffs among clarity, depth, scope, and production cost.

Deliverables

• guardrail policy
• red flags
• allowed/forbidden patterns
• copy/comms notes

Validation bar

• acceptance criteria present
• risks/dependencies surfaced
• next implementation or test path clear