When your Three.js game renders a blank canvas, tanks to 15 FPS on mobile, or ships a 12 MB bundle, this walks you through the diagnosis. It loads checklists for scene debugging, performance profiling, and mobile input issues, then enforces a structured workflow: reproduce, check console errors, verify canvas size and renderer ownership, inspect camera and scene graph, profile draw calls and memory, fix one bottleneck at a time, and re-measure. The checklist ledger stops you from skipping steps during debug sessions. Honest take: the rigid reference-loading requirement feels heavy for quick fixes, but if you're stuck on why shadows disappeared after a refactor or why frame time doubled, the methodical approach pays off.
npx -y skills add majidmanzarpour/threejs-game-skills --skill threejs-debug-profiler --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
JamieMason/syncpack
awslabs/agent-plugins
github/awesome-copilot