Full text of the Opus "motion director" prompt that films in code

minchoi · x · 2026-10-17

This reply contains the full "motion director" prompt behind the viral Opus demo, where Claude designs, animates, scores and QA-checks a finished film entirely in code.

Key structure:

brief: blank lines are decided by the model and justified in brief.md; covers mode, subject, viewer, length (15s/30s, 16:9 & 9:16), frame rate, style and audio.
modes: showreel builds around one transforming idea; product features real UI as live components; launch-story follows a narrative arc; explainer traces one cause-and-effect chain.
crafts: 10 editing rules — one object/word carries the film and sits center-frame, hard cuts only on beats, audio leads, visible results every second, no filler transitions or stock footage.
audio: music prompts hit every cut, voices peak at -1 LUFS, silences keep room tone.
build: everything renders frame-by-frame in code on one timeline, checkpoints every 3–5 beats, API keys in env vars.
critic loop: after each render a fresh critic subagent that never saw the build samples frames and scores 0–100; below 85 triggers re-renders until scores stabilize at 90+, tracked in a ledger.
quality bar: exact duration, 60fps caption animation, frame contrast ≥8:1, loudness -14 LUFS, zero invented facts.

Original post →

Full text of the Opus "motion director" prompt that films in code

More from coding & agent