Quick summary
A scroll-world is a single continuous camera flight through a generated place, scrubbed by the page scroll. There are no cuts: the visitor scrolls and the camera moves, beat to beat, until they arrive somewhere.
This is the pipeline that produces one. It interviews you for the story beats, generates the scene stills, picks a camera architecture that suits the concept, generates and joins the video legs, encodes them so a scrubbing playhead stays smooth, and assembles the page — then makes you inspect every seam before it calls the build finished.
Who this skill is for
This is for people who want a cinematic fly-through site and do not have a 3D artist, a motion designer, or six weeks.
- Studios pitching an experience-led site who need to show one, not describe one
- Brands with a world worth flying through — a place, a product line, a process, a story
- Developers who want the seam-joining and encoding technique documented instead of guessed at
What problem this skill solves
Everyone can see what a scroll-world looks like. Almost nobody can get one to hold together, because the hard parts are invisible in the finished result.
- Generated scenes drift — palette, light and scale wander between shots, and the world stops feeling like one place
- The joins between camera legs are where these builds die: a mismatched frame reads as a hard cut and breaks the illusion instantly
- Video that scrubs smoothly under scroll needs specific encoding, and the default export from any tool stutters under a scrubbing playhead
What you get with this skill
The download is the full production pipeline, including the parts that only matter once something has already gone wrong.
- The eight-step build method, from the brand interview through to the seam QA pass
- Two documented camera architectures with guidance on which concept each one suits
- The encoding recipe for scrub-safe video, plus the assembly code for the scroll-scrubbed page
- A gotchas reference collected from real builds — the top five inline, the full list alongside
Steps overview
| Step | What happens |
|---|---|
| Bootstrap | Set up the workspace and check the tools before spending anything |
| Interview the user | Decide what the world is before deciding what it looks like |
| Generate the scene stills | Lock the look of every beat as a still first |
| Float the scenes | Optional pass to lift flat scenes into depth |
| Choose the camera architecture | Pick continuous take or dive-in — this makes or breaks the feel |
| Generate the connectors | Join the beats without a visible cut |
| Encode for smooth scrubbing | Make the video survive a scrubbing playhead |
| Assemble and QA the seams | Wire it up, then go looking for the joins |
Design & branding system
The engine treats visual continuity as an engineering constraint rather than a matter of taste, because a world that drifts stops being a world.
- One video model for the whole chain — documented as a rule, because mixing models is the single biggest cause of a world that does not cohere
- Palette, light direction and scale are locked at the stills stage and every later step is checked against them
- Camera grammar is matched to the concept rather than defaulted — the skill spells out which moves suit which kind of world
- The interface layer sits above the film as its own layer, so captions and chrome can be restyled without touching the flight
Output & performance budget
The output is pre-rendered video driven by scroll position, which is why the cinematic look costs almost nothing on the device.
- No WebGL and no 3D runtime — the browser only ever scrubs a video, so mid-range phones handle it
- Encoding is tuned for scrubbing rather than playback, which is what keeps the scroll responsive instead of stuttering
- Poster frames and compressed masters keep the first paint fast even on cellular
- Output is framework-agnostic: the assembled page drops into plain HTML, React, Vue or Next without changes to the technique
How this skill pays off
A scroll-world is a pitch you can fly through. The engine exists so that experience is a week of work rather than a quarter.
- The visitor is inside the story from the first scroll tick, which is a fundamentally different level of attention than a static page earns
- Each beat lands one message before the camera moves on, so the argument accumulates instead of blurring
- By the final beat the visitor has flown the whole world, which is why the closing ask reads as earned rather than pushed
Other information about this skill
Worth knowing before you download it.
- This is the hardened fork. The upstream reference build is published separately as Scroll-World Original if you want to compare them
- Generation costs real credits through Higgsfield. The pipeline is ordered to spend them late — stills before video, video before connectors
- The seam QA pass is not optional. Every build that has looked wrong has looked wrong at a join
- The engine runs in your own Claude Code session, so your brand material and your generated assets stay on your account
Output examples
Four worlds built with this engine, captured from the live sites.
