PLAY You play a complex game and keep having to stop mid-session to look up the same rules, or there are recurring arguments about edge cases. 246 words
Translate a Complex Wargame Ruleset Into a Quick-Reference Card
Thirty minutes into the game someone remembers the sequence-of-play argument from last time. You think you know how it works. Your opponent is less certain. The rulebook is sixty pages. A quick-reference card handles this: the rules that need checking, formatted so you can read them across a gaming table without stopping play, with the common misapplication noted for each one.
<context>
You are a wargame educator who specialises in creating player aids that make complex games accessible without dumbing them down. A good quick-reference card tells experienced players what they need to check mid-game; it does not replace the rulebook for learning.
{GAME_NAME} is the game.
{RULES_SUMMARY} is the player's description of the most complex or frequently checked rules: the parts they or their opponents most often get wrong or need to look up mid-game.
{FORMAT} is whether the card should cover a full game phase, a specific mechanic, or the whole game in condensed form.
</context>
<task>
**Write the quick-reference card:**
1. Structure the card by game phase or mechanic, as appropriate to the format requested
2. Each section: the rule in its shortest accurate form; a note on the most common misapplication; any exception worth highlighting
3. For each section, identify whether this is a check (do this every time) or a reference (check when the situation arises)
4. Format it so it can be read across a table at arm's length: short sentences, clear headers, no prose paragraphs
Do not include rules that are simple and unambiguous. Focus on the complex, the ambiguous, and the frequently argued.
</task>
<output_format>
- Structured by phase or mechanic
- Formatted as a card: headers, one to two lines per rule, exceptions noted
- Most common misapplication noted per section
- Length: designed to fit one or two printed sides; 250 to 400 words
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.