Board Game Designer Skill
Everyone has a board game idea; almost nobody has a prototype, because the gap
between theme ("it's about deep-sea heists!") and game (what do I DO on my
turn?) is where ideas stall. This skill forces the designer's questions in the
order working designers ask them — loop before theme-decoration, tension before
content, cardboard before art — and ships the user toward a playtest this week
with ugly components and honest kill criteria.
What This Skill Produces
- A design one-pager: hook, core loop, tension source, end condition,
player count/length targets
- A prototype spec buildable tonight: index cards, dice, cubes — counts and
what's written on each; zero art
- Balance starting-points: first-pass numbers with the reasoning, labelled
as guesses to tune, never as solved math
- A 3-session playtest protocol with what to watch, what to ask, and kill
criteria — the honest thresholds for pivot-or-persevere
Required Inputs
Ask for (if not already provided):
- The idea as they'd pitch it to a friend, plus what inspired it
- The feeling the best turn should produce (clever? tense? gleeful betrayal?)
- Target: players, minutes, audience (family? hobbyists? their own group?)
- If mid-design: what's working, and where it drags
Process
- Find the loop. One sentence: "On your turn you [verb] to get [resource]
to [convert] toward [goal]." No loop sentence, no game yet — iterate here
before anything else.
- Name the tension. Every game that works has a recurring painful choice
(this OR that, now OR better-later, me OR blocking-you). Identify the one
this design offers; if every option is good, there's no game in the loop yet.
- Steal structure honestly. Name 2–3 existing games whose mechanisms
neighbour this design and what each does with them — designers study prior
art; note where this design genuinely differs (its one new twist) and where
it shouldn't bother differing.
- Spec the ugliest playable version. Index cards and cubes, tonight. Every
component count written down. The rule: nothing gets art until it survives
five plays.
- First-pass the numbers. Costs, income, end-trigger pacing — pick values
with stated reasoning ("end triggers around turn 8 so the engine peaks once"),
marked TUNE. Balance comes from plays, not spreadsheets; the spreadsheet just
picks where to start.
- Protocol the playtests. Session 1 (solo, all seats): does the loop
function? Session 2 (friendly table): where does attention die? Watch for the
tells — checking phones, analysis stalls, kingmaking, runaway leader. Session
3 (someone who owes you nothing): would they play again unprompted? Kill
criteria stated up front: if the same drag survives two fixes, the mechanism
goes, however loved.
Output Format
## Design one-pager
[Hook · loop sentence · the tension · end condition · count/length targets]
## Neighbouring designs
[2-3 games, the mechanism borrowed/varied, the one honest twist here]
## Prototype spec (build tonight)
[Component list with counts and card text · setup · turn structure v0.1]
## Numbers v0.1 (all marked TUNE)
[Table of starting values + one line of reasoning each]
## Playtest protocol
[3 sessions: goal, what to watch, questions to ask AFTER not during]
Kill criteria: [the honest thresholds]
Quality Checks
Anti-Patterns
Example Trigger Phrases
- "I have a board game idea."
- "Design a game about X."
- "My game drags in the midgame."
- "How do I playtest this?"
1---2name: board-game-designer3description: "Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan."4disable-model-invocation: true # skill-optimizer5metadata:6 source: https://skillmd.com/skills/slipcast-dev/board-game-designer7---89# Board Game Designer Skill1011Everyone has a board game idea; almost nobody has a *prototype*, because the gap12between theme ("it's about deep-sea heists!") and game (what do I DO on my13turn?) is where ideas stall. This skill forces the designer's questions in the14order working designers ask them — loop before theme-decoration, tension before15content, cardboard before art — and ships the user toward a playtest this week16with ugly components and honest kill criteria.1718## What This Skill Produces1920- A **design one-pager**: hook, core loop, tension source, end condition,21 player count/length targets22- A **prototype spec** buildable tonight: index cards, dice, cubes — counts and23 what's written on each; zero art24- **Balance starting-points**: first-pass numbers with the reasoning, labelled25 as guesses to tune, never as solved math26- A **3-session playtest protocol** with what to watch, what to ask, and kill27 criteria — the honest thresholds for pivot-or-persevere2829## Required Inputs3031Ask for (if not already provided):32- The idea as they'd pitch it to a friend, plus what inspired it33- The feeling the best turn should produce (clever? tense? gleeful betrayal?)34- Target: players, minutes, audience (family? hobbyists? their own group?)35- If mid-design: what's working, and where it drags3637## Process38391. **Find the loop.** One sentence: "On your turn you [verb] to get [resource]40 to [convert] toward [goal]." No loop sentence, no game yet — iterate here41 before anything else.422. **Name the tension.** Every game that works has a recurring painful choice43 (this OR that, now OR better-later, me OR blocking-you). Identify the one44 this design offers; if every option is good, there's no game in the loop yet.453. **Steal structure honestly.** Name 2–3 existing games whose *mechanisms*46 neighbour this design and what each does with them — designers study prior47 art; note where this design genuinely differs (its one new twist) and where48 it shouldn't bother differing.494. **Spec the ugliest playable version.** Index cards and cubes, tonight. Every50 component count written down. The rule: nothing gets art until it survives51 five plays.525. **First-pass the numbers.** Costs, income, end-trigger pacing — pick values53 with stated reasoning ("end triggers around turn 8 so the engine peaks once"),54 marked TUNE. Balance comes from plays, not spreadsheets; the spreadsheet just55 picks where to start.566. **Protocol the playtests.** Session 1 (solo, all seats): does the loop57 function? Session 2 (friendly table): where does attention die? Watch for the58 tells — checking phones, analysis stalls, kingmaking, runaway leader. Session59 3 (someone who owes you nothing): would they play again *unprompted*? Kill60 criteria stated up front: if the same drag survives two fixes, the mechanism61 goes, however loved.6263## Output Format6465```66## Design one-pager67[Hook · loop sentence · the tension · end condition · count/length targets]6869## Neighbouring designs70[2-3 games, the mechanism borrowed/varied, the one honest twist here]7172## Prototype spec (build tonight)73[Component list with counts and card text · setup · turn structure v0.1]7475## Numbers v0.1 (all marked TUNE)76[Table of starting values + one line of reasoning each]7778## Playtest protocol79[3 sessions: goal, what to watch, questions to ask AFTER not during]80Kill criteria: [the honest thresholds]81```8283## Quality Checks8485- [ ] The loop fits in one sentence and contains a decision, not just an action86- [ ] The tension is a *recurring* choice, named concretely87- [ ] Prototype is buildable from household stationery in an evening — if it88 needs printing services, it's overdesigned for v0.189- [ ] Every number carries reasoning and a TUNE flag — no false precision90- [ ] Kill criteria exist and are specific enough to actually trigger9192## Anti-Patterns9394- [ ] Do not start with theme, art, or a Kickstarter plan — loop, tension,95 cardboard, in that order96- [ ] Do not claim the idea is original without the prior-art pass, and do not97 copy a game wholesale with the theme swapped — name the twist98- [ ] Do not present first-pass numbers as balanced — playtesting owns balance99- [ ] Do not let the designer explain rules during playtests — confusion IS the100 data101- [ ] Do not promise market outcomes ("this would sell!") — the promise is a102 playtest by Friday103104## Example Trigger Phrases105106- "I have a board game idea."107- "Design a game about X."108- "My game drags in the midgame."109- "How do I playtest this?"