Use when designing and producing game levels, worlds, encounters, missions, narrative content, procedural generation, streaming partitions, content schemas, validation, pacing, or multidisciplinary content handoffs.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add peterbamuhigire/chwezi-dev-engine --skill level-world-and-content-production --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Level World And Content Production?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/peterbamuhigire-level-world-and-content-production)More formats (shields.io, HTML) on the badges page.
---
name: level-world-and-content-production
description: Use when designing and producing game levels, worlds, encounters, missions, narrative content, procedural generation, streaming partitions, content schemas, validation, pacing, or multidisciplinary content handoffs.
metadata: {portable: true, compatible_with: [claude-code, codex]}
---
# Level, World, and Content Production
Turn design intent into versioned, testable content that a multidisciplinary team can produce at a measured rate.
## Use When
- Building levels, encounters, missions, dialogue/narrative packages, world partitions, spawning rules, or procedural content.
## Do Not Use When
- Core game-system architecture or asset creation is the primary task.
## Required Inputs
Player verbs, design pillars, content schema, camera/input, target performance, progression dependencies, accessibility/localisation constraints, asset kit, streaming/save model, throughput estimate, owners, and playtest questions.
## Workflow
1. Define level/encounter goals, teaching/test beats, pacing, metrics, dependencies, completion/failure, and observability.
2. Establish modular kits, naming/ownership, greybox-to-final gates, content schemas, validation, and review cadence.
3. Make streaming, checkpoints, save identifiers, spawn/despawn, navigation, and procedural seeds deterministic and migration-safe.
4. Test impossible states, sequence breaks, backtracking, interruption, low-memory streaming, localisation expansion, accessibility routes, and missing content.
5. Measure throughput and rework by content type; recalibrate schedule rather than hiding variance.
## Outputs
Content bible/schema; level and encounter briefs; dependency/streaming map; validators; playtest evidence; throughput forecast and variance; acceptance manifest.
## References
- [Content production gates](references/content-production-gates.md)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!