AI Motion Graphics
The reel is a program, not a file, so I re-render it when the work moves on.
The question I was chasing
Why should a brand showreel be a finished file at all, rather than something I can re-render from code?
A sizzle reel is frozen the moment it is exported. Rolling Waves keeps shipping, so the day something new lands the reel needs another pass in After Effects just to stay current.
Remotion renders video from React code, so the reel can be a codebase instead: versioned, built from reusable pieces, and re-rendered whenever the work moves on. The open question was whether that survives contact with a real brand film.
The constraints
Build the whole thing from prompts and AI-generated assets, with no traditional design or editing tools in the loop. The composition had to stay flexible, so updating it later means editing those pieces, not re-cutting a timeline. And it still had to land as a real brand reel: motion and pacing that sell the work, not a tech demo that only impresses other engineers.
The decisions that mattered
I built the reel in Remotion so the video is made of React components and stays maintainable code rather than a finished export you cannot update cleanly.
I generated every asset with prompts, so the reel is prompts and code end to end, with no design tools in the loop. The cost is real. A generated asset is the one the model gave me, and the fix for a near-miss is another prompt rather than a nudge in an editor.
I structured the film as reusable pieces per beat, so adding a new venture is a code change, not a from-scratch re-edit.
Built with: Remotion, Claude Code, React
Where it landed
The reel is finished and it plays at the top of this page.
Code makes re-rendering cheap. It does not make it automatic. If I stop running it, the reel goes stale exactly like a file would.
Part of the Rolling Waves work archive.