Those slow-scroll camera sites drift toward a product as you scroll, then reverse the moment you scroll back up. They used to run through an agency and a five-figure invoice. The original poster on r/PromptEngineering, posting as u/Professional-Rest138, just skipped the agency step entirely. The whole pipeline, footage generation and scroll-sync, now runs from inside one Claude Code chat. No video editor, no agency retainer, just one sentence describing the shot.
Quick start: write the camera shot as one sentence, cap the budget before Claude spends any credits, then scroll-test on a phone before anything ships. The steps below cover all three.
Here’s the mechanic behind it. Claude Code writes the actual website, same as any other build. Higgsfield, connected as a custom connector, generates the footage on request. Claude asks it for a starting image, then animates that into one continuous camera move. After that, it maps your scroll progress onto the video’s timeline, forward and backward. Scroll down, the camera drifts in. Scroll up, it drifts back out.
This Redditor also flagged the part that decides whether the result looks cheap or expensive, and it isn’t the code. It’s the shot description itself. A good one names five things: the subject, the setting, one camera move, a clear ending point, and empty space reserved for the headline. Skip any one of those and Higgsfield fills in the gap with a guess, and guesses are where the “obviously AI” look creeps back in.
🎬 Old Pipeline vs New Pipeline
The old way needed a storyboard, a motion designer, and a rendered clip handed to a developer. That developer wired the video to scroll position with custom code, then tested it across devices. Days of back and forth, plus the agency markup, before anything shipped. Every change to the shot meant a new round trip through the same chain of people.
The new way collapses all of that into one chat. Claude Code builds the site, requests the shot from Higgsfield, and wires the scroll binding itself. The only real input left is one well-written sentence instead of a studio-level production. Changing the shot now means rewriting a sentence, not re-opening a project with an agency. I didn’t expect the scroll-sync part to just work on the first pass.
Practical Steps
- 📝 Write the shot in one sentence. Name the subject, the setting, one camera move, an ending point, and space for the headline text. This is the exact sentence the original poster used:
Move slowly toward a charcoal running shoe on a black stone platform, ending close enough to see the knit texture, with empty space on the left for the headline.
One move per clip. Ask for five moves in one shot and the whole thing falls apart.
- 🔒 Lock the constraints before any generation starts. This instruction is what stops the result from looking like a demo reel:
Keep all readable text, logos and buttons in the website, not baked into the footage. No cuts, no sudden zooms, no morphing, no new objects appearing. Show a poster frame immediately while the video loads. Never hide the whole site behind a loading screen. Give me a static version for anyone with reduced motion turned on.
- Test it like a visitor, not a viewer. Scroll down fast, then scroll back up, then open the page on a phone. Scrolling exposes every frame of the clip, so a product that quietly changes shape halfway through becomes obvious.
- 💳 Set a budget before anything generates. Higgsfield needs a paid subscription, and every generation spends credits. Tell Claude the budget up front and ask it to show the full batch before it spends a single credit.
- Reuse the pattern across the page, not just the hero. A pricing section, a feature section, and a testimonials section can each get their own one-sentence shot and their own scroll range. Keep the same rule in every case: one move per clip, never five.
- Know where this technique stops. A fixed camera path is all this covers. Free rotation around a product, where a visitor can spin it themselves, is real 3D work and a different job entirely.
Once the scroll mechanic works, the next weak point is usually the page around it. Default fonts and a purple gradient give away an AI build just as fast as a broken scroll animation does. Pick a deliberate type and color system before launch, not after. That’s the part an agency would have handled anyway, and it’s worth getting right even when nothing else cost five figures.
Worth reading the original thread in full. The prompt wording and the reasoning behind each constraint are laid out better there than any summary can manage.
you know those websites where scrolling moves a camera through a scene, like a film? claude can build one now. you describe the shot, it generates the footage and wires it to your scroll
by u/Professional-Rest138 in PromptEngineering