beckon
Beckon blog

How to Build Scroll-Driven Video Websites with Claude Code

ยท Beau Johnson

In shortScroll World is a Claude Code skill that turns a chain of short pre-rendered video clips into a homepage you fly through as you scroll. It doesn't use a 3D engine or WebGL. I used it to build nightcrew.studio and heybeckon.ai, and I cover the seven steps, the playbook files and where it breaks.

In this video I break down how I build websites that are made to convert and don't look like AI slop. I use two real sites as examples, nightcrew.studio and heybeckon.ai, and both were built with Scroll World. It's a Claude Code skill where your scroll moves a camera through a world made of short pre-rendered videos. If you use AI coding agents to ship landing pages and every page keeps coming out looking the same, this one is for you.

What I cover in this video

  • 0:00: How one picture of a clay film studio grew into a whole homepage in a single afternoon
  • 0:46: What the AI slop look actually is, and the fair argument on the other side
  • 2:18: The test I use to spot slop, and the start of the heybeckon.ai walkthrough
  • 3:49: nightcrew.studio, scene by scene
  • 4:36: What "made to convert" means here, and what Scroll World actually is
  • 6:06: How it works in seven steps
  • 9:53: The playbook, file by file
  • 11:25: Where it breaks, and when not to use it

What AI slop looks like, and the fair other side

You've seen it: a purple gradient on white, the Inter font, a big centered headline and three rounded cards with an icon in each. Anthropic described it in their post on frontend design through Skills: without guidance, an LLM "will almost always conform to Inter fonts, purple gradients on white backgrounds, and minimal animations." They call this distributional convergence. The model learned from the whole web, so the safe average of the whole web is what you get back. Adam Wathan, who created Tailwind, half-jokingly apologized for making every button in Tailwind UI indigo, which he said ended up "leading to every AI generated UI on Earth also being indigo."

To be fair to the other side, Unbounce's 2021 study of 36,928 landing page variants found that copy carried about twice the weight of design. A plain template with a sharp offer can beat a beautiful page with a vague one. Also, full disclosure: my Beckon site uses Inter too.

So the problem isn't really purple. It's that every page looks the same. This is the test I use:

Could a competitor swap their logo in and use this page as is? If yes, it's slop, no matter how pretty it is.

The two sites, scene by scene

heybeckon.ai is the site for Beckon, my agent desktop app. The current theme is Theme 01, Aurora: a pixel art night under the northern lights, with six scenes and five connectors. It opens at an observatory ("workspace for your coding agents") and moves to a voice hall where an astronomer talks into a big brass horn, because in Beckon you talk to your agents. Next is a dome with a telescope surrounded by terminals ("not an IDE, every agent, one workspace"), then a lantern garden where every idea gets its own workspace, then a star archive for the built-in second brain. It ends at a lake town where you build it together. The world on the site is also a feature in the app, so you can switch your own workspace to Aurora inside Beckon.

nightcrew.studio is a clay world, and its story walks through the service in order: a house at night with the owner asleep upstairs, an archive workshop where you describe your business once, a film set where the crew works, a rooftop where glowing video cards float up as posts go out, and a shop at sunrise. It has five scenes and four connector flights, made with GPT Image and Kling. The first picture was made at 1:04 PM on Oct 23, 2026, the last clip finished at 1:59 PM, and the site was committed at 2:34 PM. Forty-two minutes in, I told the agent the first hero looked way too vibecoded.

I can't show you a conversion number for either site, and I won't make one up. What I mean by "made to convert" is that each page tells one story, every scene sells one step of the offer, and the page ends with plain pricing, an FAQ and a clear button to book or buy.

How Scroll World works in seven steps

There's no 3D engine and no WebGL. The site is a chain of short videos made ahead of time, and your scroll bar scrubs through them: scroll down to play forward, scroll up to play backward. I didn't invent it. It's built on the open-source scroll-world skill by oso95 and the hardened fork by cth9191, and my version was patched by actually shipping it. Because it's a skill, it starts by interviewing you about the world, the story beats, brand colors, art style and budget. It tells you what it plans to spend before it makes anything.

  1. Scenes. Make one still picture per story beat. Every prompt starts with the same style paragraph, copied word for word, so the pictures look like one world. Make the anchor image first and approve it before you generate the rest.
  2. Dives. Turn each still into a roughly 10-second clip that flies the camera in. Every dive prompt ends with the same kind of line: The clip ends settling into a slow, steady, forward drift.
  3. Connectors. Each connector flight starts on the real last frame of the previous clip and ends on the real first frame of the next one. Never use the original pictures, because each generation renders a little differently and you'd see a jump at the seam.
  4. Seam check. Each seam gets an SSIM score from 0 to 1, and 0.95 or higher counts as a true handoff. On the first version of the Beckon site, two seams scored 0.62 and 0.67 and re-rolling didn't fix them, so a short crossfade hides them. Aurora landed between 0.87 and 0.92 on all ten seams. You also have to watch the middle of each clip. One connector grew a giant disc on the horizon, and the fix was a re-roll prompt that said empty sky, dark water horizon, no new islands.
  5. Encoding. Strip the audio and put a keyframe every 8 frames on desktop. Phones get their own 720p copy with a keyframe every 4 frames. The loading pictures are taken from the encoded video, so nothing jumps when playback takes over.
  6. Scrub engine. It's 615 lines of plain JavaScript with zero dependencies. The page is one tall, normal scroll, and each dive gets about 1.4 screens of it. How far you are through that slice sets the video time, with a little easing so it glides. Clips load as whole files in memory because some hosts can't seek video. There's also a plain-text copy of every line for Google, since this is a landing page and SEO copy matters.
  7. Mobile. This is where it broke. Desktop worked on day one, and phones took seven engine revisions. iOS Safari gives you about three live video decoders, so the engine hands them out and takes them back as you scroll. All video elements are created up front, seeks never stack up, hold frames make a slow connection wait at the seam instead of jump-cutting, and a debug overlay is the only practical way to debug a real iPhone.

The playbook and where it breaks

The skill file is 608 lines and covers the whole method. The most useful file is the field notes from shipping heybeckon.ai, and its rule is that where it disagrees with the skill file, the field notes win. It holds the real seam scores, the encode settings that shipped and a symptom-and-fix table for iPhones. Alongside it are the production scrub engine with every change marked, a pipeline you can rerun after a crash without paying twice for finished clips, a prompts file, a camera guide by industry, and a gotchas file. For example, the video model's safety filter flags words like "bed," "pool" and "wine," and the file has a four-step ladder for working around that.

Here are the limits. It's heavy: a full scroll measured on Nov 4, 2026 pulled about 208 MB on desktop and 86 MB on a phone for heybeckon.ai, and about 100 MB and 40 MB for nightcrew.studio. Clips only load near where you are on the page, though. In Low Power Mode an iPhone can refuse to play the clips, so you see stills. The engine respects reduced motion and shows stills there too, and I put pricing and the FAQ in plain HTML after the flight. Some seams are still hidden behind crossfades. Skip this approach for docs, dashboards, catalogs, or any offer you haven't nailed down yet.

Key takeaways

  • AI gives you the average website when you ask for the average, so pick a world only you could build.
  • Copy and offer come first. A beautiful flight can't save a vague offer.
  • Build connectors from the real last and first frames of neighboring clips, and score every seam with SSIM.
  • Most of the work is mobile polish, and writing iPhone fixes down once means your agent doesn't have to learn them again.
  • Make the pictures and clips first, then let the scroll tell the story.

FAQ

Does Scroll World use WebGL or a 3D engine?

No. It's a chain of short pre-rendered video clips, and the scroll position scrubs through them. The scrub engine is 615 lines of plain JavaScript with zero dependencies.

How do you avoid visible jumps between scenes in a scroll-driven video site?

Each connector clip starts on the real last frame of the previous clip and ends on the real first frame of the next, never on the original pictures. Seams are scored with SSIM, where 0.95 or higher is a true handoff, and a short crossfade covers any seam that won't score well.

Why is scroll-scrubbed video hard on iPhones?

iOS Safari gives you only about three live video decoders, and in Low Power Mode an iPhone can refuse to play the clips. The engine recycles decoders as you scroll, creates every video element up front, and uses a 720p copy with a keyframe every 4 frames.

When should you not build a scroll-driven video landing page?

Skip it for docs, dashboards, catalogs, or anything people come to scan quickly. Also skip it if you haven't nailed your offer yet, because copy matters more than design.

Run your agents in Beckon

A workspace for your coding agents. Get more work done in less time.

Download BeckonSubscribe on YouTube
Full video transcript

0:00At 10:04 in the afternoon on October 23rd, my agent made one picture, a tiny Clayfilm studio at night. By 2:34, that one picture had grown into a whole homepage you fly through, built and committed. It's five scenes and one camera with no cuts. And 42 minutes into that build, I looked at the first hero section and told it it looks way too vibecoded. So that's nightcrew.studio. And in this video, I'm going to be breaking down how I build websites that are made to convert and don't look like AI slop using that site and heybecken.ai. What AI slop actually is, both sites scene by scene, the scroll world skill behind them, how it works step by step, and where it breaks, because it does

0:46break. Let's jump right into it. So, what is AI slop when it comes to a website? You've seen it. a purple gradient on white, the inter font, a big centered headline, and three rounded cards with an icon in each one. I mean, who uses a centered hero with a purple gradient anymore? Apparently, everybody. Anthropic wrote it down themselves back in November 2025. Their post says, "When you ask an LLM to build a landing page without guidance, it will almost always conform to interfonts, purple gradients on white backgrounds, and minimal animations." They even gave it a name, distributional convergence. So basically, the model learned from the whole web and the safe average of the whole web wins. And then there's Adam Wavin, the guy who made Tailwind. Half

1:33joking, he formally apologized for making every button in Tailwind UI indigo 5 years ago. And he wrote that it ended up quote leading to every AI generated UI on Earth also being indigo. Which is hilarious. And I mean, you've definitely seen those indigo buttons. Now, here's the other side, and I want to be fair about this. In a study from 2021, Unbounce looked at almost 37,000 landing page variants, and their model found copy had about twice the weight of design on conversion. They do sell a page builder, so take that for what you will, but a plain template with a sharp offer can beat a beautiful page with a vague one. So, the real problem with slop is that every page looks the same, purple or not? And full disclosure, my

2:18beckon site uses inter 2. So, here's the test I use. Could a competitor swap their logo in and use this page as is? If the answer is yes, it's slop, no matter how pretty it is. So, the goal is a page only you could have made, where the story is the offer. I'll show you mine right after this. What if a new video for your business showed up every morning? Night Crew learns your business once, then makes a short every night in your own voice. It runs five brands right now, over half a million views a week. Nightcrew. Nightcrew.studio. So, the first site is Heybecken. Beckan is my agent desktop app. And the site right now is theme1 called Aurora. It's a pixel art night under the northern lights. And you can see as you

3:04scroll, the camera flies into each scene. It starts at an observatory where the headline says workspace for your coding agents. Then a voice hall with an astronomer talking into a big brass horn because in Beckin you talk to your agents. Then the dome a telescope with terminals all around it. And that's where the site says not an IDE an every agent one workspace. Then a lantern garden where every idea gets its own workspace. Then a star archive which is your second brain builtin and it lands on a lake town where you build it together. And here's the part I love. The world on the site is also a feature in the app. Every month or two, Becken gets a new world and subscribers can switch their own workspace to Aurora

3:49inside the app. So the second site is nightcrew.studio, the one from the start of this video. It's a clay world and the story is the service in order. It opens on a little house at night where the owner is asleep upstairs while the crew works downstairs. Your content made while you sleep. Step one is an archive workshop with a brass filing machine and that's where you tell it about your business once. Step two is a film set where the crew gets to work while you sleep. Step three is a rooftop with glowing video cards floating up into the sky. You approve and it posts everywhere. And then it lands at sunrise on a shop with a little crowd gathering outside. Wake up to a new video every day. So, which one would you rather scroll through? The observatory or the clay house? Let me

4:36know down below. Now, I can't show you a conversion number for either site, and I'm not going to make one up, but here's what I mean by made to convert. Each page tells one story. Every scene sells one step of the offer, and then you get plain pricing, an FAQ, and a clear button to book or buy. That's the part templates skip. So, what is scroll world exactly? It feels like a 3D world, but there's no 3D engine in the browser and no WebGL either. It's a chain of short videos that were made ahead of time, and your scroll bar is the scrubber. Scroll down, the video moves forward. Scroll up, it goes backwards. So, it looks almost like a movie is unfolding as you scroll through the site. Apple's product pages made this kind of thing famous.

5:21CSS Tricks rebuilt the AirPods Pro page back in 2020, and that one flips through a stack of images as you scroll. So, Scroll World does the same thing with video instead. And I didn't invent this. It started as an open- source agent skill on GitHub called Scroll World by OSO95, which is sitting at about 10.8K stars right now. Then cth9191 made a hardened fork and my version is a fork of that one patched by actually shipping it on heybecken.ai and breaking it on iPhones. So because it's a skill you don't start by writing code. It interviews you first. What's the world about? What are the story beats? Your brand colors, the art style, your budget. Then it tells you what it's

6:06going to spend. And only then does it start making anything. So, here's how it actually works. And don't get lost in the sauce here. There are seven steps, but each one is simple. Step one, the scenes. You make one still picture for every beat of your story. And every single prompt starts with the same style paragraph, copied word for word. That one paragraph is what makes it feel like one world instead of six random pictures. So, you make the anchor first, one image, you approve it, and then you make the rest from it. A styless on the anchor costs one generation and after a cold batch it costs all of them. On night crew the anchor was that 104 picture and three more scenes came off of it by 118. Step two, the dives. Each

6:52still turns into about a 10-second video that starts on that picture and flies the camera in. And every dive ends on the same kind of line in the prompt. The clip ends settling into a slow, steady, forward drift. So every clip hands the next one a clean, calm starting motion. Step three, the connectors. This is the trick, and honestly, it's pretty awesome. Between two scenes, you make a flight where the first frame is the real last frame of the clip before it, and the last frame is the real first frame of the clip after it. Never the original pictures because every generation renders a little bit differently. Can you see why that matters? Use the original picture and you get a jump right at the scene. So, Night Crew is five dives and four connectors, and

7:37Aurora is six dives and five connectors. Step four, the scene check. Every scene gets a similarity score from 0 to one, called SSIM. A true handoff is 0.95 or higher, and cling drifts. On the first version of the Beckan site, two seams came in at 62 and 67, and re-rolling didn't fix it, so a short crossfade hides them. Aurora landed between 087 and 0.92 on all 10 seams. So, you also watch the middle of the clips. One connector grew a giant disc on the horizon out of nowhere. And what helped was a roll prompt that literally said empty sky, dark water horizon, no new islands. Come on now. Step five, the encoding, which is what keeps the

8:22scrubbing smooth. The audio gets stripped and there's a full key frame every eight frames, so jumping to any spot in the video is cheap. Phones get their own 720p copy with a key frame every four frames. And the loading pictures come from the encoded video, so when the video takes over, nothing jumps. Step six, the scrub engine. It's 615 lines of plain JavaScript with zero dependencies. The page is one tall normal scroll, and each clip gets a slice of it, about 1.4 four screens per dive. Every frame, how far you are through that slice becomes the video's time, eased a little so it glides. So, the clips load as whole files in memory because some hosts can't seek a video and it just freezes on frame zero. And there's a plain text copy of every line

9:08on the page for Google because SEO copy is not optional. This is a landing page. Pretty simple when you break it down, right? And then step seven, mobile, which is where it really broke. Desktop worked on day one. Phones took seven engine revisions. So, an iPhone only gives you about three live video decoders, and the engine now hands them out and takes them back as you scroll. Every video element gets created up front because iOS gives play permission per element. Seeks never stack up, so a fast flick can't freeze it. Hold frames mean a slow connection waits at the seam instead of jump cutting. And there's a debug overlay because that's the only practical way to debug a real iPhone. So now here's what this is all about. The

9:53playbook. Let's walk through it like a GitHub repo. It starts with skill.md 608 lines, the whole method from the interview all the way to the final check. Then there's a file called beckan learnings field notes from shipping hey beckan.ai. And it has one rule at the top. where this file and skill.md disagree, this file wins. So, that's the best file in there. It has the real seam scores, the encode settings that actually shipped, and a symptom and fix table for iPhones. Seam one is fine, but seams 2 through 4 are frozen. That's the decoder recycling. Jump cuts on slow networks hold frames. The page froze at the first seam on Chrome for iOS create the video elements up front. So then there's the scrub engine itself, version

10:397, the exact one running in production. Every change is marked as a beckon patch, and the notes say never recopy it from upstream. There's a pipeline file you can rerun after a crash without paying twice for clips that already finished. There's a prompts file with the style, dive, and connector lines. And the skill has a camera guide for different industries. Real estate gets a steady cam glide through doorways. Food gets a push-in close on the craft. And there's a gotchas file. huge files. You used all intra, a video model safety filter flagging the words bed, pool, or wine, and a four-step ladder to get around it. So, honestly, the best stuff in here is the boring stuff, the things that only break on a real iPhone written down once so your agent never has to learn them again. That's what I mean by

11:25a playbook. So, here's where it loses, and I want to be straight with you. First, it's heavy. When we measured it on November 4th, a full scroll of Heybecken.ai pulled about 208 megabytes of video on a desktop and about 86 on a phone. Night crew is about 100 on desktop and 40 on a phone. Now, the clips only load near where you are on the page, so someone who leaves at the hero never downloads the rest, but the phone version isn't optional. Second, iPhones, you get about three decoders, and on low power mode, an iPhone can refuse to play the clips. So you see the still pictures instead of the flight. Third, motion. For some people with inner ear disorders, motion on a page can cause dizziness, nausea, and

12:10headaches. That's from the W3C. So the engine respects the reduced motion setting and shows stills instead. It keeps your normal scroll speed, but you still have to scroll through the story to reach the pricing. So I put the pricing and the FAQ in plain HTML after the flight. Fourth, the seams aren't perfect. Some of them are hiding behind a crossfade, like I said. So, what about the cost? Aurora was five images and 11 clips for about $24 by the build notes. The flight is the fast part. The phone polish is the long part. So, when should you not use it? Docs, dashboards, cataloges, anything people come to scan fast. And any page where you don't know your offer yet. Remember, Unbounce, copy first. A beautiful flight can't save a

12:56vague offer. So, what am I doing with it next? Beckon gets a new world every month or two, and there's now a follow-on skill that builds a whole six scene flight from one hero picture and a few sentences. So, to sum it up, AI gives you a generic website when you ask it for the average. So, pick a world only you could build. Make the pictures and the clips first and let the scroll tell the story. I'm not a designer, and I still got sites out of this that I'm really proud of. So, what would your world be if your business was a place people could fly through? What's the first room? Put it in the comments. I'm curious. And if this got you thinking past the purple gradients, give it a like. It really helps the video spread. Have a blessed day.