level-design
Level design fundamentals, pacing, difficulty progression, environmental storytelling, and spatial design for engaging gameplay experiences.
What this skill does
# Level Design ## Level Design Philosophy ``` ┌─────────────────────────────────────────────────────────────┐ │ LEVEL DESIGN PILLARS │ ├─────────────────────────────────────────────────────────────┤ │ 1. FLOW: Guide the player naturally through space │ │ 2. PACING: Control intensity and rest moments │ │ 3. DISCOVERY: Reward exploration and curiosity │ │ 4. CLARITY: Player always knows where to go │ │ 5. CHALLENGE: Skill tests that teach and satisfy │ └─────────────────────────────────────────────────────────────┘ ``` ## Level Structure Patterns ``` LINEAR LEVEL: ┌─────────────────────────────────────────────────────────────┐ │ [Start] → [Tutorial] → [Challenge] → [Boss] → [End] │ │ │ │ PROS: Easy to pace, clear direction │ │ CONS: Limited replay value, less exploration │ │ BEST FOR: Story-driven games, action games │ └─────────────────────────────────────────────────────────────┘ HUB & SPOKE: ┌─────────────────────────────────────────────────────────────┐ │ [Level A] │ │ ↑ │ │ [Level B] ← [HUB] → [Level C] │ │ ↓ │ │ [Level D] │ │ │ │ PROS: Player choice, non-linear progression │ │ CONS: Can feel disconnected │ │ BEST FOR: RPGs, Metroidvanias, open-world │ └─────────────────────────────────────────────────────────────┘ METROIDVANIA: ┌─────────────────────────────────────────────────────────────┐ │ ┌───┐ ┌───┐ ┌───┐ │ │ │ A │───│ B │───│ C │ (locked: need ability X) │ │ └─┬─┘ └───┘ └───┘ │ │ │ │ │ │ ┌─┴─┐ ┌─┴─┐ │ │ │ D │───│ E │ (grants ability X) │ │ └───┘ └───┘ │ │ │ │ PROS: Rewarding exploration, ability gating │ │ CONS: Can get lost, backtracking tedium │ │ BEST FOR: Exploration games, 2D platformers │ └─────────────────────────────────────────────────────────────┘ ``` ## Pacing & Flow ``` INTENSITY GRAPH (Good Pacing): ┌─────────────────────────────────────────────────────────────┐ │ High │ ╱╲ ╱╲ ╱╲ │ │ │ ╱ ╲ ╱╲ ╱ ╲ ╱ ╲ ╱╲ │ │ │ ╱ ╲ ╱ ╲ ╱ ╲╱ ╲ ╱ ╲ │ │ Low │───╱──────╲╱────╲──────────────╲╱──────── │ │ └────────────────────────────────────────→ Time │ │ │ │ PATTERN: Build → Peak → Rest → Build → Peak → Rest │ └─────────────────────────────────────────────────────────────┘ PACING ELEMENTS: ┌─────────────────────────────────────────────────────────────┤ │ BUILD-UP: │ │ • Introduce new mechanic safely │ │ • Increase difficulty gradually │ │ • Foreshadow upcoming challenge │ ├─────────────────────────────────────────────────────────────┤ │ PEAK (Combat/Puzzle): │ │ • Test player skills │ │ • High stakes moments │ │ • Boss encounters │ ├─────────────────────────────────────────────────────────────┤ │ REST: │ │ • Safe zones │ │ • Story/exploration moments │ │ • Resource replenishment │ │ • Save points │ └─────────────────────────────────────────────────────────────┘ ``` ## Environmental Storytelling ``` STORYTELLING TECHNIQUES: ┌─────────────────────────────────────────────────────────────┐ │ VISUAL NARRATIVES: │ │ • Abandoned objects tell stories │ │ • Environmental damage shows history │ │ • Character belongings reveal personality │ │ • Graffiti and notes provide context │ ├─────────────────────────────────────────────────────────────┤ │ ATMOSPHERE: │ │ • Lighting sets mood (warm=safe, cold=danger) │ │ • Sound design reinforces tone │ │ • Weather reflects narrative beats │ │ • Music cues emotional state │ ├─────────────────────────────────────────────────────────────┤ │ DISCOVERY LAYERS: │ │ • Surface: Obvious story elements │ │ • Hidden: Rewards for exploration │ │ • Deep: Lore for dedicated players │ └─────────────────────────────────────────────────────────────┘ ``` ## Whitebox Process ``` LEVEL DESIGN WORKFLOW: ┌─────────────────────────────────────────────────────────────┐ │ 1. CONCEPT (Paper) │ │ • Sketch rough layout │ │ • Define key beats │ │ • Identify player path │ │ ↓ │ │ 2. WHITEBOX (Engine) │ │ • Block out with primitives │ │ • Test scale and timing │ │ • Place placeholder enemies │ │ ↓ │ │ 3. PLAYTEST │ │ • Get feedback early │ │ • Iterate on layout │ │ • Fix flow issues │ │ ↓ │ │ 4. ART PASS │ │ • Replace with final art │ │ • Add lighting │ │ • Polish visual details │ │ ↓ │ │ 5. FINAL POLISH │ │ • Audio integration │ │ • VFX placement │ │ • Performance optimization │ └─────────────────────────────────────────────────────────────┘ ``` ## Player Guidance ``` VISUAL GUIDANCE TECHNIQUES: ┌─────────────────────────────────────────────────────────────┐ │ LIGHTING: │ │ ┌─────────────────────────────────────────────────────┐ │ │ │ [Dark] [BRIGHT PATH] [Dark] │ │ │ │ ↓ │ │ │ │ [OBJECTIVE] │ │ │ └─────────────────────────────────────────────────────┘ │ │ │ │ LANDMARKS:
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.