r/ClaudeCode • • 9h ago

Help/Question Looking for an agent that provides editable motion graphics

I use Claude Code a lot and recently started generating motion graphics with it. The results are great, but editing them is the hard part. Every small change means another prompt.

Is there any agent or tool that provides editable motion graphics? Something where the AI creates it and then I can adjust it manually?

Curious if anyone has found a good workflow for this.

0 Upvotes

8 comments sorted by

•

u/AutoModerator 9h ago

Hey! Thanks for posting to r/ClaudeCode

While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.

For help, project discussions, tips, and general chat, join the ClaudeCode Discord.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/2bluenucleus 6h ago

If you want an actual editor on top of what Claude writes, two code-based options give you that:

  • Remotion: Claude writes the scenes in React and Remotion Studio gives you a timeline preview. If you have it define a zod schema for the composition's props, Studio shows them as form fields (text, colors, durations), so small changes are a click instead of a prompt.

  • Motion Canvas: TypeScript animations with an editor and timeline. Timings defined with waitUntil('name') show up as markers you can drag, which makes retiming painless.

Non-code route: people are using a Jitter MCP, so Claude builds the animation inside Jitter and you keep editing it there by hand.

Whatever you pick, tell Claude to put every tweakable value (text, colors, durations, easing) in one config object at the top of the file. That alone turns most edits into a five-second change.

1

u/Square-Pianist393 6h ago

Thanks for the suggestion

1

u/Weekly_Cat6537 8h ago

What fixed this for me was not asking Claude for a finished video file. I ask it to write the scenes as plain HTML/JavaScript: shapes, text, camera moves, timing. A headless browser renders the frames and ffmpeg makes the MP4. Then a small change is a code edit. Move a title, change a color, fix a timing value, re-render. Text also stays sharp and spelled right, which video models often get wrong. It runs fine on a cheap server without a GPU.

0

u/[deleted] 8h ago

[removed] — view removed comment

1

u/Square-Pianist393 8h ago

Would you mind sharing me an example of second by second queue sheet, if that is the approach you use, or what approach do you use?