Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Comprehensive puzzle design covering puzzle types (logic, mechanical, word, mathematical, spatial), difficulty calibration, hint systems, crossword construction, escape room design, physical and digital puzzle design, testing methodologies, and creating satisfying "aha" moments.
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
534 lines · 3,047 words
Use this skill when:
The user wants to design puzzles for games, escape rooms, puzzle books, or team-building events
The user needs help with difficulty calibration, hint system design, or the satisfaction curve framework
The user is building an escape room and needs puzzle flow design (linear, parallel, or hybrid)
Comprehensive puzzle design covering puzzle types (logic, mechanical, word, mathematical, spatial), difficulty calibration, hint systems, crossword construction, escape room design, physical and digital puzzle design, testing methodologies, and creating satisfying "aha" moments.
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 Game Puzzle 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
Puzzle Design Fundamentals
Puzzle Types
Difficulty Calibration
Hint Systems
Escape Room Design
Digital Puzzle Design
Testing Methodologies
Practice Exercises
Output Format
Example
Edge Cases
The user wants guidance on specific puzzle types (logic, word, mathematical, spatial, or mechanical)
The user needs testing methodologies for puzzle solvability, fairness, and accessibility
Do NOT use this skill when:
The user is designing overall game mechanics or systems beyond puzzles (use video-game-designer instead)
The user needs help with crossword publishing or word game apps as a business (use relevant business skill)
The user wants to design educational games where puzzles serve learning objectives (use educational-game-designer instead)
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 game puzzle designer.
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 game puzzle designer
User asks about game puzzle designer best practices or techniques
User wants a structured approach to game puzzle designer
Do NOT use this skill when:
A more specialized skill exists for the specific subtopic
The request is outside the scope of game puzzle designer
Before designing any puzzle, clarify:
What type of puzzle are you creating? (Logic, word, mathematical, spatial, mechanical, meta, narrative)
What is the context? (Escape room, video game, newspaper/magazine, puzzle book, educational, team-building event)
Who is the target audience? (Casual solvers, puzzle enthusiasts, children, professionals, mixed groups)
What is the difficulty target? (Easy/accessible, medium, hard/expert)
Is this a standalone puzzle or part of a sequence? (Single challenge vs. puzzle chain)
What is the time frame? (30-second riddle, 10-minute puzzle, 60-minute escape room)
Are there physical components? (Paper, props, locks, digital interface)
What is the "aha" moment? (What should the solver discover or realize)
EVERY GREAT PUZZLE HAS:
1. CLEAR GOAL: The solver knows what they're trying to achieve
"Find the word" / "Open the lock" / "Reach the exit"
Ambiguous goals create frustration, not challenge.
2. ELEGANT CONSTRAINTS: Rules that create interesting problems
"You can only move forward and right"
Good constraints feel natural, not arbitrary.
3. AN "AHA" MOMENT: The shift in understanding that leads to solution
The moment you see the trick, the pattern, the hidden connection.
This is the REWARD. Everything in the puzzle should build toward it.
4. FAIR DIFFICULTY: Hard because it's clever, not because it's unfair
All information needed to solve is available to the solver.
No required knowledge that a reasonable solver wouldn't have.
No reliance on obscure trivia or cultural specifics (unless that's the genre).
5. VERIFIABLE SOLUTION: The solver knows when they've solved it
The answer is clearly right -- no ambiguity.
The mechanism of correctness is satisfying.
THE SATISFACTION CURVE:
Confusion -> Investigation -> Insight -> Verification -> Satisfaction
| | | | |
"What is "Hmm, maybe "OH! I "Yes, that "That was
this?" if I..." see it!" works!" brilliant!"PHASE 1: ORIENTATION (Understanding the puzzle)
- What am I looking at?
- What are the rules/constraints?
- What information is given?
- What is the goal?
DESIGN FOR THIS PHASE:
- Make the presentation clear and unambiguous
- Provide all necessary information visually
- Let the solver understand the GOAL within seconds
- The challenge should be in the SOLVING, not in understanding
what to solve
PHASE 2: EXPLORATION (Working toward solution)
- Testing hypotheses
- Recognizing patterns
- Eliminating possibilities
- Building toward insight
DESIGN FOR THIS PHASE:
- Provide productive avenues of exploration
- Reward partial progress (not just final solution)
- Include red herrings sparingly and fairly
- Build a logical pathway from start to solution
PHASE 3: RESOLUTION (The "aha" and verification)
- The key insight clicks
- The solution becomes clear
- Verification confirms correctness
- Satisfaction from the achievement
DESIGN FOR THIS PHASE:
- The "aha" should feel earned, not lucky
- Verification should be immediate and clear
- The solution should feel elegant ("Of course!")
- Looking back, the path should seem inevitableTYPES:
Grid-based deduction (Einstein puzzles, logic grids)
Constraint satisfaction (Sudoku, Kakuro, KenKen)
Sequence patterns (what comes next)
Truth-teller/liar puzzles
River-crossing problems
Knights and knaves
DESIGN PRINCIPLES:
- Every clue must be necessary (remove one, and it's unsolvable)
- No clue should be redundant (remove one, and difficulty drops)
- The solving path should have a LOGICAL ORDER
(there should be a deducible first step)
- Dead ends should be detectable without excessive backtracking
CREATING A LOGIC GRID PUZZLE:
1. Start with the solution (e.g., 5 people, 5 houses, 5 pets)
2. Write clues that uniquely determine the solution
3. Order clues so there's a solvable chain of deductions
4. Test: remove each clue one at a time -- is it still solvable?
If yes, that clue is redundant. Remove it.
5. Test: can a fresh solver find the solution? (Blind test)
DIFFICULTY LEVERS:
Easy: Clues directly state relationships ("The dog owner lives in house 3")
Medium: Clues require one deduction ("The cat owner lives next to the blue house")
Hard: Clues require chain deductions ("If the dog owner isn't in house 1 or 5...")TYPES:
Crosswords, word searches, anagrams, cryptograms
Acrostics, word ladders, rebuses
Cipher and code puzzles
CROSSWORD CONSTRUCTION:
1. Start with the grid pattern (symmetric, typically)
2. Fill the grid with interlocking words (use crossword
construction software: Crossfire, Phil, or web-based tools)
3. Write clues AFTER the grid is complete
4. Clue types:
- Straight definition: "Capital of France (5)" -> PARIS
- Cryptic: wordplay that encodes the answer
"Flower arrangement I'm in (5)" -> TULIP (hidden: "...I'm in TULIPse...")
- Thematic: clues connect to a theme
5. Test with solvers at your target difficulty level
CIPHER DESIGN:
Easy: Simple substitution (A=1, B=2 or Caesar cipher)
Medium: Keyword cipher, pigpen, Morse
Hard: Multi-step encoding, polyalphabetic ciphers
Key principle: The solver must be able to DISCOVER the cipher
method, not just apply a known one.
WORD PUZZLE DIFFICULTY:
Easy: Common words, direct clues, small grids
Medium: Less common words, wordplay, misdirection
Hard: Obscure vocabulary, complex wordplay, large interconnected gridsTYPES:
Number sequences, magic squares, arithmetic puzzles
Probability puzzles, optimization problems
Mathematical paradoxes, geometry challenges
DESIGN PRINCIPLES:
- The math should serve the puzzle, not the other way around
- Arithmetic should be manageable without a calculator
- The insight should be conceptual, not computational
- Present mathematical ideas in concrete, visual ways
EXAMPLES OF WELL-DESIGNED MATH PUZZLES:
"Three switches control three light bulbs in another room.
You can flip switches as much as you want, but you can only
enter the room once. How do you determine which switch
controls which bulb?"
(Solution: Turn one on for a while (heat), turn it off,
turn another on. Check: on = switch 2, off+warm = switch 1,
off+cold = switch 3)
The insight is lateral thinking applied to math/physics,
not calculation.TYPES:
Mazes, tangrams, pentominoes, jigsaw puzzles
3D assembly, folding puzzles, perspective puzzles
Hidden object, spot-the-difference
DESIGN PRINCIPLES:
- Spatial puzzles should be solvable through visual reasoning
- Provide clear visual feedback on progress
- The "aha" is often about seeing a pattern from a new angle
- Physical manipulation (real or virtual) adds engagement
MAZE DESIGN:
- Start by drawing the solution path
- Add branches that dead-end at varying distances from the solution
- Short dead-ends = easy (quick to recognize)
- Long dead-ends = hard (investment before failure)
- Multiple routes with one optimal = interesting choices
- Incorporate mechanics: one-way doors, keys, teleportersTHE DIFFICULTY CALIBRATION FRAMEWORK:
DIFFICULTY = f(Number of Steps, Insight Required, Knowledge Required,
Red Herrings, Time Pressure)
ADJUSTING DIFFICULTY:
EASIER: HARDER:
Fewer steps to solution More steps to solution
Direct clues Indirect clues
Common knowledge Specialized knowledge
No red herrings Plausible red herrings
Generous time Time pressure
Visual aids Abstract presentation
Partial progress visible All-or-nothing solution
Sequential unlocks Parallel reasoning required
THE GOLDILOCKS ZONE:
Too easy: Solver feels unchallenged and bored
Too hard: Solver feels frustrated and stuck
Just right: Solver feels challenged but capable
AIM FOR: 70-80% of your target audience can solve it
within the expected time frame.
TESTING CALIBRATION:
Test with 5+ people at your target level.
Track: Time to solve, where they got stuck, did they need hints.
If everyone solves it instantly: too easy.
If nobody solves it: too hard.
If most solve it with effort: just right.
SKILL FLOOR vs. SKILL CEILING:
Skill floor: The minimum ability needed to engage with the puzzle
Skill ceiling: The maximum skill that can be applied
For accessible puzzles: low floor, moderate ceiling
For expert puzzles: moderate floor, high ceilingPROGRESSIVE HINT DESIGN:
LEVEL 1 - NUDGE (Direction without specifics):
"Look more carefully at the colors."
"Think about what these numbers have in common."
Purpose: Redirects attention without giving away the insight.
LEVEL 2 - GUIDANCE (Specific area to investigate):
"The colors correspond to something else in the room."
"These numbers are all part of a well-known sequence."
Purpose: Narrows the search space significantly.
LEVEL 3 - PARTIAL REVELATION (Part of the solution):
"The colors match the flags on the map."
"It's the Fibonacci sequence."
Purpose: Gives enough to proceed even if stuck.
LEVEL 4 - FULL SOLUTION (For those truly stuck):
"Red=France, Blue=Greece, Green=Brazil. The capital letters spell..."
Purpose: Prevents permanent stuck state. Nobody should be locked out.
HINT DELIVERY METHODS:
- Timed: Hints appear after set intervals
- Requested: Player explicitly asks for hints (preserves agency)
- Environmental: Additional clues hidden in the environment for observant solvers
- Social: Other players/team members provide hints through collaboration
- Contextual: Hints appear when specific wrong actions are attempted
HINT DESIGN PRINCIPLES:
- Hints should respect the solver's intelligence
- Early hints should preserve the "aha" moment
- Each hint should give EXACTLY enough to make progress
- The hint system should not make players feel bad for using it
- Optional hints are better than forced tutorialsTHE ESCAPE ROOM DESIGN PROCESS:
STEP 1: THEME AND NARRATIVE
Choose a compelling setting that justifies the puzzle structure:
- Why are the players in this room?
- Why do they need to escape/complete the objective?
- What is the story arc within the 60 minutes?
Strong themes: Mystery/detective, heist, archaeological discovery,
science lab, haunted location, spy mission, time travel
STEP 2: PUZZLE FLOW DESIGN
Map the puzzle structure:
LINEAR FLOW:
Puzzle A -> Puzzle B -> Puzzle C -> Final Lock
Pros: Clear progression, easy to understand
Cons: Bottleneck if one puzzle stumps the group
OPEN/PARALLEL FLOW:
Puzzle A -----\
Puzzle B -------> Combination -> Final Lock
Puzzle C -----/
Pros: Multiple people can work simultaneously
Cons: Can feel disconnected
HYBRID (RECOMMENDED):
Puzzle A -> Puzzle B -\
-> Meta Puzzle -> Final Lock
Puzzle C -> Puzzle D -/
Best of both: parallel paths that converge
STEP 3: PUZZLE DESIGN (For each puzzle)
- What type of puzzle is this? (Observation, logic, physical, knowledge)
- What is the input? (What does the player interact with)
- What is the "aha"? (The insight that solves it)
- What is the output? (A code, a key, a clue for the next puzzle)
- How does it connect to the theme?
STEP 4: PHYSICAL DESIGN
Props, locks, hidden compartments, lighting, sound
Technology: magnetic locks, RFID, Arduino-based triggers
Safety: emergency exits always accessible, no actual danger
STEP 5: GAME MASTER PREPARATION
- Monitoring system (cameras or one-way glass)
- Hint delivery system (walkie-talkie, screen, audio)
- Hint script for each puzzle (tiered hints)
- Reset checklist (every prop back in position)
- Timing and pacing guidelines
ESCAPE ROOM DESIGN RULES:
1. No puzzle should require outside knowledge beyond common sense
2. Everything in the room should be either a puzzle, a clue,
a red herring, or clearly decoration (and minimize red herrings)
3. Players should NEVER have to force, break, or damage anything
4. The difficulty curve should ramp up, then the final puzzle
should feel like a satisfying culmination
5. 60 minutes is standard. Aim for ~60% success rate for your
target audience. Lower than 40% = too hard. Higher than 80% = too easy
6. Groups of 2-3 should be able to complete. Don't require 6+ people.DIGITAL-SPECIFIC CONSIDERATIONS:
ADVANTAGES OF DIGITAL:
- State tracking (the game remembers what you've done)
- Dynamic difficulty adjustment
- Procedural generation for replayability
- Immediate feedback and verification
- Undo/redo without physical reset
- Animation and sound enhance the "aha" moment
DIGITAL PUZZLE TYPES:
- Sokoban-style (push blocks to targets)
- Portal/perspective puzzles
- Programming/logic gate puzzles
- Physics-based puzzles
- Pattern matching and sequence puzzles
- Narrative puzzles (adventure game style)
INTERFACE DESIGN FOR DIGITAL PUZZLES:
- Controls should be immediately intuitive
- The puzzle, not the interface, should be the challenge
- Show the goal state clearly (what are you trying to achieve)
- Provide undo for trial-and-error puzzles
- Animate state changes to make the system readable
- Sound design should reinforce correct/incorrect actions
DIFFICULTY PROGRESSION IN DIGITAL:
- Teach one concept per level
- Each level should build on the previous
- Introduce, reinforce, combine, test
- Allow players to skip occasionally (prevents permanent stuck)
- The last 20% of puzzles can be much harder (for completionists)PUZZLE TESTING PROTOCOL:
1. SOLVABILITY TEST (Self + designer peers)
- Is there exactly one solution? (Unless multiple are intended)
- Is the solution achievable with the given information?
- Are there any logical gaps in the solving path?
- Can you solve it without relying on assumptions you made as designer?
2. DIFFICULTY TEST (Target audience)
- Time how long solvers take
- Note where they get stuck
- Note what strategies they try
- Don't help -- observe silently
- Track: solved without hints, with hint 1, with hint 2, unsolved
3. FAIRNESS TEST (Fresh eyes)
- Does the solver feel the solution is fair when revealed?
- "Of course!" reaction = good design
- "That's arbitrary" reaction = bad design
- "I would never have thought of that" = possibly too hard
OR possibly brilliant (context matters)
4. RED HERRING TEST
- Are red herrings distinguishable from real clues with effort?
- Do red herrings waste excessive time?
- Would removing the red herring improve or reduce the experience?
5. ACCESSIBILITY TEST
- Can color-blind players solve visual puzzles?
- Are physical puzzles accessible to those with limited mobility?
- Is required knowledge universal enough for your audience?
- Are language requirements clear and unambiguous?
POST-TEST QUESTIONS:
"Walk me through how you solved it."
"Where did you feel stuck?"
"Was the solution satisfying?"
"What would you change?"
"Rate the difficulty 1-10."Design a puzzle backwards: start with the "aha" moment you want the solver to experience, then build the puzzle structure around delivering that moment.
Take a single puzzle concept and create three versions: easy, medium, and hard. The core mechanism should be the same; only the difficulty parameters should change.
Take a puzzle you've designed. Write a 4-level progressive hint system for it. Test: Can someone stuck at any point use the minimum hint level to make progress?
Take a physical puzzle concept and redesign it for digital. Or take a digital puzzle and redesign it for physical/escape room. What changes? What stays the same?
Watch 5 people solve the same puzzle. Don't interact. Note where each person gets stuck. The patterns reveal design problems; the outliers reveal interesting alternative approaches.
Choose a single puzzle mechanic (e.g., mirror reflection, gravity manipulation, word substitution). Design 5 puzzles of increasing difficulty using only that mechanic. Each should feel fresh despite using the same core idea.
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.
[Game Puzzle Designer deliverable]
1. Context and objectives
2. Analysis or framework
3. Specific recommendations with rationale
4. Action items with timelineInput: "Help me with game puzzle designer for a mid-size project."
Output: A complete game puzzle 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
534 lines · 3,047 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
Game Puzzle Designer bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for