How to Make Viral Motion Graphics With AI With 0$ (Turned it into a Skill)
This video breaks down how Claude can orchestrate code-generated motion graphics, locally generated music and sound effects, and iterative visual critique without paid media APIs. Comparing three attempts, it shows that strong results come from a prepared framework, explicit creative constraints, a story-driven multi-role brief, and repeated grading and revision rather than a supposedly magical one-shot prompt.
Jad M.H | AI Automation16 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 Jad M.H | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to direct an AI through a reproducible, local motion-graphics workflow that integrates story, animation, sound, constraints, rendering, and iterative critique.
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.
1,905 cleaned transcript words reviewed across 549 timed caption segments.
Thesis
How to Make Viral Motion Graphics With AI With 0$ (Turned it into a Skill) teaches a practical coding-agent workflow move: This video breaks down how Claude can orchestrate code-generated motion graphics, locally generated music and sound effects, and iterative visual critique without paid media APIs. Comparing three attempts, it shows that strong results come from a prepared framework, explicit creative constraints, a story-driven multi-role brief, and repeated grading and revision rather than a supposedly magical one-shot prompt.
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:19
Setup Beats One-Shot
“with Claude to test it out. The first one from a simple prompt, second one with a bit better. I didn't think AI could do this yet, and today I'll show you all three exactly what changed between...”
Viral motion-graphics claims often hide long prompts, examples, skills, frameworks, and API setup; the speaker cites the prompt as only a small part of the finished result. His progression from a generic reel to a story-driven piece demonstrates that reusable process knowledge matters more than a short command. Turn a one-line video idea into a production brief that names the story, visual rules, sound requirements, forbidden defaults, and review loop.
5:31
Render Video From Code
“prompt or is it just a trust me, bro situation here? Harik, who works on Claude code at Anthropic, answered on one tweet. The post, Claude one shot this prompt, 10,000 characters plus skill examples and API keys.”
Claude does not directly output an MP4; it writes a coded web page that defines each frame, a browser captures the frames, and FFmpeg assembles them into video. Starting from the open-source Hyperframes framework avoids rebuilding the rendering setup and keeps colors, timing, and other details editable in code. Diagram the pipeline from coded scene to browser screenshots to FFmpeg output, then identify one visual property you would revise and re-render.
11:03
Direct A Crew
“story in this. For video one and two, I gave Claude a task. For video three, I gave it a crew. The prompt starts with you're a director, writer, animator, composer, sound designer, and a render engineer. And...”
The strongest attempt assigns Claude the roles of director, writer, animator, composer, sound designer, and render engineer, then gives it an emotional story rather than merely a task. It reviews contact-sheet screenshots, scores story, composition, motion, typography, and music sync, fixes the three weakest issues, and repeats until every shot scores at least eight. Create a five-criterion scorecard for a short sequence, grade one frame from every shot, and revise the three lowest-scoring problems before rendering again.
01
Inspect context
Start with this video's job: This video breaks down how Claude can orchestrate code-generated motion graphics, locally generated music and sound effects, and iterative visual critique without paid media APIs. Comparing three attempts, it shows that strong results come from a prepared framework, explicit creative constraints, a story-driven multi-role brief, and repeated grading and revision rather than a supposedly magical one-shot prompt. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:19, where the video says: “with Claude to test it out. The first one from a simple prompt, second one with a bit better. I didn't think AI could do this yet, and today I'll show you all three exactly what changed between...”
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 5:31, where the video says: “prompt or is it just a trust me, bro situation here? Harik, who works on Claude code at Anthropic, answered on one tweet. The post, Claude one shot this prompt, 10,000 characters plus skill examples and API keys.”
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: This video breaks down how Claude can orchestrate code-generated motion graphics, locally generated music and sound effects, and iterative visual critique without paid media APIs. Comparing three attempts, it shows that strong results come from a prepared framework, explicit creative constraints, a story-driven multi-role brief, and repeated grading and revision rather than a supposedly magical one-shot prompt.
02
Explain the practical stakes without hype: New playlist item from Jad M.H | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Brief -> Source material -> Generation -> Selection -> Edit -> Taste review -> Reusable recipe sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A creative production board with source inputs, prompt recipe, selection criteria, edit pass, and taste-review checkpoints.
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: How to Make Viral Motion Graphics With AI With 0$ (Turned it into a Skill)
- URL: https://www.youtube.com/watch?v=zke3bTtvmLo
- Topic: Creative Automation
- My current learning frame: Produce a 10–16 second coded motion graphic from a story brief, add locally generated music and programmatic sound effects, render it through browser frames and FFmpeg, and complete one scored critique-and-revision cycle.
- Why this matters: New playlist item from Jad M.H | AI Automation; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:19 / Evidence 1: "with Claude to test it out. The first one from a simple prompt, second one with a bit better. I didn't think AI could do this yet, and today I'll show you all three exactly what changed between..."
- 2:18 / Evidence 2: "Now, I made Opus 5.5 in less than 30 minutes, which I also did in less than 30 minutes. >> And this one is actually crazy. It's from Dolmolt. He posted it. I spoke to my computer for..."
- 5:31 / Evidence 3: "prompt or is it just a trust me, bro situation here? Harik, who works on Claude code at Anthropic, answered on one tweet. The post, Claude one shot this prompt, 10,000 characters plus skill examples and API keys."
- 7:03 / Evidence 4: "know? Because if you don't give Claude a framework, he usually builds everything from scratch. Every single time it starts from a setup that already works. All right. So, here's the first video. It's a simple prompt. I..."
- 8:41 / Evidence 5: "So, I found a music model called Ace Step 1.5. It's free. It's open source, and it runs on my laptop. And my laptop is not a beast. It's a MacBook Air, 16 gigs of RAM. So, for..."
- 11:03 / Evidence 6: "story in this. For video one and two, I gave Claude a task. For video three, I gave it a crew. The prompt starts with you're a director, writer, animator, composer, sound designer, and a render engineer. And..."
- 14:20 / Evidence 7: "10,000 character prompts. The structure is already in there. The story, the steps, can't skip the music, the sound effects, the critical loop, and all the lessons that I have to learn. I damaged definitely my computer to..."
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 "How to Make Viral Motion Graphics With AI With 0$ (Turned it into a Skill)", 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.
Why are impressive AI motion graphics rarely the product of only a simple one-shot prompt?
How does Claude's text output become an MP4 in the demonstrated workflow?
What iterative review loop improved the third video's shots?
Source shelf
Use the video as a doorway, then verify with primary sources.
