REUSABLE WORKFLOW FOR INTERACTIVE ROOM DESIGN

Use Blender for detailed assets and final renders, and Three.js for the browser
configurator. Use MCP to inspect and control Blender; keep repeatable modeling
steps in versioned Blender Python scripts.

1. Gather measured dimensions, layout photos, references, and what stays.
   Record measured values separately from assumptions in one design config.
2. Build one accurate neutral scene in Blender. Use named components, real
   units, properly scaled materials, and detailed fixture models.
3. Export reusable GLB components into Three.js. Generate variable geometry
   such as tiles from the shared dimensions; keep fixed surroundings unchanged.
4. Store presets as settings rather than separate scenes. Reuse the same
   settings for the website and any subsequent Blender rebuild or final render.
5. Verify dimensions, openings, material changes, saved-design deletion, and image downloads.
   Compare consistent camera views against the supplied photographs.
6. Explore quickly in the website, then render shortlisted selections in
   Blender Cycles. Keep AI images as visual references, not measured previews.

Improve realism through asset detail, texture scale, material calibration, and
lighting. Budget for differences between real-time and offline rendering.

Current project: dimensions are shared in design.json, but live edits are not
automatically synchronized to the Blender master. The browser supports image
and settings downloads; round-trip configuration rendering is future work.

Use uv for project Python work. Ask before adding dependencies, pin reviewed
stable versions, and keep lockfiles. No extra dependencies are needed here.