3D & Animation Workflows

Turn a locked 3D brief plus chosen recipe into a measurable acceptance checklist with evidence hooks.

Provide a fallback strategy when an asset is unavailable, over-budget, license-blocked, or style-incompatible — without halting the recipe.

Plan an internal asset library structure (folders, naming, metadata, license tracking, version control) so future recipes find and reuse assets reliably.

Verify license compliance for downloaded 3D assets, textures, HDRIs, fonts before scene build or export.

Verify chosen assets share visual style (realism, detail, color treatment) before scene build; flag style drift between assets early.

Plan the asset acquisition strategy (procedural, library, generative, photogrammetry) for a Blender scene without installing or executing. Use after the brief, before scene planning.

Define explicit per-stage gates and acceptance checklists before any modeling, render, or export work — work only proceeds gate by gate.

Provide detailed composition and camera planning for product hero outputs.

Build detailed lighting and material direction with portability and caveat handling for Blender/web-3D outputs.

Break a complex / over-scoped Blender intent into 2-5 smaller recipes that each have a clean stop condition, brief, and handoff.

Apply multi-category readiness gates with pass/warn/fail and evidence-bound verdicts.

Detect mid-recipe scope creep and push back constructively before the recipe drifts; require explicit user agreement before scope expansion.

Define explicit "done" conditions for a Blender recipe before starting work, so the agent stops at the right point instead of drifting into endless polish.

Blender skills pack for non-Blender users. Use for scene planning, runtime readiness, render/export/GLB evidence, Claude Connect guidance, and plain-language handoff across multiple AI agents.

Claude Desktop-facing BlendOps router skill for planning, runtime readiness, evidence truth, and non-Blender-user outputs using bundled references.

Help users and agents choose the next safe BlendOps action across skills, docs, runtime readiness, evals, packaging, and Draft v0 release boundaries.

Plan a character-portrait scene (subject, pose, expression, wardrobe, framing, lighting, background) before any modeling or render attempt.

Plan headless blender --background export or render jobs when MCP chat control is a poor fit; cite upstream Blender CLI docs only.

Pick the right color management config (sRGB / Filmic / ACEScg / Standard) per output context before render, so colors travel correctly to the consumer.

Validate camera framing, subject placement, headroom/lead-room, and visual hierarchy against the scene brief before render.

Pick Cycles or Eevee (or Eevee Next / Workbench) for a render based on quality bar, time budget, and feature requirements (caustics, subsurface, etc.).

Plan a wide environment / establishing-shot scene (locale, time of day, weather, focal subject, depth, atmosphere) before any modeling or render attempt.

Document GLB animation contract (skeletal vs morph, FPS, looping, root motion, blend transitions) with truthful caveats for web playback.

Set explicit triangle / texture / draw-call / file-size / animation budgets for GLB targeted at mobile-web before any export decision.