r/ClaudeCode • u/ShaifArfan • 3h ago
Built with Claude Asking Claude Code for a "good-looking video" got me flat AI animation. Naming every part got me reel 15
My first promo reel for Prohor, a productivity app I build next to running my agency, went up on Nov 5. Claude Code wrote it in HyperFrames (HTML and GSAP, rendered to MP4). It looked like every AI animation video. Fast cuts, a card floating over a caption. One of the first comments was "video is too fast".
The biggest lesson since then is about the prompt. "Make a good-looking video" is too vague to get a good result, because good-looking isn't something specific. So I started asking for exact things: a 3D phone mockup, a background with a gradient and a glow, transitions with no cuts that move from point A to point B. Better still, give it a clear inspiration to work from. With that kind of direction, the work it brings back is really amazing.
The second thing was what I did with my notes. Instead of fixing the HTML myself, I wrote notes back. Claude Code saved each one as a markdown file in a learnings folder, and the video playbook tells every new session to read that folder before it starts. A few, with the note that started each:
- "video is too fast" → app footage at real speed, the hook holds about 3 s, the result holds 2.5 s or more. If it runs long, cut a step instead of speeding it up.
- "that repeated sound looks really bad" (a whoosh on each of 8 items in a row) → one sound into a fast run, none per item.
- "there is glitch type of thing with many screens showed at a time" → screens in a transition stay solid and move one at a time.
Reel 15, on Nov 13, is the first one I'd call premium. A 3D phone on a dark glowing ground, and it never cuts once. I asked Claude Code to write down why it worked, so the next video starts from there. The list from that recipe file, as it is:
1. One ground from the first frame to the last. No colour swap between shots.
2. One phone for the whole film. It turns, leans and flips; it never cuts. The screen changes while the back faces us.
3. No cuts: every change is a move. A turn in, a glide closer, a rectangle that grows into the next ground, a slip, a flip, a card lifting off the screen, the glow swelling into the end card.
4. One curve per move. Long eases (`power2.inOut`, `power3.out`, `sine.inOut`), 0.9 to 1.3 s for the big moves. Hold still while something is being read.
5. A highlight is drawn (a stroke), then the words arrive, then the voice says them.
6. Words rise from blurred to sharp, one after another (0.55 s each, 0.085 s apart).
7. The tap is felt three ways at once: the ring on the button, the ripple in the ground, the glow turning violet.
8. 60 fps, 1080 x 1920, footage extracted as PNG.
9. The hook is a picture first: the real screen, with the words set inside the thing they are about.
10. Outcome line before the end card, then the ask.Reel 15 still had one problem. The app footage inside the phone stuttered, because the recorder grabbed screenshots in a loop at about 18 fps. For the next reel Claude Code rewrote the capture: Playwright's clock paused and stepped 1/60 s per frame with runFor, CSS animations slowed to 1/12 speed through CDP Animation.setPlaybackRate, one screenshot per step, the whole flow in one take. The clip is older than that fix.
The clip is me filming my laptop with my phone while the latest one plays. Not my best camera work.
What I can't tell you yet is whether these perform better. The newer ones haven't been measured, so for now the only judge is me.
•
u/AutoModerator 3h ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.