threejs-performance teaches an agent to measure a three.js scene before changing it. It reads renderer.info for draw calls, triangles, geometries, textures and compiled programs, and explains that the counters reset on every render call.
The optimization sections cover merging, instancing, batching and level of detail, fill rate, shadows, CPU work per frame, shader compile stalls and GPU compute for particles, on WebGL or WebGPU with TSL.
What You Get
- A quick start that logs renderer.info counters each frame
- A Measure First section with a console table of render and memory stats
- Techniques for fewer draw calls using merging, instancing, batching and level of detail
- Guidance on fill rate, shadows, CPU work and shader compile stalls
- GPU compute for particles on WebGPU with TSL
Common Use Cases
- Finding out why a scene runs slowly
- Cutting draw calls in a scene with many objects
- Reducing GPU memory use from textures and geometry
- Avoiding frame hitches when new materials compile
- Moving heavy particle updates to the GPU
What Makes It Unique
It orders the work as measure first, then fix what the counters point at, and it explains how to read the counters correctly. The other skills in the set each carry a cost note for their topic and link here. It is pinned to r186.
Under The Hood
The skill is a single SKILL.md of explanation and JavaScript examples, with no scripts, and it tells the agent to run no commands. The agent reads it and writes three.js code into your project, including code that logs statistics to the browser console. It fetches nothing and writes no files itself.