Create and revise a code-based promo video with Remotion and Claude Code

Create the project and install the skill

Luke demonstrates Remotion with Claude Code and reports generating a SaaS promotional video in about 16 minutes. That is the timing of his example, not a guaranteed turnaround. The retained resources are https://remotion.dev, https://remotion.dev/prompts and https://www.remotion.dev/ for the project and prompting references.

1. npx create-video@latest
2. npx skills add remotion-dev/skills

Give Claude the animation instructions

Launch Claude normally with permission checks retained, then use /skills to inspect the available skill. The source supplies the two instructions reproduced below: one establishes detailed prompting and use of the Remotion skill, and the other separates animation subdirectories while retaining a shared root context.

Animations are created by simple prompts, so make sure to use a very detailed prompt and ask Claude to use the Remotion skill. do not do anything yet, just acknowledge this.

Ask Claude to create a separate subdirectory for each animation to keep things clean. So you will have one root folder that shouldn't have any animations and several sub-folders for each animation. That way, you keep having the context necessary for Claude not to repeat the same mistakes when making another animation. (again, do not do anything yet, just acknowledge this)

1. Describe the actual product, supplied assets, scene order, on-screen text and intended duration before asking for the animation. Keep claims and screenshots aligned with the product you are presenting.
2. Ask Claude to acknowledge the saved instructions first, then request one specific animation in its own subdirectory. Inspect the created structure and preview before expanding to a full sequence.

Inspect the edit and render the selected version

The video moves to the Remotion editor at 10:01, rendering at 10:40 and output improvements at 11:25. A working composition preview and a finished video file are separate checkpoints. Keep the source project with the export so that text, timing and layout remain revisable.

1. Review the sequence in the editor, checking readable text, product accuracy, scene transitions and the opening and ending. Request a targeted change to a visible problem rather than regenerating everything without preserving the baseline.
2. Render the selected version using the project’s supported route and watch the actual exported file. Compare its timing, framing and complete scene sequence with the preview and keep unresolved issues in the next revision brief.

The takeaway

Save the project structure and instructions with the finished export. A useful AI-generated promo is one you can inspect, revise and render consistently.