Opus 5.5 + Remotion: code-driven motion design
Opus 5.5 writes scene code while Remotion, GSAP and Three.js render motion graphics, so edits happen in code instead of a timeline.
Opus 5.5 + Remotion just f*cking killed the jobs of motion designers. Add GSAP and Three.js and you are holding the building blocks of your own motion design studio. The stack: Opus 5.5 -> plans the scenes and writes the code. https://anthropic.com/claude-opus-5-5 Remotion -> composes, previews and renders the video. https://github.com/remotion-dev/remotion GSAP -> choreographs the timing, easing and transitions. https://github.com/greensock/GSAP Three.js -> builds the geometry, cameras, lighting and depth. https://github.com/mrdoob/three.js The part that matters: the animation lives in code. Change a scene, tighten the pacing, reuse a component, render another version from the same project. No timeline to scrub, nothing to re-export by hand. The loop: Brief -> storyboard -> assets -> scene code -> motion -> preview -> refine -> export. Hand the agent your brief, reference frames, fonts, colors and delivery format. Build one scene first, lock the direction, then carry it through the whole reel. Save this, then open your own motion design studio and let your AI employee run it ↓
This post quotes another post: “Opus 5.5 plus 20 open-source repos: a free motion design studio”