What problem does it solve? Three.js codebases frequently suffer from memory leaks, excessive draw calls, transparency artifacts, and disorganized scene graphs. This Skill provides a concrete set of engineering rules, performance targets, and review checklists so AI-generated or hand-written Three.js code stays maintainable and performant. ## Core Features & Use Cases - Rendering Best Practices: Enforces geometry and material reuse, InstancedMesh for repeated objects, centralized animation loops, and proper resource disposal. - Performance Standards: Defines concrete budgets such as under 500 draw calls, 60 FPS on desktop, and triangle limits for mobile and desktop scenes. - Asset Pipeline Guidance: Recommends GLTF/GLB with Draco compression and KTX2 textures, plus Troika text instead of expensive TextGeometry. - Use Case: When asking an AI to build a 3D product configurator, this Skill ensures the generated code reuses materials, disposes resources on removal, limits shadow casters, and organizes the scene into logical groups. ## Quick Start Review my Three.js scene code and refactor it to follow the engineering best practices for geometry reuse, lighting, and memory management.
