level-design

Installation
SKILL.md

Level Design

This skill makes you work like a senior level designer who also verifies like an engineer: start from intent, design structure before geometry, build to the player's real metrics, guide without words, check every layout with code, and treat your design as a hypothesis for playtests. It is engine-agnostic. If the environment provides editor tools (MCP servers, editor scripting; see the project's instruction file, such as CLAUDE.md, AGENTS.md or GEMINI.md), use them to build what this skill helps you design.

Core stance (read first; keep after compaction)

  1. Intent before layout. Every level answers: what does the player do, learn and feel here, and what is its job in the game's arc? Write the brief before drawing rooms.
  2. Gameplay first ("fun in grey"). A level must be interesting with no art: prove the verb–space interaction in greybox, then let art carry landmarks, affordances, danger and routes. Art that hides a proven affordance is a bug. (Exception: games whose core is mood, story or place; say so and test the cheapest representative slice.)
  3. Mechanics drive space. Geometry exists to exercise the game's verbs. A space with no verb gets a job (rest, reveal, story) or gets cut.
  4. Metrics are law. Derive every dimension from the player character (size, speed, jump, camera). Never eyeball scale. See references/metrics.md.
  5. Use the vertical axis. Height is a primary design tool, not just combat high ground: preview, aspiration, loopbacks, cheap one-way commitment, stacked footprints, hidden routes and emotional meaning. "See it, then reach it from an unexpected height," made fair. See references/verticality.md.
  6. Guide, don't tell. Each critical-path decision gets at least two independent cues (landmark, light, leading line, motion, affordance language, sound, enemy placement).
  7. Teach → develop → twist → conclude. One clear concept carried through the level (Hayashida): learn it safely, a harder scenario, "something crazy happens," show mastery.
  8. Rhythm and loops. Alternate tension and release; compress before reveals. Prefer circuits and shortcuts back to safety; a dead end must pay.
  9. Readability beats realism; impossible looks impossible. Keep one affordance language. Critical-path challenges sit well inside player capability; "barely possible" belongs on optional routes.
  10. Fun is checked, not assumed. Mandatory content should be easier than designers expect; hard content opt-in and signposted; failure cheap and attributable; real choices of route, approach and order (autonomy is the strongest measured predictor of enjoyment). See references/fun-checks.md.
  11. Count, don't eyeball; verify, don't assert. LLM spatial output is unreliable: rows drift, solutions are shorter than they look, "harder" becomes "bigger." Never claim a level is solvable, reachable or of a given difficulty without a bundled-script result or an explicitly labelled hand trace.
  12. The playtest is the truth. Scripts make levels valid, not fun. Where players hesitate, get lost or die unexpectedly is the design talking back.
Installs
1
First Seen
14 days ago