Build a flyable procedural city from an art bible in one HTML file

A Redditor gave Claude Code on Fable 5.2 a prompt, an art bible and eight concept images, and got a WebGPU Atlantis you can fly through that fits in one 96 KB HTML file.

Done withClaude Code· Nov 21, 2026

What they did

The poster wanted to test how far a current model could take a real-time 3D scene with no engine, assets or libraries. They wrote an art bible (city plan, materials, plants, water, lighting and six review shots) and made eight concept images of the city with ChatGPT, then handed both to Claude Code running Fable 5.2 with one starting prompt. Claude Code wrote everything: a WebGPU renderer, shaders for crystal refraction and mirrored canals, generators for every building and tree, collision, detail levels and a chiptune soundtrack made with Web Audio. The prompt set up its own checks: a separate subagent that saw only the art bible, the concept images and the renders listed visual faults, and GPU timing over a scripted 60-second flight tracked frame time.

How it went

The result is a ringed city of marble, canals and crystal towers that is generated on load, packed into one 96 KB file and published on GitHub Pages with the source and prompt in the repo. The poster reports about 2.5 ms per frame at 1440p on High on an RTX 5070 Ti, and the README gives about 28 fps on the Low setting on a budget Samsung phone. The post passed 390 upvotes on its first day. No cost or run time is given.

Worth knowing

This is the same poster's second build with this method, after an underwater scene, so the reviewer-subagent and timing loop is the part that carries over. The art bible and concept images gave the reviewer something concrete to judge against. It needs a WebGPU browser, best Chrome or Edge on desktop.

Try it

With Claude Code· 7 parts to fill in

Build [a place, e.g. a city or landscape] that a visitor can fly through in the browser, as one self-contained HTML file. Read [my art bible file] and the images in [my concept art folder] first and treat them as the target look. Use WebGPU with no engine or libraries, and generate every mesh, texture and sound in code on load. Target [frame time] ms per frame on [my GPU]. After each major step, render the review shots from the art bible and give them, with the art bible and concept images only, to a subagent that lists visual defects; also time a scripted [60]-second flight on the GPU. Fix what they report. Stop when the file is under [size] KB, the timing target is met and the reviewer finds no major defects, then show me the result.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related