---
name: claude-3d-animation
description: Direct 3D animation for videos: decide when 3D is worth it, design 3D titles, device mockups, exploded UI, particle morphs and camera moves, and write deterministic three.js code. Use when the user asks for 3D animation, 3D titles, 3D video, three.js scenes or 3D product shots.
---

# 3D animation skill

3D is expensive attention. Spend it on two or three moments per film.

## When 3D earns its place
- The reveal (product name as a 3D title or particle morph).
- Showing the product physically (laptop opening, phone turning).
- Explaining structure (exploded UI layers, architecture).
Not for: body copy, every transition, or scenes that need to be read quickly.

## Shot vocabulary
3D extruded title · device mockup (laptop, phone) · exploded isometric UI · floating UI cloud with depth of field ·
particle morph (galaxy/sphere/vortex to text) · dotted globe with arcs · camera fly-through between panels.

## Look
- Materials: chrome and glass for premium, iridescent for playful tech, clay for friendly, neon for night/cyber.
- Lighting: a key, a fill and a rim; or a studio HDR environment. Avoid flat ambient-only light.
- Depth of field to separate the hero from the background; keep text layers in focus.

## Camera
- Slow push-ins (5 to 15% over the shot), gentle orbits (under 30 degrees), eased start and stop.
- One camera move per shot. Never shake text.

## Writing three.js yourself
- Drive every animation from a time value (`t` in seconds), not from `Date.now()` or frame deltas, so renders are deterministic.
- Use `renderer.toneMapping = THREE.ACESFilmicToneMapping` and sRGB output; set `setPixelRatio` explicitly for renders.
- Load models as glTF/GLB, dispose geometries, materials and textures when done.
- Keep particle counts proportional to output size; test a frame at 4K before a full render.

## Render with Claude Video (optional)
If the Claude Video MCP server is connected (tools: `guide`, `create_video`, `get_video`, `update_video`,
`edit_video_with_ai`, `preview_frame`, `render_video`, `get_job`):
1. Call `guide` once, then `create_video` with a brief (or a full VideoSpec as `spec`).
2. Check key moments with `preview_frame`, fix with `update_video` or `edit_video_with_ai`.
3. Only when it looks right, `render_video` and poll `get_job` for the MP4 link. Do not render drafts.
Setup: remote MCP server `claude-video`, URL `https://claudevideo.io/api/mcp`, header `Authorization: Bearer <API key>`.
