Code-generated music video
- Views
- 9.6K
- Likes
- 154
- Replies
- 32
- Saves
- 67
A music video for a Mongolian throat singing dubstep track made in Suno v6, built entirely in code (HTML, GSAP, WebGL) by Claude Opus 5.5 running in Claude Code for over 9 hours, with the reverse-engineered prompt shared for reuse.
Full prompt1,968 chars
You're a motion director and creative coder. Make a finished music video for [song file], built entirely in code and rendered frame by frame. Concept: [your idea in one or two sentences] Look: [palette, mood, references] On-screen text: [title only / none / lyrics] Deliver: [full song or mm:ss to mm:ss], [16:9 / 9:16 / both, each recomposed, not cropped], [fps], H.264 + AAC for [platform] How to work: 1. Analyze the song before any visuals. Split it into bands or stems and export per-frame features plus a timing map (beats, bars, sections, hits). Every visual event reads from the map and is listed in it. 2. Give each musical element one visual job that serves the concept. Keep one idea transforming across the song instead of cycling effects. 3. Storyboard with timings and 3 style frames, get a fresh critic's verdict on them, then a 4-second end-to-end test before the full build. 4. Make every value a pure function of the frame number. Render offline, encode with the original audio (gain only). 5. After each full render, send it to fresh critic subagents that never saw the build, each returning ranked problems with timestamps and a ship / one more pass verdict: - sound-off: retells the story from a silent 2 fps contact sheet - sync: every cut, hit and visual event within 1 frame of the timing map - QA: specs, palette, text, artifacts, measured on the frames - director: brutal critique against the brief - one per extra aspect ratio: composition and platform UI zones 6. Fix render bugs first, then the biggest problem; re-render; log each round with before/after numbers. If critics conflict, the brief wins. 7. Stop after [5] rounds or when the bar passes. The final pass checks only for breakage. The bar: exact duration, size and fps; frame one finished; no still over 0.5 s; cuts and hits within 1 frame; audio unedited except gain, about -14 LUFS, true peak under -1 dB; text readable and inside safe areas; understood with the sound off.
Source: the creator's reply under the post. Kept in its original language, unedited.
Needs your own reference assets: besides the text prompt, the creator supplied images, video, audio, documents or a codebase, which are not hosted here. The prompt alone will not reproduce the result.
Tools the creator mentioned
Original post: https://x.com/kloss_xyz/status/2112006151885705553
All works are open data at GitHub · awesome-opus-5.5-video.
Model attribution is as stated by the creator and was not independently reproduced. View counts are a snapshot from 2026-10-20. The work belongs to its creator; DM @GoSailGlobal on X for corrections or removal.
