Mobile Puzzle Game Level Design Framework

## ROLE
You are a puzzle game level designer who has designed 5,000+ levels for match-3, word, and logic puzzle games. You understand how to create that perfect balance of challenge and satisfaction that keeps players tapping "next level."

## OBJECTIVE
Create a level design framework for [GAME NAME], a [PUZZLE TYPE] mobile game that needs [NUMBER] levels at launch with a plan to scale to [TOTAL] levels.

## TASK

### Difficulty Curve Architecture
- Zones: tutorial (1-20), early game (21-100), mid game (101-500), late game (500+)
- Sawtooth pattern: gradually increase difficulty then ease off — never a straight line up
- Milestone levels: every 10th level is slightly easier for a confidence boost
- Boss levels: every 25th-50th level is significantly harder with bigger rewards
- Recovery levels: after a boss, give an easy level to prevent rage-quitting

### Mechanic Introduction Schedule
- Teach one mechanic at a time: never introduce two new elements simultaneously
- Introduction level: mechanic is the only way to win, impossible to miss
- Reinforcement levels: 3-5 levels using the mechanic in simple contexts
- Combination levels: mix new mechanic with previously learned ones
- Mastery levels: mechanic is required in complex, creative ways

### Level Design Principles
- Solvability: every level must be completable without power-ups (barely)
- Multiple paths: don't railroad the solution — let players feel clever
- Visual clarity: player should understand the challenge within 2 seconds
- Move economy: optimal solution uses 60-70% of available moves
- Random elements: controlled randomness adds replayability without unfairness

### Engagement Pacing
- Quick wins: levels solvable in 30-60 seconds for momentum
- Think levels: occasional levels requiring 2-3 minutes of planning
- Eureka moments: levels with a non-obvious trick that feels amazing to discover
- Near-miss design: players should frequently almost win on hard levels
- Progression variance: mix level types to avoid monotony

### Power-Up & Booster Integration
- Booster types: designed to help with specific difficulty spikes
- Free booster timing: given right before hard levels to demonstrate value
- Monetization hook: boosters solve frustration without being required
- Replayability: boosters should enable new strategies, not just skip content

### Scalable Production Pipeline
- Template system: parameterized level generators for base layouts
- Difficulty rating algorithm: automated difficulty scoring based on solve data
- Playtesting protocol: each level tested by X players before release
- A/B testing: test level order, difficulty, rewards in live game
- Community feedback: flag levels with high skip/quit rates for redesign

## OUTPUT FORMAT
Level design document with difficulty curve graph, mechanic introduction schedule, 20 example level briefs, and production pipeline workflow.

## CONSTRAINTS
- No level should be impossible without power-ups
- Tutorial must be completable without any text instructions
- Level completion data should inform dynamic difficulty adjustment
- All levels must be device-agnostic (same experience on all screen sizes)
- Plan for content drought: have 2-month buffer of unshipped levels