You commented STACK. Here it is.

The video stack behind @I_Ship_With_AI

I can't edit video and I can't make music. Every video on my account is made by Claude Code with the tools below. All of them are free, except Claude Code itself.

A frame from one of the videos: “I can't edit video. I can't make music.” next to five real videos

The tools, with the original sources

1Claude CodeThe engine. You describe the video in plain words; it writes and runs everything.claude.com/claude-code
2HyperFrames skills (by HeyGen)Turns a web page into a video: animations, timeline, transitions, render to MP4.github.com/heygen-com/hyperframes
3AI voice: KokoroA natural English voice that runs free on your own computer (built into HyperFrames).huggingface.co/hexgrad/Kokoro-82M
4Whisper (faster-whisper)Listens to the voice and times every word, so captions and hits land exactly on it.github.com/SYSTRAN/faster-whisper
5Taste skillKeeps colors, type and spacing looking designed instead of generated.github.com/Leonxlnx/taste-skill
6Brag skillFinds the story: what to say first, what proves it, what the punchline is.github.com/latent-spaces/brag
7Music written as mathNo samples, no music library: Claude writes the soundtrack in Python and puts every hit on a word. That part is in my recipe below.see the recipe ↓

Install the video skills

npx skills add heygen-com/hyperframes

My recipe: the rules I use

Every rule below came from a real note I gave on a real video. You can read them here, or download the same thing as a Claude Code skill.

  • Voice first, picture second. Write the narration, generate one voice line at a time, and lay the scenes on a 120 BPM beat grid.
  • Keep ~180 ms after each voice line. Cutting tighter clips quiet final sounds: “Code” became “Cogue”.
  • Caption text from your script, caption timing from Whisper. Whisper mishears names and numbers; your script doesn't.
  • Every hit lands on the word that says it: a stamp, a counter reaching its number, a ✓.
  • The first frame is the thumbnail. Compose it; never swap in a different poster frame.
  • No grain, no jitter, no random numbers at render time. Viewers call it flicker.
  • Never show code or file names on screen. Say what happened in plain words.
  • Music ducks under the voice, except the closing line. A drop right at the punchline feels wrong.
  • One timeline, two formats: 16:9 for X, 9:16 for TikTok and Shorts.
  • Check before posting: flicker (frame-to-frame brightness), loudness (about −15 LUFS), and “can you hear every word” through the music.

A plain text file. Put it in ~/.claude/skills/voiced-explainer-video/ and ask Claude Code for a video.

The honest part

The tools do the work, but the first version is never the one I post. My job is saying what's wrong: “where's the voice?”, “why show the code?”, “remove the flicker”, “the music drops at the end”. Plan on a few rounds. AI is the engine. I'm the one driving.

What I'm building with this approach

Blitz Content AI writes SEO articles, product descriptions and posts in 5 languages. I don't write code; Claude does.

Try it free →
✓ No card · ✓ 2 free, then 5/mo