threejs-debug-profiler
Skill0 starsChanged 5 months agoMITView on GitHub
Debug and profile Three.js browser games. Combines scene debugging, render/runtime/loading/animation/resize/mobile input fixes, performance profiling, draw calls, triangles, textures, memory, shader/post-processing cost, bundle size, and mobile DPR/input issues.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- iberi22/skillstheir own version, first seen Oct 15, 2026
- majidmanzarpour/threejs-game-skillstheir own version, first seen Sep 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- majidmanzarpour/threejs-game-skills★ 2.2ksame name
- iberi22/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- threejs-3d-generatorSkill
- threejs-aaa-graphics-builderSkill
- threejs-audio-generatorSkill
- threejs-game-directorSkill
- threejs-gameplay-systemsSkill
- threejs-game-ui-designerSkill
- threejs-image-generatorSkill
- threejs-qa-releaseSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Read console/page/network errors.
- Distinctive: line 20
Check canvas display size and drawing-buffer size.
- Very specific: line 21
Check renderer/context/loop ownership.
- Distinctive: line 22
Check camera, aspect, near/far, lights, materials, fog, scene contents, transforms.
- Very specific: line 23
Check asset paths/loaders/CORS/base path.
- Distinctive: line 24
Check animation delta units, physics/update order, fixed timestep, collider/body ownership, input listeners, pointer/touch behavior, …
- Distinctive: line 26
Verify browser screenshot, nonblank canvas, console/page errors, and broken path.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Three.js Debug Profiler
Purpose
Find root causes and optimize measured bottlenecks without breaking playability.
Debug Workflow
Load references/debug-profile-checklists.md as the first action when debugging render/runtime/mobile issues, asset loading, audio loading/playback, animation, resize, input, blank canvas, physics/collision bugs, or profiling performance. Track it in a reference ledger with yes/no, path, and failure reason. Do not mark the debug/profile phase complete while this reference is skipped for debug or profiling work.
Load references/checklists/scene-debugging.md for render/runtime bug diagnosis, references/checklists/performance-profile.md for profiling work, and references/checklists/mobile-input.md for mobile render/input issues. Load references/prompt-templates.md only when the user asks for reusable debug/profile prompts or a task template.
- Reproduce locally.
- Read console/page/network errors.
- Check canvas display size and drawing-buffer size.
- Check renderer/context/loop ownership.
- Check camera, aspect, near/far, lights, materials, fog, scene contents, transforms.
- Check asset paths/loaders/CORS/base path.
- Check animation delta units, physics/update order, fixed timestep, collider/body ownership, input listeners, pointer/touch behavior, resize, and audio context unlock/decode errors when audio is involved.
- Fix root cause in owning module.
- Verify browser screenshot, nonblank canvas, console/page errors, and broken path.
Performance Workflow
- Reproduce in correct build mode.
- Record baseline: FPS/frame time, draw calls, triangles, geometries, textures, memory, bundle.
- Identify CPU/GPU/memory/network bottleneck.
- Optimize one thing at a time: instancing, shared resources, culling, LOD, DPR cap, cheaper shadows/post, texture discipline.
- Re-measure same scenario and verify visuals/playability.
Final Response
Lead with root cause or bottleneck. Report the reference ledger, checklist items used, files changed, baseline/post metrics, commands, screenshots/artifacts, broken paths retested, and residual risks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

