unreal-worlds
Skill4 starsChanged 3 months agoMITView on GitHub
Build open worlds with World Partition, Landscape, procedural foliage, HLOD and level streaming. Use when sculpting landscapes, biomes, or World Partition in Unreal.
In this repository47 other files it gives its agents.
- anti-cheatSkill
- blender-add-on-engineerSkill
- blender-animationSkill
- blender-modelingSkill
- blender-toolingSkill
- game-aiSkill
- game-audio-engineerSkill
- game-audioSkill
- game-build-pipelineSkill
- game-designerSkill
- game-designSkill
- game-ideationSkill
- game-monetization-designerSkill
- game-monetizationSkill
- game-performanceSkill
- game-uiSkill
- game-version-controlSkill
- godot-gameplay-scripterSkill
- godot-multiplayer-engineerSkill
- godot-shader-developerSkill
- level-designerSkill
- level-designSkill
- narrative-designerSkill
- narrative-designSkill
- playtest-feedback-analyzerSkill
- playtestingSkill
- production-planningSkill
- roblox-avatar-creatorSkill
- roblox-experience-designerSkill
- roblox-systems-scripterSkill
- tech-artSkill
- technical-artistSkill
- unity-architectSkill
- unity-architectureSkill
- unity-editor-tool-developerSkill
- unity-multiplayer-engineerSkill
- unity-multiplayerSkill
- unity-shader-graph-artistSkill
- unity-shadersSkill
- unity-toolingSkill
- unreal-multiplayer-architectSkill
- unreal-multiplayerSkill
- unreal-systems-engineerSkill
- unreal-systemsSkill
- unreal-tech-artSkill
- unreal-technical-artistSkill
- unreal-world-builderSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Never place gameplay-critical content at cell boundaries
- Distinctive: line 21
Always-loaded content in dedicated Always Loaded data layer
- Distinctive: line 34
Use clear headings and bullet lists where helpful.
- Distinctive: line 35
Call out assumptions and open questions at the end.
- Distinctive: line 47
NEVER weaken or skip a failing test to make a change land.
- Distinctive: line 48
NEVER swallow errors silently or leave unhandled rejections in production paths.
- Distinctive: line 49
NEVER introduce a breaking API change without a version bump and migration path.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Unreal Worlds
Core Mission
- Configure World Partition grids and streaming sources for hitch-free loading
- Build Landscape materials with multi-layer blending and runtime virtual texturing
- Design HLOD hierarchies that eliminate distant geometry pop-in
- Implement foliage and environment population via PCG
- Profile open-world performance with Unreal Insights
Critical Rules
- Cell size by streaming budget: 64m dense urban, 128m open terrain, 256m+ sparse
- Never place gameplay-critical content at cell boundaries
- Always-loaded content in dedicated Always Loaded data layer
- Max 4 active Landscape layers per region; enable RVT for 2+ layers
- HLOD for all areas visible at > 500m camera distance
- Large-scale population uses PCG, not Foliage Tool
Success Metrics
- Zero streaming hitches > 16ms during sprint traversal
- PCG areas > 1km² pre-baked
- HLOD covers all areas visible at > 500m
- Nanite instance count within 16M limit
Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Unreal World Builder workflow; avoid generic filler.
Verification & Quality Checklist
- Code compiles and all automated tests and typechecks pass without new warnings.
- Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- No hardcoded secrets, credentials, or insecure defaults introduced.
- Changes are covered by a test that fails without them.
Anti-Patterns & Constraints
- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.
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.

