MUSIC VIDEO IN CODE - PROMPT PACK 10 prompts to direct Claude Code step by step. Free file from the AI2Play tutorial. HOW TO USE THEM - Use them in order. Words in [square brackets] are yours: replace them with your own. - Claude Code proposes, you decide. Give one note at a time and look at the result before the next one. - One prompt gives you a default video. Directing it step by step gives you YOUR video. - What we made with them: a 2:16 music video, made 100 % in code. Six three.js scenes, rendered frame by frame in headless Chrome, joined with FFmpeg. No video generator, no stock footage. - Each prompt is on one line, so it pastes as one message. 0. FIRST MESSAGE (before the 10 prompts, if you use our free files) When: Put your song and the free files in one new folder, unzip the Render Kit there, open Claude Code in that folder, and send this before prompt 01. Read the files in this folder first: the Render Kit's README, the checklist and the robot motion guide. Use the Render Kit to render my video. Then wait for my brief. 1. THE BRIEF When: Your first prompt: say what you want and what to avoid, before anything is built. Make a music video for my song [song file], made only from code: three.js scenes rendered frame by frame, joined with FFmpeg. It should feel like [a real hip hop music video]: a story, a camera that moves on the beat, [sci-fi machines]. Mood: [dark, epic, clever]. Avoid the usual AI look: no neon glow, no grids, no fake screen labels. Keep every word above the bottom quarter of the frame, where YouTube puts captions, and never cut a word off. Don't build it yet. First show me options. 2. OPTIONS When: Before you choose one look: see a few real choices, with your own song. Make [3] different worlds as [12]-second tests on the chorus, with the real song, so I can choose. Put a still of each on one sheet, with a letter. A note that worked in our video: "It's cute, but a robot arm gets boring after a few minutes. Let's do something new." 3. MIX When: When you like parts of different options: keep the best of each. I like the mood of [A and B] and the [liquid] in [C]. Use them together, one place for each part of the song. Leave out [the person in C]. 4. CHARACTER FIRST When: Before any scene: get the main character right on its own. Before any scene, design the main character alone: front, side and back, a close-up of the hands, and [3] poses. Matte materials, nothing shiny on the face. Show me [3] different directions on one sheet. A note that worked in our video: "Is the figure a little too stiff? Or should he be a robot, maybe a one-wheel robot?" 5. A NOTE THAT WORKS When: Every time something looks wrong: one problem, the change you want, and what to keep. In [picture 4], [the elbow is above the hand when the arm goes up]. I want [the elbow below the hand]. Keep [everything else]. A note that worked in our video: "When the hand goes up, the elbow is above it. It looks broken." 6. VERSIONS When: When you are not sure how to fix something: ask for choices, then pick one. Show me [6] versions of [option A], side by side, front and side view. A note that worked in our video: "Show me better versions of 4. The arms bend backwards at the elbow." 7. STORY MAP When: Before you build the scenes: plan the whole song, part by part. Map the song: list every section with its time, give each one its own place and one camera idea, put the cuts on the bar lines, and keep the biggest camera move for the last chorus. 8. ONE PART AT A TIME When: While you build: one part, your notes, then the next part. Make only [the intro and verse 1] first and send me the video. I will give notes, then we move to the next part. A note that worked in our video: "The first seconds feel static. Can the camera move smoothly with that first sound?" 9. CHECKS When: Before every render: Claude Code finds the beginner mistakes and proves its checks work. Before you render, check and tell me: every word above the caption area, no word cut off, nothing over the words, nothing passing through anything else, cuts on the beat, and a clean sound timeline. Break one check on purpose to prove it catches the problem. 10. FINAL RENDER When: When every part is approved: the full-size video. Render the whole video at 2560x1440, 30 fps, with smooth edges, and check that every frame is there. NOTES THAT WORKED (from our video, written clean) - "It's cute, but a robot arm gets boring after a few minutes. Let's do something new." - "Is the figure a little too stiff? Or should he be a robot, maybe a one-wheel robot?" - "Show me better versions of 4. The arms bend backwards at the elbow." - "The wheel is a little too big." - "Is he touching the ground or floating? Does the wheel roll the right way?" - "When the hand goes up, the elbow is above it. It looks broken." - "The first seconds feel static. Can the camera move smoothly with that first sound?" - "The ceiling looks like a box, not endless. It lost the realism." - "The tiny droplets far away look like noise. Make fewer and bigger ones." - "The outro is a little boring. Try a better composition." 8 TIPS FOR A GOOD NOTE 1. One change per note. Two problems = two notes. Then you can see what each change did. 2. Say what to keep. "Keep everything else" stops the parts that already work from changing. 3. Point at it. Name the picture, the letter or the second in the video: "in picture 4", "at 0:42". 4. Say what you see, then what you want. "The elbow is above the hand. I want the elbow below the hand." 5. Not sure? Ask. Ask a question ("Is he touching the ground or floating?") or ask for versions and pick one. 6. Details on your computer, then a phone. Most people will watch it on a phone. Away from your PC? Leave it on, turn on Remote Control and ask Claude for a phone copy. 7. Check the side view of a character. Some mistakes, like elbows that bend backwards, only show from the side. 8. You decide. Claude Code proposes. It is your video: say no when it is not what you want. MORE FREE FILES FROM THE SAME TUTORIAL - Checklist - Before You Render.txt - Robot Motion Guide.txt - Render on Your PC - Notes.txt - Song - Lyrics and Suno Style.txt - Music Video in Code - Render Kit.zip (our code from the video, free under the MIT licence) The video: https://youtu.be/uu9xPgwkYxY AI2Play: https://www.youtube.com/@AI2Play | https://ai2play.net/resources.html