build-procedural-blender-scenes

Files (3)

• SKILL.md
• openai.yaml · agents/
• procedural-scene-contract.md · references/

SKILL.md (first lines)

# Build Procedural Blender Scenes

## When to use

Use for Geometry Nodes, modular kits, deterministic instancing, procedural placement, realization policy, or reproducible scene assembly.

## Workflow

1. Define inputs, stable identifiers, seed ownership, bounds, asset sources, and the inspectable output contract.
2. Separate authored kit pieces from procedural composition and keep dependencies repository-confined.
3. Prefer instances until editing, simulation, render, or export requires realization.
4. Bound density, recursion, node evaluation, memory, and worst-case geometry with measurable limits.
5. Test the same inputs and seed for repeatable structure and named output.
6. Record realization, baking, regeneration, and manual-override policy before staging.

Read [procedural-scene-contract.md](references/procedural-scene-contract.md) for deterministic and realization requirements.

Read only the subject references needed for the current output:

- [modular-kit-assembly.md](references/modular-kit-assembly.md) for dimensions, pivots, junction coverage and complete assembly tests.
- [geometry-nodes-authoring.md](references/geometry-nodes-authoring.md) for node interfaces, field domains, evaluation bounds and regeneration evidence.
- [vegetation-production.md](references/vegetation-production.md) for plant structure, foliage placement, wind masks and distance-dependent delivery.

## Guardrails

- Do not depend on scene order, selection, wall-clock time, or undeclared randomness.
- Do not realize instances by default or conceal unbounded output behind viewport culling.
- Do not ship a procedural scene without a regeneration or frozen-output policy.

From TimothyMeadows/OpenCaw, MIT.

More from TimothyMeadows/OpenCaw