Editing videos with Claude and Remotion: how I organise my workflow

I show a collection of reusable assets: graphics, comparisons, numbers, browser scenes, terminals and calls to action. I also keep ELITE IA's typography, colours and identity in mind. The aim is for the pieces to belong to the same brand even when the message or format changes.

That library takes preparation. In the recording, I explain that I built the project over several weeks, collecting references and refining instructions. Time saved on later edits comes from that accumulated work; it does not simply appear after writing the first request.

I work in Visual Studio Code with Claude and use Remotion for the programmatic part of the video. I show a project instruction file containing the context the assistant needs: which style to follow, which assets exist and how to work with them.

In my setup, input videos are inside public and results are exported to an output folder. That is a choice for this project, not a requirement for every application. The transferable idea is to separate originals from exports so that you can compare results and repeat a test.

The demonstration compares raw footage with its edited version. Motion graphics, music and sound effects are added. I also show a test that already had visual editing but still needed better audio: producing an output does not mean the work is finished.

At that point, I preferred to supply some cuts myself because I stumble when speaking and wanted to control which parts to keep. It is a practical quality decision. Delegating part of the process lets you focus your review on pacing, message clarity and errors that distract viewers most.

In the recording, I use Freesound as a source of effects and explain that I look for variety so that every transition does not sound the same. Before using an asset commercially, check that file's specific licence and keep the required attribution.

I also compare horizontal, vertical and square pieces. Adapting an ad involves more than cropping the canvas: you need to check text sizes, positioning and what remains visible. A shared library helps, but every export needs to be watched in its final format.

In the video, I describe working on more than forty pieces in roughly five hours. That is the result I report for my own workflow, with prior preparation and specific materials. It is not a universal performance benchmark and does not necessarily include the time spent building the system.

To try a similar idea, start with one piece: keep the original, define a visual reference and compare the complete result, including audio. Then note which instructions recur. That repetition will show you what is worth turning into a reusable template.