Blender Production

Produce editable 3D work whose shape, appearance, motion, and delivery are supported by actual inspection. Use Blender Python for repeatable construction and checks, MCP for live inspection and targeted operations, and the native UI for the experience the user receives. MCP is a transport; realism comes from the scene and renderer.

Apply this workflow to buildings, products, environments, characters, abstract/stylized scenes, and animation. Select domain-specific modeling techniques from the brief. Do not turn every task into photoreal architecture. A skill cannot guarantee a perfect reconstruction from incomplete references: define observable acceptance criteria and report what was verified.

Establish the task and owned session

Read the brief, current status, accepted work, and latest user scope. Identify the deliverable: editable scene, stills, film, interactive experience, or export. A request to wrap up or show current work ends unsolicited refinement; render and package the accepted state.

Before a live mutation, identify Blender version/build, PID, exact open file, scene, engine, and active job. Multiple windows/MCP connections may belong to different projects. A tool connection is not proof of the correct target. Keep one writer per scene and one clear source checkpoint.

Read control.md for API/MCP selection, scoped session control, dependency failures, and recovery. Run probe_scene.py inside Blender for bounded scene/asset/device diagnostics; ordinary Python generally lacks bpy.

Translate the brief into checks

Select criteria with tolerances based on sources and intended camera distance: