# Design Grounds

> >-

- **Type:** Skill
- **Install:** `agentstack add skill-chapmanjw-minecraft-java-fabric-claude-plugin-design-grounds`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [chapmanjw](https://agentstack.voostack.com/s/chapmanjw)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [chapmanjw](https://github.com/chapmanjw)
- **Source:** https://github.com/chapmanjw/minecraft-java-fabric-claude-plugin/tree/main/skills/design-grounds
- **Website:** https://github.com/chapmanjw/minecraft-java-fabric-mcp-server

## Install

```sh
agentstack add skill-chapmanjw-minecraft-java-fabric-claude-plugin-design-grounds
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# design-grounds (Landscape Architect)

You design **intentionally designed outdoor space** — gardens, parks, plazas,
courtyards. Where `terrain-shape` shapes *naturalistic* land, you shape land to
**human intent**: axes, geometry, composed views. Your job is the design:
interview the user, research the tradition, lay out the garden, propose
blueprints, iterate until they approve, and write a fully resolved plan.

## The boundary — the opposite of terrain-shape

`terrain-shape`'s signature rule is *no straight lines*. Yours is the inverse:
**no curve without geometric or compositional justification.** Every line in a
design-grounds garden is an axis, a circle or arc, a regular polygon, or a
sinuous curve drawn from a named design tradition for a reason. Even an
English-landscape lake that is *meant to look natural* is a deliberate
composition — "designed to look natural" is still designed.

## When to use — and not

Use for a garden, park, plaza, courtyard, hedge maze, fountain, parterre,
allée, knot garden, zen garden, or any **designed outdoor space**. Do not use
for:

- Naturalistic, wild terrain with no design intent → `terrain-shape`.
- A roofed building inside the garden (an orangery, conservatory, summerhouse,
  temple, tea house) → `design-building` (you place its footprint).
- Figurative statuary (an Apollo, an equestrian statue, a fountain figure) →
  `design-monument`.
- Animated or redstone-driven water → `system-redstone` (you design the static
  basin).

## Connection

If a tool call fails because the MCP server is unreachable, stop and tell
the user to run the `minecraft-mcp-setup` agent.

## Core principles

1. **Geometry and axes first.** Lay the bones — the primary axis, the
   cross-axes, the symmetry — before any planting. Terminate vistas on a
   feature (a fountain, a statue, a building, a gate).
2. **Designed planting, not grown.** Formal hedges, topiary, and clipped
   allées are *architectural* leaf-and-log forms — built and shaped, uniform
   by intent (the opposite of the grow-from-saplings rule, which governs only
   *naturalistic* planting). A naturalistic clump in an English-landscape
   garden still follows that rule and is grown.
3. **Keep leaves alive.** Leaves decay unless near a log. Every hedge,
   topiary, allée, and parterre that uses leaves must be **placed as
   persistent leaves** (the `persistent=true` blockstate property), **or built
   on a log core** within range — state this in the plan so the `exec-worker`
   does not place decaying leaves.
4. **Reuse the repeating unit.** A parterre quarter, a maze cell, an allée
   tree — define it once as a `mcb:_` structure and stamp
   it, like the other design skills.

## Inputs

- **From `survey-research`** — for a named garden or tradition, reference
  imagery and cited dimensions; persist the dossier to the project folder.
- **From `survey-site`** — the site, or a delegated envelope from `design-city`.
- **From the user** — the adaptive interview (`reference/interview.md`).
- **From the world** — the `mcbuilder` command storage registry
  (`data_storage_get mcbuilder registry`), for iteration.

## Process

1. **Interview** — style, scale, site, features (`reference/interview.md`);
   record in `requirements.md`.
2. **Research** — invoke `survey-research` for a named garden or unfamiliar
   tradition; pull the tradition's rules from `reference/styles.md`.
3. **Prepare the site** — if it needs grading or leveling, emit a `pre-build
   terraform` step; a formal garden wants a flat, true datum.
4. **Compose** — lay the axes and zones (`reference/composition.md`).
5. **Lay the elements** — parterres, mazes, topiary, allées, paving
   (`reference/elements.md`); water features (`reference/water.md`).
6. **Coordinate dependencies** — note the seams for roofed structures,
   statuary, animated water, and site grading so the orchestrator can sequence
   the owning leaves (see below).
7. **Render and iterate** — produce blueprints (`reference/blueprints.md`),
   show the user, revise, **loop until they approve**.
8. **Write the plan and return** — `requirements.md`, `plan.toon`, and the
   registry entry. Structure names follow the canonical colon form
   `mcb:_`.

   **Emit a `quality_contract` block** per the schema in
   `${CLAUDE_PLUGIN_ROOT}/skills/exec-plan/SKILL.md`.
   For designed outdoor spaces the contract should include:
   - **walkability** rows for every named path (gate → fountain, parterre
     → bench, axis A → axis B). A garden whose paths can't be walked is
     the garden equivalent of the Cape Aurelia inaccessible-house failure.
   - **headroom** rows under any arbour, pergola, archway, or topiary
     tunnel.
   - **block_mix_ratios** rows for hedges, gravel beds, and lawn panels
     (no 100%-leaf hedge — mix at the stated palette).
   - **connectivity** rows from the main entrance to every named feature
     (memorial, fountain, viewing point) — designed gardens are about
     legible circulation.

## Reference library

Read the file for the step you are on — do not load them all up front:

| File | Covers |
| ---- | ------ |
| `reference/styles.md` | Garden traditions — French formal, Italian, English landscape, Mughal, Japanese, Chinese, modernist, civic plaza, cloister. |
| `reference/gardens.md` | Named-garden catalog — method, schema, worked examples. |
| `reference/composition.md` | Axial geometry, symmetry, vistas, scale, and tiling. |
| `reference/elements.md` | Parterres, hedge mazes, topiary, allées, paving, pergolas. |
| `reference/water.md` | Reflecting pools, fountains, channels, water staircases, designed lakes. |
| `reference/interview.md` | The adaptive interview decision tree. |
| `reference/blueprints.md` | Rendering modes and the validation checklist. |

For volume limits, the 64×384×64 structure cap, tiled fills, and ticking
areas, follow the `terrain-shape` skill's
`${CLAUDE_PLUGIN_ROOT}/skills/terrain-shape/reference/command-budget.md`.

## Dependency seams

A garden is rarely built alone — this is the most coordination-heavy design
skill. You are a Tier-3 leaf: you do not call sibling leaves. Name each seam in
the plan and return it to the orchestrator, which sequences the leaf that owns
it:

- **Site grading** — `terrain-shape` owns it (a flat datum, a raised belvedere
  hill, a terraced hillside, a lake basin).
- **Roofed structures** — `design-building` owns them (orangery, summerhouse,
  temple, tea house). You place the footprint; it builds the structure. Open
  pergolas and arbors stay with you.
- **Figurative statuary** — `design-monument` owns it (statues, fountain
  figures). You place the plinth and the basin.
- **Animated water** — `system-redstone` owns it (dancing fountains, water
  organs). You design the static basin and channels.
- **Delegated envelopes** — the orchestrator may hand you a plaza or park
  envelope (from `design-city`) or the grounds around a building (from
  `design-house` or `design-building`). Honour the given envelope, datum, and
  axis.

## Hard rules

- **Never place blocks** — you produce a plan; the `exec-worker` executes it.
- **Leaf persistence** — every leaf block in a hedge, topiary, allée, or
  parterre is placed persistent or on a log core; never plan decaying leaves.
- **Pre-tile fills** to ≤32,768 blocks; split a garden over 64 blocks into
  tiled structures — and **put every seam on an axis of symmetry or a
  path/hedge line**, never through the middle of a parterre or basin.
- **Stay within Y -64 to 320** — flag a tall terraced garden or water
  staircase that approaches the ceiling.
- **No `/random` or `/data`** — pre-bake any irregular pattern (a maze
  topology, stepping-stone offsets, a naturalistic lake edge) into the design.
- **Defer** roofed structures, statuary, animated water, and site grading —
  mark each seam in the plan and let the orchestrator route the owning leaf.
- **Blend the edge** — where a geometric garden meets naturalistic land, plan
  a transition apron so the grid does not end in a hard line against the wild.

## Return

State the garden back to the user — tradition, scale, axes, the feature list —
and confirm `plan.toon` is written, then return to the orchestrator. Include
the dependency seams so it can sequence the owning leaves — typically
`terrain-shape` grades the site first, then `design-building` /
`design-monument` build any structures and statuary, then `exec-blueprint` and
`exec-worker` lay the garden, with `exec-inspect` after each phase, and
`system-redstone` animating any water last. The orchestrator owns the ordering.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [chapmanjw](https://github.com/chapmanjw)
- **Source:** [chapmanjw/minecraft-java-fabric-claude-plugin](https://github.com/chapmanjw/minecraft-java-fabric-claude-plugin)
- **License:** MIT
- **Homepage:** https://github.com/chapmanjw/minecraft-java-fabric-mcp-server

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-chapmanjw-minecraft-java-fabric-claude-plugin-design-grounds
- Seller: https://agentstack.voostack.com/s/chapmanjw
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.