content-planning
Skill0 starsChanged 9 months agoMITView on GitHub
Level design and content scope planning. Use when planning level design, content production scope, pacing, procedural generation decisions, environment design, tutorial levels, world structure, or estimating content costs. Covers world structure, content-to-mechanic planning, pacing, procedural vs handcrafted, content reuse, content sequencing.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- vercel-labs/marketing-team-eve-templatetheir own version, first seen Oct 23, 2026
- vivy-yi/xiaohongshu-skillstheir own version, first seen Jan 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- vercel-labs/marketing-team-eve-template★ 459same name
- vivy-yi/xiaohongshu-skills★ 455same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- antipatternsSkill
- architecture-auditSkill
- ascii-wireframingSkill
- design-frameworksSkill
- difficulty-designSkill
- economy-designSkill
- implementationSkill
- mechanics-paletteSkill
- plan-auditSkill
- playtestingSkill
- scenario-walkthroughSkill
- scopingSkill
- simulation-guideSkill
The file
Files
Content & Level Planning
Plan content scope before building. Content is the most expensive part of most games — every hour of content costs many hours to produce.
Quick Reference
World Structure Decision
| Structure | Player Freedom | Scope Cost | Best For |
| Linear | Low — one path forward | Low | Platformer, puzzle, narrative |
| Hub-and-spoke | Medium — choose order within hub | Medium | Zelda-style, RPG, Metroidvania-lite |
| Open world | High — go anywhere | Very High | Sandbox, exploration, RPG |
| Metroidvania | Medium — gated by abilities | High | Exploration, ability-based progression |
| Procedural | Variable | High (to do well) | Roguelike, survival, infinite runners |
Decision rule: Choose the lowest-freedom structure that serves your core loop. More freedom = more content to fill the space = more scope.
Content Scope Estimation
| Content Type | Rough Production Ratio | Notes |
| Handcrafted level | 10-40 hours per 5 min of play | Includes design, art, testing, iteration |
| Enemy type | 2-5 days each | Design, art, animation, AI, balance |
| Boss encounter | 1-3 weeks each | High-impact but expensive |
| Cutscene/dialogue | 2-8 hours per minute | Writing, implementation, testing |
| Procedural system | Weeks-months upfront | Amortizes over infinite content |
Key principle: Content production does not scale linearly. Level 1 takes 2 days. Level 20 takes 2 days. But you need 20x the motivation to build level 20 as level 1. Plan for production fatigue.
Content Architecture Principle
Poor tooling makes equivalent content cost 10x more. Invest in content tools proportionally to how much content you'll build — but not before you know WHAT you're building.
Deep Dives
(see content-planning/pacing.md for Content-to-Mechanic Planning, Kishōtenketsu (Nintendo Pacing), Beat-Based Pacing, Environment-as-Teacher)(see content-planning/production.md for Procedural vs Handcrafted, Content Reuse Strategies, Content Anti-Patterns, Content Sequencing)
See Also
- scoping — Feature cutting applies to content decisions
(see scoping → MLP Scoping Process) - difficulty-design — Difficulty pacing through content, boss design as content milestones
(see difficulty-design) - scenario-walkthrough — Narrate content before building it
(see scenario-walkthrough → The 5-Beat Structure) - economy-design — Content as economy scope
(see economy-design) - antipatterns — Premature Content anti-pattern
(see antipatterns) - design-frameworks — Onboarding patterns for tutorial level design
(see design-frameworks → Game Feel, Juice & Onboarding) - playtesting — Content batching should match playtest cadence
(see playtesting)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.