terrain-cave
Skill9 starsChanged 4 months agoMITView on GitHub
Designs deliberate subterranean space in a live Minecraft Java world — cave systems, cavern halls, ravines, lava tubes, mines, vaults, and the surroundings of an underground base — as opposed to the random vanilla caves the world already has. Carves intentional voids with a known entrance, route, and chambers sized for a purpose, then dresses them (strata, dripstone, lichen, water). Tier-3 leaf, invoked by build-natural-world / build-structure / build-settlement.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-natural-worldSkill
- build-settlementSkill
- build-structureSkill
- build-systemsSkill
- design-buildingSkill
- design-citySkill
- design-groundsSkill
- design-houseSkill
- design-monumentSkill
- design-villageSkill
- exec-blueprintSkill
- exec-inspectSkill
- exec-planSkill
- exec-reflectSkill
- exec-workerSkill
- setup-connectSkill
- setup-fabricSkill
- setup-modSkill
- setup-serverSkill
- survey-researchSkill
- survey-siteSkill
- system-redstoneSkill
- system-transitSkill
- terrain-ecologySkill
- terrain-integrateSkill
- terrain-landmarkSkill
- terrain-shapeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 37
Structural safety: Leave pillars/thick ceilings over wide spans.
- Very specific: line 47
No flat 30-block ceilings (vary + pillar them).
≈ “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
terrain-cave (Tier-3 leaf)
You design deliberate underground space — not noise the player stumbles into,
but a void with intent: a known entrance, a route, chambers sized for a purpose,
and a material story. You are a forked leaf authoring a recipe + carve/dress
phases. Read ${CLAUDE_PLUGIN_ROOT}/reference/terrain/caves.md (your method) and
toolkit-api.md.
Method
- Plan the space. Entrance, route, chamber sizes/purposes, the material story
(stone type, ores, dripstone, water). For a cave base, size the chamber for
the build it will host and hand the floor+walls to
build-structure. - Carve the void (anisotropic 3D noise threshold).
- Cheese caverns (wide, rounded): sample 3D noise at
(x*0.5, y, z*0.5), carveairwherenoise < ~-0.3, damped near the surface. - Ravines (tall, thin): sample at
(3x, 0.4y, 3z), carve wherenoise < ~-1.3with a log depth filter. - Tubes/passages: swept circular cross-section along a
Centerlineroute. Emit asairfills viablock_fill_region(hollow) /block_fill_batch— tile manually under the 32,768 cap;block_replace_in_regiondoes NOT auto-tile.
- Cheese caverns (wide, rounded): sample 3D noise at
- Structural safety. Leave pillars/thick ceilings over wide spans; vary ceiling height; never carve into a fluid body without a plan (check the survey); plan lighting as part of the build, not after.
- Dress the void. Strata on the walls (deepslate below y0); features via
level_place_feature(dripstone_cluster,pointed_dripstone,glow_lichen,cave_vine,moss_patch,amethyst_geode) mask-gated (lichen on walls, dripstone on ceiling, moss in damp/low areas); water/lava features along the route.
Non-negotiables / quality_contract
No flat 30-block ceilings (vary + pillar them); support present over spans; the
space is lit; no unintended fluid breach. Runs through GATE A (verify) and
exec-inspect like any terrain. If the cave hosts a build, ground it with
terrain-integrate so it sits in the cave, not in a box carved out of it.
Return the carve+dress phases and the chamber dimensions to the orchestrator.
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.

