3D & Animation Workflows

Blender to web export workflows for 3D models and animations. Use this skill when exporting Blender models to glTF for web, optimizing 3D assets for Three.js or Babylon.js, batch processing models with Python scripts, automating Blender workflows, or creating web-ready 3D pipelines. Triggers on tasks involving Blender glTF export, bpy scripting, 3D asset optimization, model compression, texture baking, or Blender automation. Exports models for threejs-webgl, react-three-fiber, and babylonjs-engine skills.

Turn a reference image into a quality-gated procedural Three.js model, or extract a scene screenshot into a reference-matched blockout. Use for image-to-3D reconstruction, detail-accurate object rebuilds, stylized characters, sculpt specs, and, together with threejs-scene-authoring, hand-authored level/greybox composition from a gameplay image.

Open every task by writing a kickoff brief — the task restated exactly as understood, the concrete work that will follow, and the explicit list of skills to load before the first edit. Use at the start of any request that will change files, and again whenever the scope, the understanding, or the chosen approach changes mid-task.

Drive Blender from natural language. Converts plain-English requests ("model a sword and render it with cinematic lighting", "make this glass look frosted", "set up three-point lighting", "export this scene as glTF for the web") into Blender Python code executed via the Blender MCP server. Acts as the orchestrator that picks and chain-loads specialised sub-skills (blender-modeling, blender-materials, blender-lighting, blender-cameras, blender-rendering, blender-animation, blender-export, wireframe-to-3d, blender-pro-workflow, blender-skill-harmonizer, quality-refinement-autoloop). Use this skill whenever the user wants Claude to do anything in Blender, including creating geometry, applying materials, lighting a scene, framing a camera, rendering, animating, or exporting. Make sure to invoke this skill even if the user does not say "Blender" — also covers requests like "create a 3D model of...", "render this...", "make a glTF from...", "set up a scene with...", or any 3D-creation task. Requires the Blender MCP addon (ahujasid/blender-mcp) running on port 9876.

Keep Three.js / react-three-fiber draw calls low in this project. Use whenever adding repeated 3D objects (props, tiles, foliage, blocks, enemies, particles, greybox/blockout geometry) or creating materials. Enforces two rules: (1) batch repeated meshes with InstancedMesh (drei / ), never one per object; (2) define every material and geometry ONCE in the shared registry and reuse it — tint per-instance with instance color — never new THREE.Material() / new THREE.Geometry() inline. Shared assets register with @vibegameengine/shader-warmup's central warmup service. Trigger on: "too many draw calls", "scene is slow", "add N of these", "spawn", "props", "instancing", "material", "shader warmup", "shader stutter", "warmup splash", "ShaderWarmupRegistry", high draw-call count in r3f-perf.

Design coherent, inspectable scalar and vector fields for Three.js materials, geometry, terrain, biomes, wetness, displacement, and VFX. Use when several visual channels must share a physical or artistic cause instead of stacking unrelated noise.