Level Designer

Designs game levels with layout specifications, pacing charts, encounter tables, and blockout documentation.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill level-designer-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Level Designer
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/game-development/level-designer
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill level-designer-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game levels often suffer from confusing navigation, unfair encounters, and empty filler spaces because layout decisions are made without a structured design process. This Skill provides a disciplined workflow for designing levels that guide players spatially, pace tension deliberately, and tell stories through environment rather than cutscenes. ## Core Features & Use Cases - Level Design Documentation: Produces complete level design documents including intent statements, layout specifications, encounter tables, and flow diagrams. - Pacing and Flow Architecture: Generates pacing charts mapping activity type and tension level over playtime, plus navigation affordance checklists for readability review. - Blockout Specifications: Creates grey-box room specs with dimensions, cover placement, lighting direction, and environmental story beats ready for art team handoff. - Use Case: A designer needs to spec a combat arena for a third-person shooter. The Skill produces the encounter table with tactical options and fallback positions, a blockout spec with cover and lighting layout, and a readability checklist to validate before any art work begins. ## Quick Start Ask the agent to design a level layout with a pacing chart, encounter list, and blockout specification for your game concept.

Frequently Asked Questions about Level Designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a game level layout that players can navigate?▼

Start with a paper flow diagram defining the critical path and optional branches, then build a grey-box blockout and playtest it before any art work. Use lighting, color, and geometry to guide attention so players never rely on a minimap for primary navigation.

What makes a good combat encounter design in games?▼

Every combat encounter needs entry read time, at least two tactical approaches, and a spatially obvious fallback position. Enemies should be visible before they can damage the player, except in deliberately telegraphed ambushes, and difficulty should come from layout before stat scaling.

How do I write a level design document for my team?▼

A level design document should include the player fantasy and pacing arc, layout specification with shape language and playtime estimates, an encounter table with tactical options, and a flow diagram. Add blockout specs per room covering dimensions, cover, lighting, and environmental story beats.

When should a level move from blockout to art pass?▼

A level moves to art pass only after grey-box playtesting confirms navigation readability and encounter viability, with design decisions locked at blockout. Never art-dress a layout that has not been playtested, since art cannot fix unreadable geometry.

Can this approach work for procedural level generation?▼

Yes, the Skill covers designing rule sets and grammars for procedural generation, including tiles, connectors, density parameters, and handcrafted critical path anchors. Procedural output is validated with automated metrics like reachability, key-door solvability, and encounter distribution.

What are the limitations of environmental storytelling in level design?▼

Environmental storytelling requires consistent prop placement, wear, and lighting aligned with the world's narrative history, and it cannot carry complex plot exposition alone. Success is measured by whether over 70 percent of playtesters correctly infer the story when asked.