BUILDING & APPS
Build a $5k assembly animation with zero code ⚡
Master this high-ROI AI workflow: This is the full build a scroll animation where your product pulls itself apart and puts itself back together as you scr
Master this high-ROI AI workflow: This is the full build a scroll animation where your product pulls itself apart and puts itself back together as you scroll. Agencies charge thousands for these, because the normal way needs a 3D artist and a developer. Here it's four steps, zero code, and about twenty minutes.
The real unlock of AI agents is not full autonomy, but human-in-the-loop systems design. Structure your agent inputs with explicit constraints, negative prompts, and automated test checkpoints. When building tools, keep token consumption lean by caching system prompts and isolating tasks into specialized sub-agents.
What you're actually building 🧠
A scroll-linked image sequence. Instead of a video that plays on its own, you have a stack of still frames painted onto a canvas, and your scroll position decides which frame shows. Scroll down, it steps forward. Scroll up, it steps back.
That's why it feels like you're physically controlling the animation, and it's the exact technique behind those high-end product pages. Apple's AirPods page is about 65 images being swapped as you scroll. No 3D engine, no magic.
Once you know that, the whole thing stops being intimidating. You're not building an animation. You're building a folder of pictures and telling the page which one to show.
The four steps 🛠
- 🎨 Generate two frames in Higgsfield. One of your product fully assembled, one of it exploded into its separate parts. Prompts below.
- 🎬 Animate the in-between with Seedance. Inside Higgsfield, feed both images in as first frame and last frame, and it generates every frame between them.
- ✂️ Slice the clip into frames. Take the video to Frames Extractor, set 30 frames per second, and download all the frames as a zip.
- 💻 Hand the folder to Claude Code. Drop the whole frame folder in and paste the build prompt. It writes the code that ties your scroll to the frames.
The two image prompts 🖼
Step one lives or dies here, so don't freestyle it. The trick: both prompts are word-for-word identical except the one thing that changes. That's what keeps the product, camera and lighting matching across both frames, so the in-between stays clean.
Start frame (your product, assembled):
End frame (your product, taken apart):
Swap the bracket for anything: a smartphone, a mechanical watch, a film camera, an espresso machine, a sneaker, a skincare bottle. "Exploded view" is the magic phrase, it's the technical name for those pulled-apart product renders and image models know it well.
For the end frame, name the 4 to 6 parts you want visible so the model doesn't invent mush:
Step 2: the motion prompt 🎬
In Seedance, load your start frame and end frame, then:
Keep the camera locked. A moving camera here fights the scroll, because the viewer is already controlling the motion.
Step 3: slice it into frames ✂️
Take that clip to framesextractor.com, set it to 30 frames per second, and hit Download all ZIP. Unzip it and you have a numbered folder of images, one per frame. It runs in your browser, so nothing uploads anywhere and there's no waiting.
Step 4: the build prompt 📋
Drop your frame folder into Claude Code, then paste this underneath.
3 bonus prompts to push it further 🎁
Once the sequence works, these turn one animation into a full polished section. Same project, same tool.
How to get the most out of it 🎓
- 🎯 Lock your two frames before you animate. The whole effect lives or dies on the start and end images. If frame one and frame two look like two different products, the in-between will look like mush. Regenerate rather than pushing forward.
- 🐢 Fewer frames than you think. 60 to 120 is the sweet spot. Every extra frame is page weight for motion nobody consciously notices.
- 🌱 Brand new? Paste the build prompt exactly as-is. You don't need to understand the code. Drop the folder, paste the prompt, then ask "run it and show me a preview" so you can see it working before you touch anything.
- ⚡ Power user? Feed it your real page. Paste your existing site code or design system first, tell it your section width, fonts and breakpoints, and have it match your stack instead of generating a generic file.
- 🔄 Reverse it. Run the sequence backwards and the product assembles itself instead of coming apart. Same frames, and it usually feels better.
The honest bit ✅
This is genuinely how the professional version works, but AI-generated frames can drift. A logo warps, a reflection flickers, an edge wobbles. Generate a couple of clips and pick the cleanest, and keep the animation simple (a rotation, an assembly, a single reveal) rather than a complex scene. Simple subjects on clean backgrounds give you the crispest result.
Also: the exploded view is the hardest thing to get right, because the model has to invent what's inside your product. For anything with real internals, expect a few rerolls, and name the parts explicitly.
The links 🔗
🎬 Higgsfield: higgsfield.ai (images and Seedance for the in-between)
✂️ Frames Extractor: framesextractor.com (video to image sequence, free, runs in your browser)
🤖 Claude Code: claude.com/product/claude-code (wires it to your scroll)