Amir Mushich shares a Claude Code prompt for procedural Blender product films
Amir Mushich published a reusable Claude Code prompt to build product films in Blender without video models. His example took nine revisions, about five hours of agent work and four hours of rendering.

TL;DR
- Claude Code and Blender produced a code-built product film with no video models, according to AmirMushich's production breakdown.
- The reusable prompt specifies a 9.6-second vertical loop controlled by one
OBJECTvariable, as described in the full brief. - Finishing the example took nine revisions, AmirMushich said, and he still calls the sound “very weak.”
The published prompt gives the opening 12 frames four times the rendering samples of the rest and reserves red for the alarm. It also specifies Khronos PBR Neutral, a color transform designed for product photography, and a CSV cue sheet for replacing the synthesized score.
A code-built product film
Amir Mushich’s template is a miniature production bible, assigning Claude both technical-director and art-director duties for a Blender film.
Three material passes
Claude is asked to inventory 25-50 real parts, each with a material and an “explode vector,” in the build instructions. Geometry is specified as signed-distance functions in NumPy, meshed with surface nets, with Blender handling assembly and materials.
Each part switches among three passes:
- Solid: the finished material.
- Glass: three RGB glass shaders with different refractive indices, producing inexpensive dispersion.
- Field: a visualization of one object-specific quantity, such as heat, pressure or vibration.
The field shader uses procedural noise, with one conversion function keeping the labels, legend and inset readings consistent. Mushich described the film as entertainment for social media when challenged about its technical accuracy.
Contact sheets and two-pixel seams
Every frame must be computed independently from its frame number, with seeded randomness, so individual frames can be rerendered without rebuilding the sequence. The checkpoints in the production brief make the review process explicit:
- Preflight: check Blender 4.2+, Python 3.10+ and ffmpeg, then time a 540×960 test frame to estimate the full render.
- Approval: show contact sheets at marked checkpoints, sampling every sixth frame and adding 100% crops where detail matters.
- Motion checks: measure projected part positions across act boundaries. The requested tolerance is two pixels, including the bounding-box match between the last and first frames.
- Flash gate: allow at most three full-field luminance flips in any second.
- Delivery: produce social, master and clean edits, audio stems, five 4K stills and a cover image.
The agent must ask before installing software, downloading fonts or spending money. Only one Blender render may run on the GPU at a time.
The RTX 4070 production bill
Mushich counted nine revisions in his original post. His later accounting listed:
- Approximately 575,000 output tokens.
- Seven versions, including four full rerenders.
- About five hours of agent work.
- About four hours of Blender Cycles rendering on an RTX 4070 Laptop GPU.
In his cost estimate, Mushich quoted roughly $60 at API rates and about $3 for Fable edits. He said he was working on a $100-per-month subscription, so the API estimate was not his actual bill.
Synthesized sound
Audio is specified as NumPy synthesis driven by the animation timeline, with three layers:
- Mechanics: impacts, ejection sounds, seating clicks and the lock.
- Machine voice: the object’s working sound, with pitch following its state curve.
- Data: log blips and ticks, approximately 18 dB below the other layers.
Mushich’s criticism of the finished sound came despite that detailed specification. He said he was building a Claude plugin and described the plan as an “agentic-native” synth.
The free prompt and Shred template
Mushich’s version-two post links to his Telegram channel and presents reuse as pasting the prompt into Claude and changing the OBJECT variable.
He says Opus at Medium or High is sufficient in a follow-up, because the prompt already contains the direction details.
His earlier free-template post links to Shred on GitHub, a separate Blender kit that turns a printed poster into an eight-second paper-shredding loop at 1080×1920 and 60 fps. Its motion, camera and edit are fixed; the repository includes AGENTS.md instructions for customization through coding agents.
Shred’s code is GPL-3.0, and its README explicitly permits commercial use of the finished videos.