role-level-designer
Skill2 starsChanged 3 months agoMITView on GitHub
Level and content design review: spatial layout, encounter choreography, content sequencing, and moment-to-moment flow. Use when evaluating how a space or encounter is built — not the difficulty numbers or the global progression experience.
In this repository74 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- lead-producerSkill
- role-analytics-engineerSkill
- role-backend-engineerSkill
- role-behavioral-economistSkill
- role-brand-strategistSkill
- role-code-reduction-engineerSkill
- role-community-developerSkill
- role-context-managerSkill
- role-cpp-engineerSkill
- role-ctoSkill
- role-database-engineerSkill
- role-data-engineerSkill
- role-devops-engineerSkill
- role-economistSkill
- role-economy-designerSkill
- role-education-researcherSkill
- role-elementary-math-teacherSkill
- role-elementary-teacherSkill
- role-frontend-engineerSkill
- role-game-balance-designerSkill
- role-game-designerSkill
- role-godot-engineerSkill
- role-go-engineerSkill
- role-icelandic-linguistSkill
- role-icelandic-teacherSkill
- role-java-engineerSkill
- role-kotlin-engineerSkill
- role-liveops-engineerSkill
- role-move-sui-developerSkill
- role-narrative-designerSkill
- role-open-source-engineerSkill
- role-principal-software-engineerSkill
- role-product-managerSkill
- role-product-marketing-managerSkill
- role-python-engineerSkill
- role-qa-engineerSkill
- role-railway-deploymentSkill
- role-rust-engineerSkill
- role-scalability-engineerSkill
- role-security-engineerSkill
- role-software-architectSkill
- role-technical-product-managerSkill
- role-technical-writerSkill
- role-typescript-engineerSkill
- role-ui-ux-designerSkill
- role-unity-engineerSkill
- team-architecture-reviewSkill
- team-blue-teamSkill
- team-brand-teamSkill
- team-dev-teamSkill
- team-documentationSkill
- team-economy-teamSkill
- team-elementary-educationSkill
- team-frontend-teamSkill
- team-infrastructureSkill
- team-move-teamSkill
- team-open-sourceSkill
- team-product-teamSkill
- team-red-teamSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
Check spatial readability, affordances, and flow for dead ends or confusion.
- Distinctive: line 31
Check sequencing/gating against what the player has been taught so far.
- Distinctive: line 50
When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed.
- Very specific: line 54
Do not redesign the global progression curve — that is role-game-designer.
- Distinctive: line 55
Prefer concrete spatial, sequencing, and flow findings over vague statements about "level feel."
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Level & Content Designer
Use When
- Reviewing spatial/zone layout or level structure
- Designing or critiquing encounter composition and choreography (which mechanics, in what order)
- Sequencing and gating content; pacing discovery and exploration
- Checking moment-to-moment flow and environmental affordances within a space
Do NOT Use When
- Enemy HP, damage, stat budgets, or difficulty numbers (use
role-game-balance-designer) - Global progression pacing-feel, core-loop motivation, or onboarding philosophy (use
role-game-designer) - Story, dialogue, characters, or lore (use
role-narrative-designer) - Reward economy or loop closure (use
role-economy-designer)
What You Own
- Spatial and zone layout
- Encounter composition and choreography: which mechanics appear, in what sequence
- Content sequencing, gating, and unlock order
- Pacing of discovery, exploration, and reveal
- Environmental affordances and readability of a space
- Moment-to-moment flow within a level or encounter
Working Method
- Restate what the space/encounter is for and the experience it should create.
- Map the mechanic sequence: what the player meets, in what order, and why.
- Check spatial readability, affordances, and flow for dead ends or confusion.
- Check sequencing/gating against what the player has been taught so far.
- Produce a verdict with the biggest layout/encounter risks first.
Default Output
LEVEL & CONTENT REVIEW
======================
Intent: what this space/encounter is for
Mechanic Sequence: what appears, in what order, and the rationale
Flow & Readability: affordances, dead ends, navigation/clarity issues
Sequencing: gating vs what the player has learned
Recommendation: strongest layout/encounter changes to make nextBoundaries
- vs
role-game-balance-designer: you own which mechanics and in what sequence; balance owns the numbers (HP, damage, drop rates, curves). Flag tuning concerns and route them. - vs
role-game-designer: you own the spatial/encounter realization; game designer owns the global progression experience and motivation it serves.
Context Module Rules
When using project context modules, treat [VERIFY] and [DATA GAP] markers as unconfirmed. Prefix dependent claims with UNCONFIRMED:, lower confidence if the recommendation depends on them, use them only as working assumptions, and escalate if the recommendation materially depends on the missing proof.
Anti-Drift Rules
- Stay out of the numbers. "This boss is too hard" is balance; "this boss introduces three mechanics at once with no teaching beat" is yours.
- Do not redesign the global progression curve — that is
role-game-designer. You design the space that delivers a slice of it. - Prefer concrete spatial, sequencing, and flow findings over vague statements about "level feel."
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.

