Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Guide to board game design including mechanics taxonomy, theme integration, prototyping, playtesting methodology, balance iteration, rulebook writing, art direction, Kickstarter launch, and publisher pitching.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
438 lines · 2,889 words
Gather requirements. Ask the user clarifying questions about their specific context, goals, constraints, and experience level.
Analyze the situation. Review the information provided and identify key factors, challenges, and opportunities relevant to board game designer.
Guide to board game design including mechanics taxonomy, theme integration, prototyping, playtesting methodology, balance iteration, rulebook writing, art direction, Kickstarter launch, and publisher pitching.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Board Game Designer skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
What it covers
When to Use
Process
Questions to Ask First
Game Mechanics Taxonomy
Theme Integration
Prototyping
Playtesting Methodology
Balance Iteration
Rulebook Writing
Art Direction
Kickstarter Launch
Publisher Pitching
Safety and Inclusivity Considerations
Progression Path
Resources
Output Format
Example
Edge Cases
Develop the framework. Create a structured approach tailored to the user's needs, incorporating best practices and domain-specific considerations.
Deliver actionable output. Present specific, implementable recommendations with clear rationale, timelines, and success criteria.
Address edge cases. Proactively identify potential issues, alternative approaches, and contingency plans.
Use this skill when:
User needs guidance on board game designer
User asks about board game designer best practices or techniques
User wants a structured approach to board game designer
Do NOT use this skill when:
A more specialized skill exists for the specific subtopic
The request is outside the scope of board game designer
Before starting the design process:
What board games do you enjoy playing? What makes them fun for you?
Do you have a game idea already, or are you starting from scratch?
What is your design experience? (First game / Have designed casually / Published designer)
What is your goal? (Personal project / Publish through Kickstarter / Pitch to publishers)
What is your budget for prototyping and development? ($0-50 / $50-200 / $200-1,000 / $1,000+)
How much time can you commit to design and playtesting? (Weekends / Several hours a week / Full-time)
What player count and play time are you targeting?
Do you have a playtest group, or do you need to find one?
What type of game interests you? (Strategy, party, cooperative, competitive, narrative)
Are you comfortable with graphic design, or will you need help with visual production?
Action Selection / Action Points
Players choose from available actions each turn
May have limited action points to spend
Examples: Pandemic (action selection), Terraforming Mars (card-driven actions)
Worker Placement
Players place limited workers on shared action spaces
Once placed, that space is blocked from other players
Creates tension through scarcity
Examples: Agricola, Lords of Waterdeep, Viticulture
Deck Building
Players start with weak decks and buy/gain better cards
Core loop: Play cards > Buy cards > Shuffle > Draw > Repeat
Examples: Dominion (originator), Star Realms, Clank!
Area Control / Area Majority
Players compete for dominance in regions of the map
Scoring based on who has the most presence
Examples: El Grande, Root, Blood Rage
Engine Building
Players construct increasingly powerful combinations
Early actions enable bigger future turns
Satisfying exponential growth feeling
Examples: Wingspan, Terraforming Mars, Splendor
Drafting
Players select from shared pool or passing hand of options
Simultaneous decision-making reduces downtime
Examples: 7 Wonders, Azul, Sushi Go
Tile Placement
Players add tiles to a shared or personal map
Spatial puzzle element
Examples: Carcassonne, Cascadia, Isle of Cats
Auction / Bidding
Players bid resources for items, actions, or privileges
Tests valuation skills
Examples: Ra, Power Grid, The Estates
Push Your Luck
Players choose between taking current rewards or risking them for more
Generates excitement and tension
Examples: Quacks of Quedlinburg, Can't Stop, Incan Gold
Cooperative
All players work together against the game system
Win or lose as a team
Requires careful tuning of difficulty
Examples: Pandemic, Spirit Island, The Crew
Social Deduction
Hidden roles, players must identify who is on which team
Lying, deduction, and persuasion
Examples: Werewolf, The Resistance, Blood on the Clocktower
Roll and Write
Players roll dice and record results on personal sheets
Low component cost, high accessibility
Examples: Yahtzee, Welcome To, Cartographers
Most successful games combine 2-4 mechanics. The combination creates uniqueness:
Worker placement + engine building = Agricola
Deck building + dungeon crawl = Clank!
Area control + asymmetric powers = Root
Drafting + pattern building = Azul
Theme-first: Start with a setting or story, find mechanics that express it
Strength: Cohesive, immersive experience
Risk: Mechanics may feel forced to fit theme
Mechanics-first: Start with an interesting mechanism, apply theme later
Strength: Mechanically tight and balanced
Risk: Theme may feel "pasted on"
Best approach: Iterate between both. Let theme suggest mechanics and mechanics suggest theme.
Actions should feel like what the theme describes (in a farming game, planting should feel like investing in future harvest)
Resource names should be thematic (not just "red cubes" but "iron ore")
Scoring should reflect thematic success (winning conditions match the story)
Card abilities should make narrative sense
Player roles/powers should fit their character
Overdone themes: Zombies, generic fantasy, space trading (you need a unique angle)
Underserved themes: Many historical periods, professions, natural phenomena, non-Western settings
Theme affects audience: Family themes expand market, dark themes narrow it
Cultural sensitivity: Research thoroughly if using real cultures or historical events
Index cards for cards
Poker chips or coins for tokens
Printed grid or hand-drawn board
Dice, meeples, or cubes from other games
Write game text by hand or print on labels
Use card sleeves with playing cards as backing for durability
Google Slides/PowerPoint: Quick card and board layout
Canva: Free design tool, good for cards and boards
nanDECK: Specialized card design software (free, steep learning curve)
Component.studio: Browser-based game component design
Tabletop Simulator ($20): Digital playtesting platform
Tabletopia (free tier): Browser-based digital playtesting
BoardGameArena: If your game fits existing frameworks
Design cards in software (8.5x11 with 9 cards per sheet)
Print on cardstock or regular paper in card sleeves
Board: Print on multiple sheets and tape together
Laminate reusable components
Use blank dice with stickers for custom dice
V1 - Ugly prototype: Hand-written, functional only (first 5-10 playtests)
V2 - Clean prototype: Printed, readable, consistent formatting (playtesting with strangers)
V3 - Near-final prototype: Professional-looking, final art direction sample (publisher pitches or Kickstarter preview)
Production prototype: Final art, manufactured sample (pre-Kickstarter or publisher submission)
Solo playtesting (Designer plays all positions):
First 10+ sessions should be solo
Test if the core loop is fun
Find obvious broken combinations
Verify game ends in target time frame
Identify decision points that feel meaningful vs automatic
Friendly playtesting (Friends and family):
First exposure to other humans
Watch their faces, not the board (confusion, boredom, delight)
They will be too nice - look for what they DO, not what they SAY
Observe: Where do they hesitate? Where do they make mistakes?
10-20 sessions at this stage
Blind playtesting (Strangers play with only the rulebook):
The real test: Can people learn and play without you explaining?
Do NOT intervene when they get confused - note what confused them
Rules problems become immediately apparent
This stage reveals the truth about your game
5-10 sessions minimum
Development playtesting (Experienced gamers testing for balance):
Power gamers try to break the game
Test edge cases and dominant strategies
Competitive players find exploits you never imagined
Critical for balance tuning
Observation Protocol:
Note player facial expressions and body language
Track decision time per turn (long pauses = analysis paralysis or confusion)
Track game length
Note which parts generate excitement and which generate frustration
Do not explain or defend design choices during play
Post-Game Questions (Ask In This Order):
What was the most fun part?
What was the least fun part?
Was there any point where you were confused?
Did you feel like your decisions mattered?
Would you play again? Why or why not?
How did the game length feel?
Is there anything you would change?
Avoid asking: "Did you like it?" (too vague, people will just say yes)
Playtest
Collect feedback and observations
Identify the biggest problem
Change ONE thing to address it
Playtest again
Repeat (expect 50-200+ iterations for a publishable game)
Dominant strategy: One approach always wins (test by forcing different strategies)
Runaway leader: Winner snowballs advantage (add catch-up mechanics or diminishing returns)
Kingmaker: Losing player decides who wins (reduce player-targeted attacks)
Analysis paralysis: Too many options per turn (limit choices, add time pressure)
First/last player advantage: Turn order creates unfair edge (rotate start player, balance resources)
Dead turns: Some turns have no meaningful decisions (ensure every turn matters)
Cost curves: More powerful effects cost proportionally more
Opportunity cost: Choosing one path means giving up another
Diminishing returns: Concentrated strategies become less efficient
Variable setup: Randomize elements so no single strategy dominates every game
Point salad: Multiple paths to victory so players do not all compete for the same resources
Spreadsheet modeling: Calculate expected values for cards, actions, and strategies
Data tracking: Record scores, strategies, and win rates across many playtests
Cover: Game name, player count, age range, play time
Component list: Everything in the box with images
Game overview: 2-3 sentence description of what players do and how they win
Setup: Step-by-step with diagram showing table layout
Turn structure: What happens on each turn, in order
Actions available: Detailed description of each action
End game conditions: When and how the game ends
Scoring: How to calculate final score
Glossary/reference: Key terms and symbols
Quick reference card: Separate player aid with turn summary
Use consistent terminology throughout (if you call it a "region" on page 2, do not call it an "area" on page 5)
Numbered steps for procedures
Bold key terms on first use
Include examples for complex rules
Use diagrams and illustrations liberally
Test the rulebook with blind playtesters (the true test)
Read other published rulebooks for formatting inspiration
Have someone who has never played read it and explain the game back to you
The rulebook is a teaching tool, not a legal document - prioritize clarity
Illustrator: Creates game art (box art, card illustrations, character art)
Graphic designer: Creates layout, iconography, card templates, board design, UX
Note: These are different skills. Do not assume one person can do both.
BoardGameGeek artist forums
DeviantArt and ArtStation portfolios
Instagram (search game art hashtags)
Game design communities (Facebook groups, Discord servers)
Conventions (networking at Gen Con, Essen, PAX Unplugged)
Card illustration: $50-300+ per unique card image
Game board: $500-3,000+
Box art: $500-2,000+
Graphic design (full game): $2,000-10,000+
Icon design: $20-100 per icon
Total art budget for a card game: $3,000-15,000
Total art budget for a board game: $10,000-50,000+
Provide clear art briefs (description, mood, reference images, dimensions, file format)
Agree on scope, timeline, payment schedule, and rights before starting
Milestone payments (30% upfront, 30% at sketch approval, 40% at final delivery)
Get written contract specifying rights transfer or licensing
Allow creative freedom within your brief (they are the expert)
Build an email list (landing page with signup, at least 1,000 emails for a strong launch)
Establish social media presence (Instagram, BGG, Facebook groups)
Send review copies to content creators (3-6 months before launch)
Create promotional video (show gameplay, tell the story)
Get manufacturing quotes (Panda Game Manufacturing, LongPack Games, WinGo Games)
Set realistic funding goal (enough to cover manufacturing + fulfillment for minimum viable order)
Pledge levels: Keep simple (1-2 core tiers, maybe a deluxe tier)
Stretch goals: Plan in advance, pre-negotiated with manufacturer
Campaign length: 15-30 days (shorter creates urgency)
Funding goal: Cover manufacturing at minimum order + fulfillment + Kickstarter fees (10%)
Pricing: Research comparable games, include shipping estimate
Use a fulfillment partner (Quartermaster Logistics, Fulfillrite, Shipnaked)
International shipping is expensive and complex - price accurately
Customs and VAT for EU shipments
Budget 6-12 months from campaign end to delivery
Communicate delays transparently (backers are forgiving if you are honest)
Underestimating manufacturing and shipping costs
Setting funding goal too high or too low
No audience built before launch
Poor video quality
Unclear value proposition (why should I back THIS game?)
Overpromising stretch goals
Not budgeting for Kickstarter and payment processing fees (8-10% total)
Research publishers who make games similar to yours in complexity, theme, and player count
Attend conventions with publisher speed-dating events
Check publisher websites for submission guidelines
Many publishers accept unsolicited submissions
Sell sheet (1 page): Game name, tagline, player count, time, age range, elevator pitch (2-3 sentences), key features, photos of prototype, your contact info
Rulebook: Clean, complete, tested
Prototype: Playable, functional (does not need final art)
Video pitch (optional): 2-3 minute demonstration
5-minute pitch: Explain the game in 2 minutes, play a demo turn in 3 minutes
Lead with the hook: What makes this game unique and exciting?
Know your comparable games ("It is like Wingspan meets Ticket to Ride")
Be ready to leave the prototype for evaluation
Follow up within 1 week with thank you and digital materials
Royalty: 4-8% of wholesale price (not MSRP)
Advance: Sometimes $1,000-5,000 (paid against future royalties)
Publisher handles: Manufacturing, art, marketing, distribution, fulfillment
Designer provides: Final game design, rulebook, playtesting support
Contract length: 3-7 years or until out of print
Always consult a lawyer before signing
Consider content warnings if your game includes mature themes
Use the X-Card or similar safety tools for social deduction or role-playing games
Ensure representation in art and characters is thoughtful and respectful
Test accessibility: Color-blind friendly design (use symbols AND colors), readable font sizes, component sizes
Price point affects accessibility - consider offering print-and-play versions
Phase 1: Play 20+ different games, analyze what makes them work, design first prototype
Phase 2: Playtest 20+ times, iterate on core mechanics, find playtest group
Phase 3: Blind playtest, write complete rulebook, polish prototype
Phase 4: Decide path: Kickstarter or publisher pitch, prepare materials accordingly
Phase 5: Launch or pitch, navigate production/publication process
Phase 6: Published game, gather player feedback, start next design
BoardGameGeek (boardgamegeek.com): The central hub for board game community
The Game Crafter (thegamecrafter.com): Print-on-demand game manufacturing
Books: "The Game Inventor's Guidebook" by Brian Tinsman
Books: "Building Blocks of Tabletop Game Design" (academic reference)
Podcasts: Board Game Design Lab, Ludology, The Game Design Round Table
Conventions: Gen Con, Essen Spiel, PAX Unplugged, Protospiel events
Communities: r/tabletopgamedesign, Facebook Game Design groups, Game Design Discord servers
Deliver the response as a structured document with clear headings and actionable content. Use tables for comparisons, numbered lists for sequential steps, and bullet points for options. Include specific examples where applicable.
[Board Game Designer deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timelineInput: "Help me with board game designer for a mid-size project."
Output: A complete board game designer framework tailored to the specific context, with actionable steps, relevant considerations, and measurable outcomes.
Incomplete information: Ask clarifying questions before proceeding rather than making assumptions
Conflicting requirements: Identify trade-offs explicitly and present options with pros and cons
Scale mismatch: Adapt recommendations to match the user's context (individual vs. team vs. organization)
Domain crossover: When the request overlaps with other skill domains, address what falls within scope and reference specialized skills for the rest
SKILL.md
438 lines · 2,889 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Board Game Designer bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for