t1k:designer:puzzle:core
| Field | Value |
|---|---|
| Module | puzzle |
| Version | 1.8.2 |
| Effort | medium |
| Tools | — |
Keywords: design, mechanics, puzzle, puzzle design
How to invoke
Section titled “How to invoke”/t1k:designer:puzzle:corePuzzle Game Design
Section titled “Puzzle Game Design”When This Skill Triggers
Section titled “When This Skill Triggers”- Designing match-3, block-drop, grid, logic, or spatial puzzle mechanics
- Balancing match mechanics, combo multipliers, or cascade scoring
- Creating puzzle-RPG hybrids (puzzle combat → RPG loot/stats)
- Designing polyomino/Tetris bag randomizer, rotation systems, scoring
- Tuning F2P economy (lives, boosters, soft/hard currency, conversion)
- Generating solvable boards, difficulty curves, or level pacing arcs
Puzzle Game Taxonomy
Section titled “Puzzle Game Taxonomy”| Type | Core Loop | Key Mechanic |
|---|---|---|
| Match-3 | Swap tiles to match ≥3 | Cascade chains, special pieces |
| Block-drop (Tetris) | Piece falls, player rotates/places | Line clear, T-spins |
| Polyomino inventory | Place shaped pieces in grid | Spatial fit, adjacency bonus |
| Logic/sokoban | Push/pull to reach goal | State-space search |
| Puzzle-RPG hybrid | Solve puzzle → deal damage | Mana gen, element matching |
Core Design Principles
Section titled “Core Design Principles”Insight vs Execution — Great puzzles reward insight (the “aha moment”), not twitch execution. Players should feel clever, not punished.
Player Contract — State the rules completely and visibly before the first challenge. Never introduce a new rule mid-puzzle without a tutorial moment.
Difficulty Saw, Not Monotonic Curve — Group levels into per-mechanic cycles: difficulty DIPS when a new mechanic is introduced (cognitive room to learn) and RISES through mastery, then dips again with the next mechanic. The aggregate trend climbs across cycles, but every cycle gives the player a fresh “I learned this” moment. Combine mechanics only after each is mastered independently. → See references/difficulty-saw-framework.md.
Solvability Guarantee — Every procedurally generated board must be verifiably solvable before display. Never show an impossible state.
Anti-Patterns
Section titled “Anti-Patterns”| # | Anti-Pattern | Problem | Fix |
|---|---|---|---|
| 1 | Artificial difficulty wall | RNG makes level unsolvable regardless of skill | Guarantee minimum matches on board gen |
| 2 | RNG frustration (bad luck spiral) | Player loses streak due to bad drops | Add pity: guaranteed useful piece/match after N bad draws |
| 3 | Unclear rules | Player doesn’t know why they failed | Visual preview of effects before commit |
| 4 | Runaway cascade | Long chain one-shots level, no skill | Cap cascade multiplier or add chain-break mechanic |
| 5 | Pay-to-win boosters | Boosters trivialize hard levels | Balance hard levels to be winnable without boosters |
| 6 | Tutorial overload | Too many rules at once | One mechanic per tutorial screen, max 3 screens |
Quick Reference → Reference Files
Section titled “Quick Reference → Reference Files”→ See references/match-3-design.md — board gen, combos, special pieces, move economy, star ratings
→ See references/polyomino-tetris-design.md — bag randomizer, SRS rotation, scoring, speed curves
→ See references/puzzle-rpg-hybrid.md — puzzle→stats mapping, mana gen formula, element matching
→ See references/puzzle-difficulty-curve.md — difficulty measurement, tutorial phases, pacing model
→ See references/difficulty-saw-framework.md — Strachan’s saw model, per-mechanic cycles, empirical playtest methods, audience targeting
→ See references/puzzle-f2p-economy.md — lives system, dual currency, boosters, conversion targets
Cross-References
Section titled “Cross-References”rpg-game-design— stat formulas, item balance, progression curves for puzzle-RPG hybrid statsgame-balance-tools— spreadsheet formulas and validation for difficulty spike detectiongame-design-document— GDD structure for documenting puzzle mechanics and economy- engine inventory skills (auto-activated via registry) — polyomino grid placement, adjacency/set bonuses
Reference Files
Section titled “Reference Files”| File | Coverage |
|---|---|
references/match-3-design.md | Board gen, combo/chain scoring, special pieces, move economy, star ratings, difficulty curve |
references/polyomino-tetris-design.md | 7-bag randomizer, SRS wall kicks, scoring, speed curves, back-to-back bonus, inventory integration |
references/puzzle-rpg-hybrid.md | Puzzle→RPG stat mapping, mana gen formula, element matching, equipment modifiers, progression loop |
references/puzzle-difficulty-curve.md | Difficulty measurement, tutorial design, pacing model, hint tiers, procedural vs hand-crafted |
references/difficulty-saw-framework.md | Strachan’s “Difficulty Saw” — per-mechanic cycles, Teaching/Main/Finale level structure, DOs/DON’Ts, empirical playtest methods (death heatmaps, completion drop-off, friend testing), adrenaline/contrast pacing, audience targeting |
references/puzzle-f2p-economy.md | Lives system, dual currency, booster design, paywall timing, conversion targets, daily rewards |
Gotchas
Section titled “Gotchas”- Difficulty curves diverge between expert and casual players — what looks like an even ramp on paper is a cliff for one cohort. Validate via playtest, not spreadsheet.
- Match-3 boards must be solvable from any state — a single unsolvable shuffle wipes player trust; bake a solver-validator into level export.
- One puzzle mechanic per level is a heuristic, not a rule — combination levels can shine if the mechanics are individually mastered first.