level-design
Level Design Skill
A design consulting framework based on "Level Design: Processes and Experiences" edited by Christopher W. Totten (CRC Press, 2017).
Core Philosophy
Level design is the thoughtful execution of gameplay into gamespace for players to dwell in. It sits at the intersection of programming, design, and art—implementing the game design vision while leading players through experiences without revealing the designer's presence.
"Level designers don't merely create things for players to do. They create situations that invite players to interpret who they are." — Brian Upton
The Designer's Core Tasks
- Guide without forcing — Lead players through intended experiences while maintaining illusion of freedom
- Teach through space — Use environment to communicate mechanics, not tutorials
- Control pacing — Modulate intensity through spatial rhythm and stillness
- Support narrative — Align levels within overall game progression
- Create consistency — Establish and honor environmental rules players can rely on
More from jarrodmedrano/jarrod-claude-skills
threejs-scene-builder
Comprehensive Three.js and React Three Fiber skill for creating 3D scenes, characters, NPCs, procedural generation, animation retargeting, and interactive experiences. Use when user asks to "create Three.js scene", "setup React Three Fiber", "add 3D character", "create NPC AI", "procedural 3D generation", "retarget animation", "setup avatar system", or "create 3D game".
69guitar-fretboard-mastery
>
40game-feel
>
24game-design-theory
>
23guitar-fretboard
Create interactive guitar fretboard visualizations for scales, chords, CAGED system, triads, intervals, and note positions. Use this skill when users ask to build guitar learning tools, visualize scales/modes/pentatonics on the fretboard, show chord shapes, display CAGED patterns, create interval diagrams, or build any guitar theory visualization as React artifacts. Supports standard tuning, custom tunings, and comprehensive music theory for guitar.
20frontend-performance-reviewer
Use when reviewing React/frontend code for performance issues, before optimization work, when page load is slow (>3s), when users report UI lag, or when preparing production deployments requiring performance validation
17