JSON-driven Three.js scene runtime: declarative 3D scenes, builders, and handlers.

Static textures, models, fonts, audio, and scene JSON for ThreeJSON

Ready-made, styled React components for ThreeJSON scene-host apps: mesh export dialog, export warnings, and other shared UI. Built on @threejson/react (headless hooks) + @threejson/host-kit.

React hooks and UI primitives for an embeddable conversational ThreeJSON scene workbench.

Framework-neutral conversational ThreeJSON scene authoring: routing, generation and adjustment orchestration, settings, progress contracts, and persistence adapters.

Framework-agnostic, no-shell logic for building ThreeJSON scene editors: the editor command layer (registry + command specs), the AI scene-update flow (command/JSON round-trips), and the domain-edit session (drill-in, child-transform baselines, undo). No

Embeddable ThreeJSON scene player runtime: mount to a canvas, load/dispose scenes, transport (play/pause), highlight, editor-preview protocol, playlist IndexedDB storage. No full app shell (top bar, playlist list UI, settings modal) — that stays in tools/

Thin React bindings over ThreeJSON's framework-agnostic host/player kits: <SceneViewport />, useScenePlayer(), useHostI18n(), usePlayerSettings(). No business shell — app UI stays in the app.

Framework-agnostic scene-host runtime shared by ThreeJSON's editor/player/shower/threebox apps: settings schemas/stores, AI turn orchestration, scene file IO, i18n, and viewport helpers. No React or other UI framework dependency.