\r \r

Level Design Checklist Skill\r

\r

Purpose\r

Help a game creator review and improve a level design before building, testing, or publishing it.\r \r Use this skill for platformer levels, top-down levels, puzzle rooms, combat arenas, tutorial stages, and small indie game maps.\r \r

Inputs\r

Ask for or collect:\r

• Game genre\r
• Level goal\r
• Player abilities available in this level\r
• Main mechanic or teaching point\r
• Level map, sketch, blockout, or short description\r
• Target difficulty\r
• Known problems or player feedback\r \r

Checklist\r

\r

1. Player Goal\r

• The objective is clear within the first few seconds.\r
• The player can understand where to go next.\r
• The level has a start, middle, and finish.\r \r

2. Readability\r

• Important paths are visually stronger than decoration.\r
• Hazards, enemies, pickups, exits, and interactable objects are easy to recognize.\r
• The camera or viewpoint supports the main action.\r \r

3. Flow\r

• The level introduces one idea at a time.\r
• Safe practice comes before dangerous use.\r
• Challenge increases gradually.\r
• There are no long empty sections unless they serve pacing.\r \r

4. Fair Challenge\r

• Failures feel understandable, not random.\r
• Checkpoints or recovery points match the difficulty.\r
• Enemy and hazard placement gives the player time to react.\r
• Optional hard routes are clearly optional.\r \r

5. Mechanics\r

• The level teaches or tests the intended mechanic.\r
• Required abilities are available before they are needed.\r
• There are no softlocks or required jumps/actions that exceed intended player skill.\r \r

6. Rewards and Secrets\r

• Rewards guide exploration without confusing the main route.\r
• Secrets have visual hints or logic.\r
• Risk and reward feel balanced.\r \r

7. Performance and Scope\r

• The level is not overloaded with unnecessary objects.\r
• Reused assets are consistent.\r
• The level can be playtested quickly.\r \r

8. Playtest Notes\r

Record:\r

• Where players got confused\r
• Where players died unfairly\r
• Where players ignored the intended route\r
• What felt fun\r
• What should be cut or simplified\r \r

Output Template\r

\r

Level Review: [level name]\r
\r
Goal:\r
- [clear objective]\r
\r
Strong points:\r
- [what works]\r
\r
Problems found:\r
- [issue 1]\r
- [issue 2]\r
\r
Fix plan:\r
1. [small fix]\r
2. [small fix]\r
3. [test again]\r
\r
Playtest focus:\r
- Watch if players understand [specific moment]\r
```\r
\r
## Safety and Scope\r
- Do not recommend copyrighted level copying.\r
- Do not overbuild the level before testing.\r
- Prefer small playable improvements over large redesigns.\r