In the space of a few days, three posts on X got flattened into one headline: AI can build 3D now. True - and it is hiding the interesting part.
These are not three versions of the same thing. They are three different jobs, built on different stacks and aimed at different buyers. This is a showcase rather than a tutorial: every example below has a repository, live demonstration or original thread you can inspect yourself.
Source: WY on X - @akokoi1
The short version of Three.js
Three.js is the JavaScript library that turns a browser tab into a 3D viewport: camera, lights, meshes, materials and controls. It is the renderer, not the source of truth - nothing below replaces a real CAD or BIM file. What it buys you is distribution: a link a client can open on a phone and walk through instead of a PDF they must imagine in 3D.
@akokoi1 - a floor plan turned into an app
One floor plan in, about an hour with Claude Opus later: a single HTML application with a dimensioned 2D plan, furniture library, wall alterations, floor-material cost take-offs and a walkable low-poly 3D twin with WASD navigation. It is open source: a client-facing options tool, not a BIM system.
@Skylartkitchen - a kitchen renovation turned into a manual
This is not merely a polished render. It is a 21-step build manual for a real kitchen renovation: demolition order, products, supplier details, measurements, plumbing connections and a live-with installation programme. Three.js acts as the visual highlighter over a document that already contains trades, sequencing and checks.
@uncle_render - a house turned into a film
A short photoreal day-in-the-house film: overhead linework becomes a rendered facade, then cuts to a home office, the front door and a drive away. This is image and video generation used as an architectural sales pitch - not an editable Three.js model and not a construction document.
Steal the pattern, not the aesthetic: each example is a different document wearing the same 3D-walkthrough costume.
Why it is worth building on, not just watching
Separate the work into two layers. The sales and operations layer - Three.js, glTF or an IFC viewer - is where an LLM can quickly hide a level, isolate a service or walk a renovation option. The truth layer - IFC, Revit, CAD, specifications, code checks and quantities - is where liability lives. Do not let a model invent a pipe size, structural decision or wall thickness.
Source: https://x.com/Skylartkitchen/status/2103468829859020824?s=20
What this is not
None of these examples is a permit set, clash report or structural check. The floor-plan application's cost take-off is a heuristic, not a quotation. The kitchen manual names trades and products but is not a licensed plumber's drawing. The house film is persuasive imagery, not measured information. Treat them as communication tools rather than the record of what gets built.
Try it yourself
Two of the examples are one click away, and the third lives inside its original thread.