What problem does it solve?
This Skill solves the problem of getting lost in a fast-moving three.ws codebase by providing a single, practical project workflow for developing and debugging the 3D viewer plus its agent runtime.
Core Features & Use Cases
- End-to-end project workflow: navigate how the browser app, Vercel API, contracts, and SDK relate so you can change the right place the first time.
- Viewer vs agent separation: understand the boundary where the pure three.js viewer is wrapped by the runtime scene controller, preventing architectural confusion.
- Safe, repeatable change process: follow repo conventions and commands to validate changes with node checks and builds before reporting results.
Use case: You want to modify UI behavior when loading a GLB model and also adjust agent skill wiring—use this workflow to identify whether the change belongs in src/viewer/*, src/runtime/scene.js, src/skills/, or api/.
Quick Start
Use the 3d-viewer skill to tell an AI exactly which feature you want to change and where you think it lives, and ask it to propose the safest PR plan with the relevant files and commands to validate.