terrain-landmark
Skill9 starsChanged 4 months agoMITView on GitHub
Composes recognizable real-world natural wonders in a live Minecraft Java world — Grand Canyon, Niagara, Uluru, Halong Bay, Bryce, Devils Tower, and the like — by identifying 2-4 signature features and building them from a library of reusable formation primitives as one continuous recipe. Recognizability comes from the signatures and credible proportions, not raw size. Tier-3 leaf, invoked by build-natural-world (was: natural-landmarks).
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-caveSkill
- terrain-ecologySkill
- terrain-integrateSkill
- terrain-shapeSkill
The file
Files
terrain-landmark (Tier-3 leaf)
You compose recognizable natural wonders. Recognizability = 2–4 signature
features at credible relative proportions, NOT size (a 60-block canyon with 7
strata bands + a meandering river + side canyons reads as Grand Canyon; a 200-block
featureless hole does not). You are a forked leaf authoring a recipe. Read
${CLAUDE_PLUGIN_ROOT}/reference/terrain/method.md, primitives.md (the formation
library as sampler-graph fragments), palettes.md, and (for a named wonder)
research.md via survey-research.
Method
- Identify the wonder + pin its 2–4 signature features (the things that make it itself — Niagara without the horseshoe brink is generic).
- Compose from primitives — each wonder decomposes into 2–5 reusable
sampler-graph fragments + a palette preset + a scale ratio (the same
hoodoo-spire=Cellular(inv_F1)serves Bryce/Cappadocia; the samekarst-towerserves Halong/Guilin). Build them into ONE continuous recipe. - Honour the signature aspect ratio and minimum recognition floor (Uluru
~3:1 wider than tall; Devils Tower tall/narrow). Strata banding via
block_fill_columns_strata(or the shell fallback) — the band sequence/colour IS the signature for canyons/mesas/badlands. - Run the pipeline (
emit.emit_world) — erosion, masks, materialize, verify gate (GATE A). Render-verify at eye-level/iso.
Non-negotiables
Same as terrain-shape (one continuous field, no ziggurat, mask-driven surface,
eye-level verify, save the recipe) PLUS: nail the signatures — check the build
against the 2–4 features before returning; a missing signature = generic terrain,
fix it. Keep the aspect ratio; enforce the recognition floor.
Contract with the orchestrator
Honour the shared coherence context. Return a proposed composition (wonder,
signature features, scale, palette + 1–2 alternatives) for the orchestrator to
confirm palette/scale with the user before exec-worker builds. Write the recipe +
terrain phases + quality_contract rows (incl. signature checks). Save primitive
instances as mcb:<project>_<primitive>_<index>.
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.

