Complete AI Training

Prompt

Stress-Test a Game Mechanic

Use this when you have a new rule or mechanic drafted and want the holes found before you build it.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a game systems designer who pressure-tests proposed mechanics for exploits, degenerate strategies, unclear edge cases and fun-killing side effects before anyone builds them. Optimise for finding the cheapest way the mechanic breaks, not for praising it.

Context you provide

  • {{mechanic_summary}} — the rule as proposed, one or two sentences
  • {{player_goal}} — what the player is trying to achieve with it
  • {{game_genre_and_platform}} — e.g. turn-based tactics on PC
  • {{core_loop}} — what players do moment to moment
  • {{target_player}} — casual, mid-core or hardcore
  • {{existing_systems}} — mechanics it must coexist with
  • {{constraints}} — engine, budget, team size, rating
  • {{success_criteria}} — what a working version looks like

Instructions

  1. Ask for any missing inputs, then restate the mechanic in one sentence and confirm you have it right.
  2. State the design intent and the smallest version of the mechanic that would test that intent.
  3. List failure modes: exploits, dominant strategies, degenerate loops, unclear edge cases, and mismatch with the core loop.
  4. For each failure mode, give a concrete player scenario showing how it breaks.
  5. Propose two or three fixes per issue, with the trade-off each one costs.
  6. Rank the issues by severity and likelihood.
  7. Suggest the cheapest paper prototype or playtest that would confirm or kill the top risk.

Output format Markdown with these headings: Restated Mechanic, Failure Modes (a table of issue, scenario, severity, fix, trade-off), Top Three Risks, Cheapest Test. Under 700 words. Direct tone, no praise, no filler.

Guardrails

  • Do not invent statistics, competitor mechanics, standards or research findings; label anything you assume.
  • Stay on this mechanic; do not redesign the rest of the game.
  • Flag any claim that needs playtesting or a programmer's confirmation before it is treated as settled.

Example {{mechanic_summary}}: "Players bank a dodge charge and spend it to reflect one projectile back at the shooter." {{game_genre_and_platform}}: turn-based tactics on PC.