// ONE WEEKEND BUILD

The Byers house,
in your browser.

Hawkins, Indiana. November 1983, some time after midnight. The lights are up on the wall, the television is showing dead air, there is a bear trap by the front door, and the front door opens. You can walk around in it right now, in a tab, with nothing to install.

Walk through it Watch the film first

Desktop, Chrome or Safari. It takes the mouse pointer, so press Escape to get it back.

// WHAT IT IS

A room you can search

Living room, hallway, Will's room, the yard
Twenty-six bulbs that spell back
And the other side of it

// BY THE NUMBERS

19k

Lines of code, 46 files

Game engines used

Audio files in the project

// WHAT IT COST

A weekend

One person, one laptop, working in plain English with Claude Code. No 3D artist, no sound designer, no studio.

// SIXTY-SIX SECONDS

Watch it first.

Every frame is the real thing running, captured by a camera script instead of a person holding the mouse. The music is original, written by code in the same repo.

1280 × 720 · 30 fps/ 1,980 frames, captured headless/ Score: 108 BPM, C minor, written in Python

Now walk through it

W A S D walk Mouse look F ask the lights T type your own message E open the front door G cross over C crouch Esc release the cursor

// WHAT TO LOOK FOR

The room is dressed to be searched.

Not glanced at. Most of what is in here you will only find if you go looking, which is the point.

The alphabet, A to Z across three wandering rows, a bulb hung over every letter

A second string around the ceiling, because by the end she kept buying more

The bear trap, set and waiting a few feet inside the front door

A child's crayon drawing of a fort in the woods, pinned above the bookcase

A mix tape on the shelf next to the stereo, and the axe by the door

A twenty-sided die on the coffee table, and something small with five petals for a head

The waffles

The open paint can, the brush across the lid, and the drips that got away

Press G and you are standing in the same room on the other side of it

// HOW IT WAS BUILT

No engine. No art files. No sound files.

The interesting part is not that AI wrote code. It is what a small team stops needing to outsource.

// THE PICTURE

A renderer written from scratch, then pointed at a new room

No Unity, no Unreal, no game engine at all. The lighting pipeline came out of an earlier project of mine and was lifted over intact: shadow maps, ambient occlusion, anti-aliasing, bloom, automatic exposure and a film grade, all custom. Then the whole weekend went into what it points at. Light in the room comes from four different colour temperatures at once, which is most of why it reads as a photograph of 1983 instead of a video game. Moonlight through the south window at 8000K, a sixty watt table lamp at 2600K, a blue television, and twenty-six coloured bulbs.

// THE MOONBEAM

The shaft through the window is real, not a picture of one

The beam is calculated, ray by ray, against the actual geometry of the window. The glazing bars are cut out of the light rather than modelled in front of it, so the beam arrives already divided into panes and lands a real rectangle on the floor. It costs almost nothing and it is the single detail people notice first.

// THE TEXTURES

Every surface generated, then repaired by a script

Eighteen tiling surfaces and nine printed props were generated with an image model, which gets you pictures that look right and tile wrong. A Python script fixes what the model cannot: it heals the seams, divides out the lighting the model baked into the image, and derives the extra maps a renderer needs to make a flat picture feel like a rough or shiny thing. That script is the difference between an image and an asset, and it is about two hundred lines.

// THE SOUND

There is not an audio file anywhere in the project

Every sound is built out of oscillators and filters the moment you press play. The score is original, written in the idiom of the era rather than copied from it: C minor, 96 BPM, a four chord loop that circles instead of resolving, and a tempo scheduled against the audio clock so it stays in time no matter what the frame rate does. A footstep is three sounds layered, chosen by which surface you actually stood on. The room's reverb is measured from the room's own dimensions. Cross over and the music drops a third of its tempo and an octave of its pitch.

// THE TESTING

Robots walked the room before anyone else did

Two test scripts run headless. One drives the camera to nineteen fixed angles and saves a picture of each, along with any errors and the frame time. The other walks sixteen routes through the house checking that nothing climbs, sticks, or falls through the floor. The walking test is the one that finds real bugs: climbing onto the coffee table and from there onto the sofa, dropping through the floor one step into the hallway, a door that stayed solid after it opened. None of that shows up in a screenshot.

// THE FILM

The video above was shot by a script, not a person

A camera file lists eleven slow moves through the house, with events pinned to exact moments: the wall spells here, the door opens there, the room crosses over at thirty-four seconds. It renders 1,980 frames one at a time, each advancing the world by exactly one thirtieth of a second, so the lights spell at the right speed instead of at whatever speed the screenshots came back. A second script writes the music to match the same beat map. Change a camera move, rerun both, get a new cut.

// WHY I BOTHER

This is not about games.

I build one of these every few months to find the edge of what a small team can now do without hiring for it.

// THE OLD MATH

Six specialists and a quarter

A room like this used to need a 3D artist, a texture artist, a graphics programmer, a sound designer, a composer, and a QA pass. You would scope it in months and price it in tens of thousands, and most of that spend never touches the thing your customer actually cares about.

// THE NEW MATH

One person who knows what good looks like

The skill that mattered here was not writing code. It was knowing that four colour temperatures in one shot is what sells a night interior, and being able to say so in a sentence. Taste and judgment became the bottleneck. Execution stopped being one.

// WHAT TRANSFERS

Your version of this is boring and valuable

Same pattern, less atmosphere: the internal tool nobody would fund, the customer portal stuck in the backlog, the report that takes a person two days a month. The reason those never got built was cost and calendar. Both just moved.

// THE HONEST PART

It still needed someone driving

This was not a prompt and a coffee break. It was a weekend of steering, rejecting, and testing, with the same judgment I would bring to any build. AI did not replace the work. It removed the parts of the work that were only expensive.

Go walk around in it See six models try the same brief

// FREE · ONE EMAIL A WEEK

Get one AI idea you can actually use.

This page is one weekend experiment. I run these constantly, on my business and on my life, and write up the ones that work: the prompt, the result, and whether it was worth the time. Short, practical, no hype.

✓ A real prompt or workflow you can copy the same day
✓ What actually worked, and what wasted an afternoon
✓ Built from live client work, not press releases
✓ No spam. Unsubscribe anytime

// GET FREE UPDATES

One AI idea a week, plus all 9 free resources

One email. Instant access. We never share your address.