I Made Vox-Style Motion Graphics Using Only Claude Code & Remotion
MoSidd recreates a 47-second Vox-style explainer (a US-Iran peace deal story) using only Claude Code and Remotion — from a script-as-timeline storyboard and Magnific/Higgsfield MCP connectors, through three-layer scenes with halftone cutouts animated by plain-English prompts, to voiceover sync with ElevenLabs and a final 1080p render.
MoSidd | AI Made Easy13 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, route, plan, edit, verify, summarize, and decide what should be automated next.
New playlist item from MoSidd | AI Made Easy; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to produce broadcast-style motion graphics without After Effects or coding knowledge by combining a locked visual system, MCP-connected image tools, and plain-English animation prompts to Claude Code driving Remotion.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect context
02Route tool
03Plan work
04Edit safely
05Verify behavior
06Report next step
Deep lesson
Turn this video into working knowledge.
2,552 cleaned transcript words reviewed across 706 timed caption segments.
Thesis
I Made Vox-Style Motion Graphics Using Only Claude Code & Remotion teaches a practical coding-agent workflow move: MoSidd recreates a 47-second Vox-style explainer (a US-Iran peace deal story) using only Claude Code and Remotion — from a script-as-timeline storyboard and Magnific/Higgsfield MCP connectors, through three-layer scenes with halftone cutouts animated by plain-English prompts, to voiceover sync with ElevenLabs and a final 1080p render.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:00
Script is the timeline
“I made this entire Vox style explainer video using only Claude code and Remotion. >> The US and Iran are signing a peace deal. But the downfall of the American Empire has already begun. And it started when...”
The storyboard starts with the voiceover script laid out in a table where each narration beat maps to a visual, with columns for foreground and midground assets plus the image-generation prompts for each. Before touching tools, you lock a visual system: one common background across all scenes, the same fonts and accent palette, with only the midground and foreground cutouts changing. Take a 45-second script on any topic, put it in a table with one row per narration beat, and fill in columns for foreground asset, midground asset, and the image prompt you would use for each.
4:25
Layers, MCPs, halftones
“folder over here. Select folder and then just run that prompt again. So, while the Remotion project is being set up, I'll show you how this worked. Now, the reason why we have a locked background is because...”
Magnific and Higgsfield are wired in as MCP connectors so Claude Code can fetch image assets directly instead of manual downloads, and the project uses one folder per scene, each holding its cutouts plus the shared static background that makes everything feel like one continuous shot. Cutouts get a black-and-white halftone treatment via a Claude Code prompt for that papery Vox magazine feel, and animation is 'with intent' — plain English like 'spring the White House up first, stagger the characters, add an offset red marker stroke' rather than writing spring/interpolate calls yourself. Add one image-generation MCP connector to Claude Code, then prompt it to convert a transparent PNG cutout to a black-and-white halftone and spring-animate it into a Remotion scene using only plain-English instructions.
11:43
Assemble, sync, render
“deal. >> Okay. So, once you have this, you can download it and put it into the same folder, and you can come back to your Claude code, and you can ask Claude code to sync your entire...”
After fine-tuning each scene with prop controls in Remotion Studio (scale and XY sliders whose values you must save), Claude Code stitches all scenes into a master sequence timed to the narration, and a voiceover generated in ElevenLabs is embedded so each scene starts and ends on its own narration line. Jerky audio while scrubbing in Remotion Studio is normal and cleans up on render — the final ask is simply a 1080p MP4 with music and voiceover mixed in, or a bare composition if you prefer finishing audio in Premiere. Generate a short voiceover in a text-to-speech tool, drop it into a two-scene Remotion project, and prompt Claude Code to sequence the scenes so each starts and ends on its own narration line, then render to MP4.
01
Inspect context
Start with this video's job: MoSidd recreates a 47-second Vox-style explainer (a US-Iran peace deal story) using only Claude Code and Remotion — from a script-as-timeline storyboard and Magnific/Higgsfield MCP connectors, through three-layer scenes with halftone cutouts animated by plain-English prompts, to voiceover sync with ElevenLabs and a final 1080p render. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “I made this entire Vox style explainer video using only Claude code and Remotion. >> The US and Iran are signing a peace deal. But the downfall of the American Empire has already begun. And it started when...”
02
Route tool
Use "Route tool" to locate the part of the coding-agent workflow mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 4:25, where the video says: “folder over here. Select folder and then just run that prompt again. So, while the Remotion project is being set up, I'll show you how this worked. Now, the reason why we have a locked background is because...”
03
Plan work
Turn "Plan work" into the reusable artifact for this lesson: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal. This is where watching becomes something you can inspect and reuse.
04
Edit safely
Use "Edit safely" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Verify behavior
Use "Verify behavior" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Report next step
Use "Report next step" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
Example
Coding-agent workflow proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the coding-agent workflow pattern.
Example
Teach-back module
Transform the lesson into a definition, a Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
choosing tools by hype
losing context across agents
letting parallel sessions become invisible
Letting the lesson drift into generic Codex vs Claude comparison.
Letting the lesson drift into feature lists without task routing.
Letting the lesson drift into claims that ignore limits or recovery.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: MoSidd recreates a 47-second Vox-style explainer (a US-Iran peace deal story) using only Claude Code and Remotion — from a script-as-timeline storyboard and Magnific/Higgsfield MCP connectors, through three-layer scenes with halftone cutouts animated by plain-English prompts, to voiceover sync with ElevenLabs and a final 1080p render.
02
Explain the practical stakes without hype: New playlist item from MoSidd | AI Made Easy; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: I Made Vox-Style Motion Graphics Using Only Claude Code & Remotion
- URL: https://www.youtube.com/watch?v=7wuYBfE131U
- Topic: Creative Automation
- My current learning frame: Build a three-scene Vox-style micro-explainer end to end: table out the script beats, lock one shared background with halftone cutouts, animate each scene with plain-English spring prompts, then sync an ElevenLabs voiceover and render a 1080p MP4 from Claude Code.
- Why this matters: New playlist item from MoSidd | AI Made Easy; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "I made this entire Vox style explainer video using only Claude code and Remotion. >> The US and Iran are signing a peace deal. But the downfall of the American Empire has already begun. And it started when..."
- 2:49 / Evidence 2: "connectors. Now, if you want to add a new connector, what you can essentially do is you can add a custom connector, and then you can get the MCP server address for Magnific, post it in here. And..."
- 4:25 / Evidence 3: "folder over here. Select folder and then just run that prompt again. So, while the Remotion project is being set up, I'll show you how this worked. Now, the reason why we have a locked background is because..."
- 7:07 / Evidence 4: "Claude Code is still running, setting up the Remotion dependencies. Okay. So, now what it's done is it set up the first scene with our characters in the midground and White House in the foreground. So, I'm just..."
- 8:44 / Evidence 5: "1.4 and you'll see Donald Trump just becomes a bit bigger over there. So, I can change the XY positions. And what you need to do, guys, is also you need to save these numbers as well. So,..."
- 11:43 / Evidence 6: "deal. >> Okay. So, once you have this, you can download it and put it into the same folder, and you can come back to your Claude code, and you can ask Claude code to sync your entire..."
Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
- answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
- 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
- a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
- one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "I Made Vox-Style Motion Graphics Using Only Claude Code & Remotion", not a generic Creative Automation essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
A reusable artifact with a done signal and one verification step.03
Coding-agent workflow teach-back card
Explain the coding-agent workflow mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
What is the first step of the workflow, and what does 'locking a visual system' mean in this video?
What are the three layers of each scene, and why is the background kept static across all scenes?
How does the voiceover get synchronized with the scenes at the end of the workflow?
Source shelf
Use the video as a doorway, then verify with primary sources.
