3d-viewer

Guide three.ws development by mapping viewer and agent responsibilities to repository areas.

5|Updated May 2, 2026
One-click install
npx skills add https://github.com/nirholas/three-ui --skill 3d-viewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 3d-viewer
Source: https://github.com/nirholas/three-ui/tree/main/.github/skills/3d-viewer
Command: npx skills add https://github.com/nirholas/three-ui --skill 3d-viewer

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about 3d-viewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a three.js 3D viewer and agent runtime project workflow?

Structure a three.js 3D viewer and agent runtime workflow by mapping viewer and agent responsibilities to correct repository areas. Separate the pure browser app from the serverless API and contract code to change the right place the first time.

Where should I modify GLB loading UI behavior versus agent skill wiring?

Modify GLB loading UI behavior in src/viewer/*, while adjusting agent skill wiring in src/skills/ or src/runtime/scene.js. Mapping these boundaries prevents architectural confusion when developing the 3D agent platform.

What is the boundary between the pure three.js viewer and the runtime scene controller?

The boundary separates the pure three.js viewer from the runtime scene controller that wraps it. Understanding this viewer versus agent separation prevents architectural confusion and ensures changes are made in the correct repository areas.

How do I validate ESM-only constraints and Vercel API builds in a 3D agent project?

Validate ESM-only constraints and Vercel API builds by running command-based verification using node --check and npm run build. This ensures deterministic workflow requirements and repo conventions are satisfied before reporting results.

Can I use this workflow to debug both the browser app and serverless API?

Yes, you can use this workflow to debug both the browser app and serverless API. It guides development across the Vercel API, contracts, and SDK, mapping validation steps and repo conventions to the correct areas for safe, repeatable changes.