How to Use the Board Game Rulebook Prompt to Teach a Prototype in Five Minutes

Playtesters do not fail your game because they are careless. They fail because the turn structure has three names for the same action and the scoring example never matches the board in front of them. The Board Game Rulebook and Player Aid Writer: Setup Order, Turn Structure, Scoring Examples, Edge Case FAQ, and a One Page Reference Card prompt takes a prototype brief and returns a teachable rulebook draft: setup order, turn phases, worked scoring, an edge case FAQ, and a one page player aid that uses the same words as the book.

What the prompt produces

1. A three sentence cover blurb that states the hook, the verb loop, and the win condition without publisher fluff.
2. A components checklist with counts and a first game sorting tip so open boxes go faster.
3. Numbered setup ending with who starts and how that is chosen.
4. A turn structure whose phase names match your core verbs exactly.
5. Two worked scoring examples with concrete pretend board states and arithmetic people can check.
6. An FAQ aimed at the confusing moments you already saw in playtests, plus ties and empty supplies.
7. A one page player aid and a forbidden synonym list so the aid does not drift from the book after layout.

How to fill the inputs

GameProfile needs player count, age, and time target. Those numbers shape tone more than flavor text does.

CoreLoop should be verbs only: draft, place, deliver, refresh. If you write theme flavor instead of verbs, the turn structure gets mushy and hard to teach.

Components must include counts. "Some cards" is how rulebooks lie and how first games stall.

PlaytestPain is mandatory. Paste the exact moments people froze, argued, or called you over. The FAQ is only as good as this list.

ToneAndBanned lets you ban words like "engine" for a family game or demand euro precision for a heavier title. Use it.

Reading the example output

Harbor Lights is a light pier placement game in the sample. The output shows:

• Deliver is optional but still has a named slot in the turn, so people stop forgetting it after the draft.
• Scoring examples use named players and coin totals, not abstract "Player A gains points" lines that nobody can verify.
• The FAQ covers ties, empty markets, and crate shortages instead of inventing publisher lore or fake FAQs.
• The term list forbids synonyms, which is the difference between a clean five minute teach and a twenty minute argument about what "resolve" means.

Tips for better results

• Run the prompt after every major playtest, not once at the end when layout is already locked.
• Keep the player aid on one page even if you have to cut flavor paragraphs from the book.
• Mark designer decisions with a clear tag instead of letting the model invent a ruling you did not make.
• Read the rulebook aloud to a new player without coaching, then feed their confusion straight back into PlaytestPain.
• When two verbs mean the same thing in your notes, pick one before you paste CoreLoop.

Mistakes to avoid

• Do not rename phases between the book and the aid. Players notice immediately.
• Do not skip worked examples. Arithmetic is where trust dies at the table.
• Do not invent MSRP, BGG ranks, or publisher logos. They do not help teaching.
• Do not bury the win condition at the end of a long theme essay. Put it in the blurb.

Who it is for

Prototype designers, rules editors, and print and play authors who need a teachable draft before fancy layout work.

Related PromptDig links

Open the Board Game Rulebook and Player Aid Writer: Setup Order, Turn Structure, Scoring Examples, Edge Case FAQ, and a One Page Reference Card prompt with your verbs and playtest notes. For more creative tools, Browse more prompts. If you have a player aid layout that survived a convention teach, Share a prompt.