level-design
/level-design
Use when designing, generating, or reviewing the craft of an individual level, zone, or encounter — layout, wayfinding, structural type, lock-and-key gating, antepieces, arena design, in-level pacing, and the greybox process. Also use to diagnose levels where players get lost, challenge feels unfair, pacing drags, or teaching moments land flat. Triggers on "level design", "level layout", "greybox", "blockout", "wayfinding", "sightlines", "lock and key", "arena design", "encounter design", "the level feels confusing", "players get lost", "chokepoint", "flanking route", "intensity curve", "antep
- Author
- rondorkerin ↗
- Repository
- gamestack ↗
- Licence
- MIT
- Last repository change
- 30.06.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when designing, generating, or reviewing the craft of an individual level, zone, or encounter — layout, wayfinding, structural type, lock-and-key gating, antepieces, arena design, in-level pacing, and the greybox process. Also use to diagnose levels where players get lost, challenge feels unfair, pacing drags, or teaching moments land flat. Triggers on "level design", "level layout", "greybox", "blockout", "wayfinding", "sightlines", "lock and key", "arena design", "encounter design", "the level feels confusing", "players get lost", "chokepoint", "flanking route", "intensity curve", "antep
Triggers from the description
Original author description
Use when designing, generating, or reviewing the craft of an individual level, zone, or encounter — layout, wayfinding, structural type, lock-and-key gating, antepieces, arena design, in-level pacing, and the greybox process. Also use to diagnose levels where players get lost, challenge feels unfair, pacing drags, or teaching moments land flat. Triggers on "level design", "level layout", "greybox", "blockout", "wayfinding", "sightlines", "lock and key", "arena design", "encounter design", "the level feels confusing", "players get lost", "chokepoint", "flanking route", "intensity curve", "antep
How it works
- When to use this
- Scope
- How the pieces fit
- The one idea to anchor on
SKILL.md preview
--- name: level-design description: Use when designing, generating, or reviewing the craft of an individual level, zone, or encounter — layout, wayfinding, structural type, lock-and-key gating, antepieces, arena design, in-level pacing, and the greybox process. Also use to diagnose levels where players get lost, challenge feels unfair, pacing drags, or teaching moments land flat. Triggers on "level design", "level layout", "greybox", "blockout", "wayfinding", "sightlines", "lock and key", "arena design", "encounter design", "the level feels confusing", "players get lost", "chokepoint", "flanking route", "intensity curve", "antepiece", "teach the mechanic", "critical path", "leading lines", "weenie", "breadcrumbs", "level feels boring", "players don't know where to go". --- # Level Design How to craft a level — or generate one — that guides players through space so they always know where to go and why, teaches through the environment instead of a tutorial pop-up, paces intensity as a rhythm of peaks and valleys, and validates all of it in blockmesh before a single art asset is committed. > **Tier:** universal craft (→ `gamestack-core`). Applies to every genre that has levels, rooms, or encounters. The macro/world spatial layer lives in `open-world-design`; this skill owns the *level/encounter* craft. ## When to use this - Laying out a level or zone — structure type, critical path, arenas, shortcuts - Designing or auditing wayfinding (players getting lost or marker-following) - Authoring antepieces and teaching sequences for new mechanics - Designing or diagnosing encounter/arena propositions - Plotting and tuning in-level intensity curves - Specifying a blockmesh-first process a generator can follow ## Scope This skill owns the **level/encounter** spatial craft layer. Adjacent concerns live in sibling skills: - The *macro/world* spatial layer (terrain, biomes, world-map layout, exploration pull) → `open-world-design` - *What* to generate and how to validate generated content → `procedural-generation`, `procgen-review` - Combat-specific feel (hit-stop, telegraphing, enemy feel) within arenas → `combat-design` - In-level pacing as part of a session-wide arc → `pacing-and-the-player-journey` - Signposting, landmarks, signal color, silhouette → `art-direction-and-readability` - Teaching through space as part of the onboarding arc → `onboarding-and-teaching` - General reward/flow/motivation theory → `game-design-fundamentals` ## How the pieces fit - **`GUIDE.md`** — the cited *why*, in six sub-domains: guidance language (critical path, breadcrumbing, leading lines, weenies, light/color, affordances); structure & gating (structural types, lock-and-key, interconnection/shortcuts, Metroidvania loop); teaching through space (antepiece, intro→develop→twist→conclude, the gym); encounter/arena design (arena proposition, cover, chokepoints, flanking, verticality); in-level pacing (intensity curve, rest beats, reward placement); and the greybox process (blockmesh, metrics, playtest iteration). Each rule carries an exemplar + source, a **test-for** criterion, the named failure mode, and the **procedural/headless implication**. - **`CHECKLIST.md`** — Do/Don't + machine-checkable **Test-for** criteria, grouped by sub-domain. Written to be enforced as validators in a generation loop. ## The one idea to anchor on > **Guide the player through the space itself — not the HUD.** Landmarks, light, leading lines, and affordances must tell the player where to go and what to do before a minimap arrow ever has to try. If a player is watching a minimap instead of the horizon, the level has become an obstacle between them and a waypoint. Start with `GUIDE.md`, then apply `CHECKLIST.md`.
Files in this package (3)
- CHECKLIST.md 9 KB
- GUIDE.md 26 KB
- SKILL.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rondorkerin/gamestack | 90 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| gamedev-skills/awesome-gamedev-agent-skills | 100 | Apache-2.0 |
| sheepk95/The-Cartographer | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 90c48d274e85 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 4 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95design-level-design
Use when designing game levels, environments, difficulty curves, pacing, encounter placement, or spatial layouts for any game genre. Triggers: level, pacing, difficulty curve, encounter, environment, spatial design. - 90godot-greybox
Fast HAND-AUTHORED STATIC blockout for prototyping ANY level in Godot — write real, editable nodes (one floor, walls/props, hazards, NavigationRegion3D) DIRECTLY into `levels/<name>.tscn` so every piece is selectable and movable in the editor. Turns a level-designer concept… - 90level-designer
Level layouts, flow, metrics, Unity greybox (ProBuilder/Splines), pacing, encounters, match-3/puzzle level sequencing. Use for building or fixing levels. - 90pacing-and-the-player-journey
Use when designing, auditing, or generating the macro arc of an experience — how engagement rises and falls across an encounter, a session, a level, and an entire playthrough. Covers the interest curve and fractal pacing, tension/rest rhythm, novelty cadence and mid-game sag,… - 90open-world-design
Use when designing, generating, or reviewing the spatial side of an open world — macro-layout and terrain, landmarks and sightlines, biome identity, verticality, navigation/wayfinding, signal color, exploration pull, and spatial pacing (the wonder→fear gradient,… - 90wayfinding-navigation
Design navigation and information architecture for cognitive accessibility. Use when designing or reviewing navigation, site maps, page hierarchies, breadcrumbs, search, multi-step flows, or any structure where users need to find content and know where they are. Triggers on:…