Opus 5 Built a Procedural Desert You Can Actually Walk To

No meshes. No textures. No downloaded assets. A Reddit post from u/Any-Reputation8118 titled "I built a procedural desert explorer with Claude Code (Opus 5) and Three.js" racked up 1.6K upvotes and 135 comments in three days — then got reposted by the official Three.js X account on July 29, 2026, pulling in another 17.8K views and a fresh round of "one shot?" questions from the graphics community.

The demo: a third-person walk across a Journey/Dune-inspired dune field, rendered entirely by shader code, with a GPU-simulated hooded robe and six sand spells that permanently reshape the terrain under your feet. It's the desert entry we added to explainx.ai's Top 10 Claude Opus 5 game prompts roundup — here's the full standalone breakdown: what shipped, how the builder used Claude, the performance numbers, and the honest gaps.

Clip as reposted by @threejs on X, July 29, 2026 — originally from u/Any-Reputation8118's Reddit post.

TL;DR

What's Actually in the Demo

From the builder's own description: a browser desert you walk around in third person, where the terrain is a procedural dune field on a GPU clipmap — every surface generated in shader code, nothing loaded from disk. Sand deforms permanently where you walk and slowly erodes back over time. A hooded robe simulated as GPU cloth covers the player character. The sky is physically based and marched per pixel. Six aimed sand spells, bound to keys 1–5 and right mouse, dig real craters into the terrain and raise real dunes the player can ride.

Two Giza-style pyramids sit on the horizon — also shader-generated, not asset-based. Commenters spent a disproportionate amount of the thread confirming you actually can walk all the way to them ("yea, they're not solid objects though" — reachable, but empty up close, the same "the journey is the destination" joke Journey itself invites).

How Claude Was Actually Used

The builder's own account, quoted directly: "Claude Code with Opus 5 handled the project end to end: planning the architecture, writing the [engine] and shader systems, profiling performance, iterating from screenshots, and documenting technical decisions." Every subsystem — TSL shaders, compute kernels, physics integration, and the Node.js tooling used to measure it — went through the same agent.

The workflow detail worth stealing: a headless-Chrome harness that boots the app, takes a screenshot, and reports per-subsystem GPU cost, so changes were validated against measured numbers rather than a subjective "looks better now." That's the same instinct behind Claude of Duty's capture.mjs/imagediff.mjs pipeline — different builder, same conclusion: if you can't measure the frame, you're optimizing vibes.

Asked directly whether it was one-shot, the builder was blunt: "the original prompt was like 20% of the result, then I was working with Claude incrementally." Total spend: ~14 hours and ~5 million tokens, including detailed follow-up prompts and feedback on what was and wasn't working. That number lines up with the same builder's later SNOWFLOW demo (~9 hours, ~4M tokens) and with Anshu's 24-hour Long Silence — hours-to-a-day of iteration, not a single completion, across every credible "one-shot" game demo this cycle.

Performance: Good on a 5070 Ti, Rough Everywhere Else

The builder measured ~160 fps at 1440p on an RTX 5070 Ti. The comment thread is the more useful data point, because it's an uncontrolled hardware sample:

The builder's explanation matches the spread: "by default, browsers use integrated GPUs on laptops, so that's a problem of its own" — a WebGPU-only demo tuned against a top-tier discrete GPU will look like a slideshow on anything defaulting to integrated graphics. There's no WebGL fallback and no quality-preset ladder; navigator.gpu absent or under-provisioned just means a worse frame rate, not a graceful degrade. This is the same trade-off called out in the SNOWFLOW brief's own hard constraint: "No fallbacks. No WebGL path, no mobile path, no feature detection branches."

Character Design: Hiding a Cheap Model Behind Cloth

One exchange in the thread is a genuinely useful game-dev lesson. Asked whether the character model, cloth sim, and animation were all prompt-generated, the builder explained the actual design pivot: "the model is super simple. From the start it was the weakest part. So the fix was to redesign the model completely with a fully robed character in mind, so that the robe simulation kind of 'hides' the super cheap model."

That's a deliberate scope decision, not a limitation papered over — when the underlying asset (a humanoid body mesh) can't be pushed to AAA quality within the iteration budget, wrap it in a system (GPU cloth) that can. It's the same "don't fight the model's weak spot, design around it" instinct as the Godot photography sandbox picking voxel art specifically to avoid Opus 5's weaker hand-authored 3D asset pipeline.

The Three.js Repost

On July 29, 2026, the official Three.js X account (@threejs) reposted the demo pulled from Reddit, drawing 17.8K views and comments from graphics-adjacent accounts. One reply asked flatly, "One shot? 😅" — echoing the same skepticism every entry in this genre attracts; another called it something not seen "in the pre-AI era." Getting picked up by the engine's own official account is a stronger authority signal than another creator-account repost — Three.js has no incentive to amplify a demo that misrepresents what the library can do.

Honest Limitations

• No public prompt or repo for this demo. Unlike Claude of Duty's public prompt.md and MIT repo, or the builder's own later SNOWFLOW repo, the desert explorer's exact seed prompt was never saved or shared — you can study the pattern from SNOWFLOW's public brief, but not reproduce this exact build.
• Hardware-gated by design. WebGPU-only, no fallback path, tuned against a 5070 Ti-class GPU. Expect single-digit-to-mid-30s fps on integrated graphics or older discrete cards.
• The character model is admittedly weak — the builder's own words, not a critic's. The robe and cloth sim are there specifically to hide it, which worked for the clip but means close-up scrutiny of the character was never the goal.
• "~5 million tokens" and "14 hours" are the builder's self-report, not an audited receipt — treat it the way you'd treat any other public demo cost claim, useful as an order-of-magnitude anchor, not a guaranteed reproduction budget.

What to Steal for Your Own Prompt

1. Give the agent its own instruments before asking for polish — a headless-Chrome harness that screenshots and reports per-subsystem GPU cost turned "does this look better" into a measurable question, the single most repeated lesson across every Opus 5 game demo this cycle.
2. When one subsystem can't hit your quality bar, design around it instead of grinding on it — hiding a cheap character model under a robe sim shipped faster than trying to force AAA-quality humanoid modeling out of the same iteration budget.
3. State your hardware target explicitly and skip fallbacks on purpose if you're building a tech demo, not a product — a WebGPU-only, no-degrade path is a legitimate scope cut, as long as you say so before someone runs it on a laptop.
4. Publish the prompt if you want the pattern to spread. This demo's virality outpaced its documentation — the builder's later SNOWFLOW demo, which did publish the full brief, is the more useful one to copy from directly.

Related on explainx.ai

• Top 10 Claude Opus 5 game prompts — full text, 10 builders
• Did Opus 5 one-shot Call of Duty? Claude of Duty, full decode
• Opus 5 built a Homeworld-style space RTS — $632.65 breakdown
• Opus 5 Rocket League clone — then Opus played it
• Top 10 Claude Opus 5 use cases
• What is an agent harness?
• Loop engineering — design loops that run while you sleep
• img2threejs — procedural photo to Three.js

Primary sources: Reddit — u/Any-Reputation8118, "I built a procedural desert explorer with Claude Code (Opus 5) and Three.js" · Play — desert-dusky.vercel.app · Three.js repost on X, July 29, 2026 · builder's follow-up SNOWFLOW Reddit post and GitHub repo.

Build time, token counts, and performance numbers are as reported by the builder and commenters on Reddit and X between July 26–29, 2026. No public source repository exists for this specific demo — re-verify the live Vercel URL before citing, and treat "one-shot" framing in any related discussion as one seed prompt plus hours of iteration, not a single completion.