Moonsail Blender 3D

Use for Blender scene creation and repair, reference-led 3D reconstruction, product or architectural visualization, procedural assets, animation, rendering, and export. Use another Moonsail content skill with this one when the Blender artifact serves a film, campaign, product demo, marketplace image, or cinematic scene.

Raw

Follow the shared production kernel from the Moonsail root. This skill owns Blender judgment and evidence. The current job owns the brief, source roles, scene contract, execution location, checkpoints, scripts, budget, and outputs.

The editable .blend file is the authoritative scene source for the delivered revision. Preserve authoring scripts and declared assets with SHA-256 hashes. State whether the next revision starts from that .blend or regenerates it from a named script revision. A script does not contain manual edits that exist only in the saved scene; do not regenerate over those edits without reconciling them. Renders, videos, and GLB files are derivatives.

Load the Right Modules#

Load only the guidance needed for the current action.

Task	Reference
Define the asset, shot, references, scale, style, or delivery contract	Design
Model, shade, light, compose, animate, or stage the scene	Craft
Operate Blender safely through live MCP or a background process	Execution
Inspect, compare, repair, and approve Blender work	Critique

For new scene creation, read Design, Craft, Execution, and Critique. For a narrow edit, load only the affected craft guidance plus Execution and Critique. Worker engineering belongs in repository documentation, not the creative skill modules.

Shared Invariants#

Inspect the current file, units, objects, collections, linked libraries, and missing assets before editing. Do not assume an empty scene.
Turn ambiguous visual direction into observable form, material, composition, light, motion, and delivery decisions. Ask only when the missing choice would materially change the result.
Work from primary silhouette and proportion toward secondary structure, materials, lighting, and detail. Do not use polish to hide a weak blockout.
Preserve existing work outside the declared scope. Save a new checkpoint before destructive, broad, or difficult-to-reverse changes.
Use stable semantic names and explicit units. Read transforms in the correct coordinate space and inspect evaluated geometry when modifiers matter.
Use Blender Python as a normal authoring tool for repeatable scene work. Review scripts before execution and keep them within the approved scene, asset, and file scope. Use typed operations when they fit an inspection or edit.
Do not install add-ons or packages, download external assets, publish a port, or access unrelated local files without separate authorization.
Review actual renders and the final editable or exported artifact. Object counts, successful commands, hashes, and valid files do not prove visual quality.

Production Loop#

scene and delivery contract
  -> inspect source and save checkpoint
  -> block out scale, silhouette, camera, and value structure
  -> refine forms, materials, lighting, motion, and detail
  -> save .blend and create required derivatives
  -> inspect deterministic facts and opened visual evidence
  -> repair the smallest coherent source-level cause
  -> regenerate and re-review the changed artifacts
  -> hand off reviewed source, derivatives, and evidence

Use inexpensive preview renders during iteration. Spend on final samples, simulation, or long frame ranges only after the relevant scene decisions pass.

Completion#

Complete work includes the final .blend, authoring scripts and assets, required derivatives, exact Blender and execution versions, input and output hashes, and evidence for every required view or time range. Reopen the saved .blend; fresh-import exported formats when downstream behavior matters. Bind the delivery to the exact reviewed revision and its stated revision authority.

The bundled CLI is a macOS-only local runner for reviewed scripts. Its successful execution report is not visual approval or a hosted review receipt. The optional scripts/moonsail.py connects local runs to Moonsail Jobs, immutable files, and Studio repair history. Cloud execution, cloud isolation, and billing remain out of scope. A local agent must write and review the script before execution.

Report a blocked or degraded result when Blender is unavailable, source assets are missing, execution is interrupted, the required modality cannot be inspected, or a material visual or technical defect remains.