Home / Work / 3D Boutique | Opus 5.5 + Three.JS

2026 · Experiments

3D Boutique | Opus 5.5 + Three.JS

Year
2026
Role
Design + Development
Type
Personal
Discipline
3D, motion, web development
Team
Solo — direction and Claude Code
Status
Live experiment

Problem

Most AI “video” demos are clips you cannot enter. I wanted to know if Claude Opus 5.5 could write code that becomes a space you walk through.

Approach

I used Claude Opus 5.5 in Claude Code to write Three.js — a boutique you can enter, look around, and treat as a store, not a timeline.

Outcome

A walkable Three.js boutique — RAWSOUL SS26 — generated as real code with Claude Opus 5.5, not a rendered video.

A boutique you can enter

This experiment sat next to a Remotion motion test: can Claude Opus 5.5 generate video, or does it write the code that becomes motion? For the 3D path I asked for a boutique you can actually walk through.

The result is RAWSOUL SS26 / Store 001 — a Three.js space with sound, a cart, and hidden details. It is not a render. It is a site.

Code becomes the animation

The key idea

Code is the animation. Once the world is a Three.js scene, you can enter it, change it, and ship it. A generated MP4 cannot do that.

Principles

  • Enter, don’t watch: if you cannot walk in, it is a clip.

  • Fashion as the brief: a boutique gives the model a world with lighting, product, and type — not a generic room.

  • Keep the human taste: I directed the brand, the season, and what “done” looked like.

Remotion vs Three.js

I compared two Claude Opus motion paths: Remotion for presentation-style graphics that render to MP4, and Three.js for interactive worlds. Remotion is the right tool for a spot. Three.js is the right tool when the audience should move.

Claude Opus 5.5 doesn’t generate video — it writes code that becomes motion.

From empty rooms to RAWSOUL

Early prompts produced empty rooms and stock lighting. Tightening the brief to a named season, a store number, and a sound-on entrance gave the scene a reason to exist. I kept iterating in Claude Code until the space felt like a lookbook you could stand in.

What I would not undo

  1. 01

    Three.js instead of a generated video

    A walkable boutique is a different deliverable from a teaser. Code lets you enter, click, and keep the file as a real site.

  2. 02

    A fashion brief, not “make a 3D shop”

    RAWSOUL SS26 / Store 001 gave the model a season, a name, and a tone. Generic shop prompts looked like every other AI room.

  3. 03

    Ship the experiment on Vercel

    The point was a URL, not a desktop preview. If it only ran locally, it was still a demo.

The live scene

The live experiment is a Three.js boutique: an entrance you click or scroll through, sound on, a cart, and a RAWSOUL season story. I directed it in Claude Code with Opus 5.5 and published it as a site you can open.

The same motion week also produced a Remotion spot for Monlio and a Figma-to-Remotion deck. This piece is the 3D one — the one you walk through.

What shipped

Claude Opus 5.5 + Three.js

Stack

Walkable boutique, not a video

Format

Live on Vercel

Status

What I’d tighten next

  • I’d lock camera height and movement speed before dressing the room — locomotion is the first thing people feel.

  • Named briefs beat generic “3D store” prompts. I’d start every future world with a season and a store number.

FAQs

A live Three.js boutique directed with Claude Opus 5.5. You enter RAWSOUL SS26 / Store 001 in the browser instead of watching a rendered clip.
No. Opus 5.5 wrote the code that becomes the scene. The motion exists because the world is interactive, not because a video file was generated.
The experiment is live at 3d-boutique.vercel.app. Click or scroll to enter, with optional sound.

Become the Designer Who Can Ship High-End Sites Fast — and Keep 100% of the Revenue 😎

Stop waiting on developers. Start shipping complete websites — and keep all the revenue that comes with it.

Book a 1:1 Session
1:1 sessions and design consultations with Sergei Chyrkov