Own the complete non-game 3D application outcome. Do not invent game objectives, scoring, failure, or progression unless the experience genuinely needs them.
Read references/app-patterns.md for the matching application archetype.
For imported-model orientation, manipulation, simulation, terrain, or other
spatially complex work, read ../../references/spatial-contracts.md.
Route The Work
| Need | Skill |
|---|---|
| Models, composition, materials, lighting, shaders, VFX | ../threejs-visual-systems/SKILL.md |
| Cameras, controls, picking, selection, configuration, manipulation, UI | ../threejs-interaction-systems/SKILL.md |
| Rendering, loading, input bugs, profiling, optimization | ../threejs-debug-profiler/SKILL.md |
| Browser QA, visual regression, production release | ../threejs-qa-release/SKILL.md |
| Game mechanics or game feel inside a mixed experience | ../threejs-gameplay-systems/SKILL.md |
Workflow
- Inspect the existing stack, scene lifecycle, assets, interactions, UI, data ownership, loading states, target devices, and deployment constraints.
- Define the app brief: user goal, primary 3D subject, essential interactions, camera/control model, state or data flow, loading/error behavior, outputs, and performance budget.
- Establish one owner for renderer, scene, camera, animation frame, resize, asset lifecycle, and disposal.
- Use Mint MCP through
../../references/mint-mcp-assets.mdwhen production assets are needed. Store ordinary artifacts at stable project paths; stream world RAD manifests through../../references/mint-world-splats.md. - Implement the smallest complete user journey before secondary polish.
- Apply visual systems and interaction guidance appropriate to the archetype.
- Reproduce and measure defects or performance issues before optimizing.
- Verify the complete journey, responsive behavior, loading/error states, and production build.
Completion Gates
- The primary user journey works through real input.
- Camera and controls match the task and do not fight each other.
- Loading, empty, unsupported, and error states are handled when applicable.
- Selection, configuration, manipulation, playback, or navigation state has one owner and visible feedback.
- Assets load from stable local paths or the deliberate remote world runtime with correct scale, orientation, materials, animation, bounds, and disposal.
- Desktop and mobile behavior is verified when mobile is in scope.
- Build/typecheck, browser errors, canvas pixels, screenshots, and changed risky paths pass.
- Visual quality and renderer cost meet the requested bar.
Final Response
Lead with the completed user journey. Report controls, state ownership, changed files, Mint links and artifact paths, screenshots, verification, performance evidence, deployment assumptions, and remaining risks.