Create a finished 3-minute explanatory video about Software Engineering for students in class 4 of my Fractal Accelerator program. After watching, viewers should be able to understand, build, and maintain their own software projects, mainly consisting of a System of Record and Interfaces which rely on that System of Record. Build the animation in code using a suitable available stack. Deliver a playable browser preview, a 1920×1080 MP4, editable source, narration script, and SRT captions. Create the script, storyboard, diagrams, animation, and audio needed to finish the video. Start with a concrete question or situation. Develop one worked example through the video. Show the mechanism step by step, address the most likely misconception, and end with a concise recap. Design each scene around one explanatory job. Use motion to show a relationship, a change, or where to look. Give important diagrams time to settle. Keep labels stable and readable, use consistent colors for recurring concepts, and keep captions clear of diagrams. Avoid continuous decorative wobble, dense paragraphs, and generic title-card sequences. Use ElevenLabs for narration. Generate and check narration before final animation timing. Align key reveals with the spoken explanation. Keep music below speech and check technical-word pronunciation. State any unavailable tool or output dependency before relying on it. Inspect representative frames and every transition. Check factual accuracy, caption timing, pronunciation, label collisions, and the exported video's beginning and ending. Correct problems you find. Work through the final render and open the preview for review. Include the sources and any remaining limitations with the deliverables.
Software Engineering 101
Everything you build with AI is software, so here is a brief crash course on building good software. First, keep the truth in one System of Record. Second, make breaking and changing and experimenting with things cheap via Version Control -- aka. save points, and the ability to roll back.
Claude Code made all five videos from the prompts on this page. It wrote the scripts, voiced them with ElevenLabs, wrote the songs and made them in Suno, edited a webcam recording, and animated everything in Remotion. Copy the prompts and try your own, if you want.
Systems of Record
Every system should have one place where the truth lives, called the System of Record, and screens that read and change it, called interfaces.
What it covers
- One System of Record: the single official copy of your data
- Rules and access control via API
- Interfaces read and write that API
- The common mistake: an interface keeping its own copy
- Maintenance: interfaces are cheap to change, if you keep records up to date
- Migrations: changing the system of record
1 · The explainer
3 minutes · narrated with ElevenLabs · animated in Remotion
Then one more message, after watching the first cut:
- the interfaces connected to the system of record should actually be beautifully designed interfaces, not just abstract boxes the interfaces connected to the system of record should actually be beautifully designed interfaces, not just abstract boxes
2 · The music video
3½ minutes · song made in Suno · every reveal timed to the sung words
These prompts went into the same conversation, right after the explainer. Claude Code wrote the lyrics, drove Suno in the browser, then re-timed the explainer's animation to the vocals.
Can you produce high quality lyrics for this script as well and then use Suno to make that into a song? I have suno, so you should just be able to use the browser to do that.
Yes, now turn Version B (the 3:27 version) into a music video using your same graphic design process.
Read the lyrics
[Intro] (Is my cake ready yet?) [Verse 1] Phone buzzing on the counter: "Is my cake ready yet?" Maya checks her messages, "three o'clock," they said Then the spreadsheet says four, and the notebook says five Three places, three answers, and a customer outside [Pre-Chorus] When every copy's talking, nobody's right So pick one place and hold it tight [Chorus] Where does the truth live? In one place, just one One System of Record, when the arguing's done Screens can come and go, they can change their clothes But the record is what lasts, and everybody knows [Verse 2] Every order is a row: who, what, and when And a status moving forward, never back again Placed, then baking, ready, picked up out the door Only during opening hours, that's what rules are for There's one door to the data, call it the A-P-I Every change has to knock, break a rule? Goodbye [Pre-Chorus] When every copy's talking, nobody's right So pick one place and hold it tight [Chorus] Where does the truth live? In one place, just one One System of Record, when the arguing's done Screens can come and go, they can change their clothes But the record is what lasts, and everybody knows [Verse 3] The order form writes it, and a new row takes its place The kitchen screen reads it, there's flour on Maya's face She taps "ready," the status flips, a phone lights up across town Three different interfaces, one record holding it down [Bridge] Here's the trap that almost everybody falls in first: Let the kitchen keep its own copy, and it only makes it worse Sam moves pickup four to six, the record knows it's true But the kitchen's copy still says four, now you've got two (Two answers again) Don't own the data, just show what's real Reload when it changes, that's the deal [Verse 4] Screens are cheap to change, so redesign the kitchen board Add a weekly sales report, leave the rest like before But the record is expensive, everything is built on top So when Maya needs allergy notes, she doesn't hack and chop She writes a migration, just a little saved script Adds a brand new column, then updates every screen that needs it [Final Chorus] Where does the truth live? In one place, just one One System of Record, when the arguing's done Screens can come and go, they can change their clothes But the record is what lasts, and everybody knows [Outro] One: decide where the truth lives Two: guard it with rules behind one door Three: build your screens through that door Four: change the record with care Interfaces come and go The record is what lasts
3 · The talking-head version
3 minutes · one webcam take · cut out, remastered, and re-timed by Claude Code
The last version swaps the AI voice for a real one. Claude Code wrote a script to read aloud. After one take on a laptop webcam, it trimmed the recording, cleaned up the audio, cut the speaker out of the room behind them, and rebuilt the animation around their words.
Can you write a script for me to read, so this becomes a talking head video, and then open that up in our markdown editor? I'll record myself talking, then you'll put me in there, edit/crop my head, and re-build/re-edit the video around my narration, since I think it will feel much more personal than the AI voice we chose.
Can you take the most recent video in ~/my-recordings (should be 3:01 or so) and edit, trim, improve/re-master the audio, cut out my talking head and remove it from the background, and then put me floating over a version of the original video which is re-timed to go along with all my words exactly? does that make sense? this should be the third and final version of this particular video.
The take didn't follow the script word for word. That was fine. Claude Code transcribed what was actually said and moved every animation to match, so you can speak naturally and still get a tightly timed video.
Save points: version control
Software breaks, and AI breaks it confidently. Version control makes every break cheap: save the project whenever it works, check what changed, and roll back instead of arguing.
What it covers
- Your app is a folder of text files
- Why one small change breaks something else
- Commits are save points: commit whenever it works
- Read a diff without reading code
- Roll back, don't argue with the AI
- What git can't save: uncommitted work and your users' data
- One small change, then test it yourself
- Branches: parallel timelines for experiments
- GitHub is a backup, not a launch
- Never commit a secret
- The loop: Ask, Test, Review, Commit
1 · The explainer
8 minutes · narrated with ElevenLabs · animated in Remotion
please make me an explanatory video which deeply explains the most important practical principles of Software and Version control to someone non-technical who is now using AI to write software. Use ElevenLabs and Remotion to make it perfect.
Then one more message:
- also, ultracode also, ultracode
Ultracode tells Claude Code to split big work across many agents at once. Here, three writers drafted competing scripts and judges picked the best. Then one animator per scene built the video, and separate reviewers checked every scene before it shipped.
2 · The music video
3 minutes · song made in Suno · animated in Remotion
The same lessons, simple enough to sing along to. These prompts went into the same conversation, right after the explainer.
Can you produce high quality lyrics for a much simpler version of this script as well and then use Suno to make that into a song? I have suno, so you should just be able to use the browser to do that.
Yes, now turn the first song (the 3:10 version) into a music video using your same graphic design process.
everything is like... "jumping" all the time, but it's not actually to the beat, and it's quite distracting. Can you get rid of that breathing motion?
Read the lyrics
[Intro] (Oh-oh-oh) Save points! (Oh-oh-oh) [Verse 1] Eleven o'clock and my app was running fine Typed "make the button blue," just one tiny line Poured myself a coffee, came back, what did it do? Now nobody can log in, but hey, the button's blue I said "Please fix it!" ... "You're absolutely right!" Then it broke two more things, and we fought half the night [Pre-Chorus] If I could just go back to when it worked Back before the blue, back before it hurt [Chorus] Save points! (Save points!) Commit when it works! Lock it in, lock it in, before it gets worse Ask! Test! Review! Commit! (Hey!) When it all falls apart, don't you fight, don't you quit Roll back to your save point, ask! test! review! commit! [Verse 2] One little change at a time, nice and slow Then I test it myself, "should work" don't make it so I look at what changed before I let it stay Asked for one button, twenty files changed? No way! And I don't need to learn every git command Just say "Commit this," and my A.I. understands [Pre-Chorus] Don't fight it for hours (No!) Don't plead and don't curse (No!) Just go back to the save from when it worked And ask again, but smaller, small steps don't hurt [Chorus] Save points! (Save points!) Commit when it works! Lock it in, lock it in, before it gets worse Ask! Test! Review! Commit! (Hey!) When it all falls apart, don't you fight, don't you quit Roll back to your save point, ask! test! review! commit! [Bridge] Push it to GitHub, keep a copy off-site 'Cause coffee finds laptops in the middle of the night And your secret keys? Keep 'em out of every commit Delete 'em later? History still keeps every bit [Spoken] Seriously. Not even once. [Break] [Gang vocals] Did you ask? (I asked!) Did you test? (I tested!) Did you look? (I looked!) Then commit! (Commit!) [Final Chorus] [Gang vocals] Save points! (Save points!) Commit when it works! Lock it in, lock it in, before it gets worse Ask! Test! Review! Commit! (Hey!) When it all falls apart, don't you fight, don't you quit Roll back to your save point, ask! test! review! commit! [Outro] Eleven o'clock, the button's blue, and everyone gets in Save points! (Save points!) Commit when it works (Commit when it works!) Save points! Commit when it works!