A six-step workflow for making videos with Claude and Remotion
The author shares a six-step method for making videos by having Claude write Remotion code: reference, data, story, motion, direction and shipping, to avoid generic-looking results.
my Claude videos used to look generic clean, smooth and completely forgettable the problem wasn’t the model. I was typing “make me a video about X” and hoping for the best now every video goes through the same 6 steps: > reference I show Claude a video I actually like. it breaks down why it works: the pacing, where the first motion lands, how the text comes in, the cut rhythm this one step fixes most of the generic look > data real numbers before anything moves. every figure has a source a wrong number in a beautiful animation is still wrong, it just looks more convincing > story one point, one hero number, three beats written before any motion, so the video is about something > motion Claude writes the animation as code with Remotion and a motion-design skill no video model, so every word, number and timing stays editable > direct I don’t re-prompt. I just say what’s off: “title is a beat late” one line changes “draw the line slower” one line changes nothing else breaks ship it renders stills, checks them against the reference and the data nothing goes out until I approve it > most people jump straight to step 4 and wonder why it looks like everyone else’s the real difference is step 1 and step 5: copy what works, then direct instead of re-rolling full setup, the prompt and the 10 open-source skills are in the article
This post quotes another post: x.com/francescoinweb3/status/2108882188624121896