threejs-debugging — Claude Code skill: what it does and how to install
The threejs-debugging Claude Code skill traces rendering faults in Three.js scenes. It kicks in for blank canvases, missing meshes, color issues, flicker, picking failures, or lost graphics context.
MIT 658 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a claude-codeWhat threejs-debugging does
The skill helps narrow down Three.js rendering failures, from an empty canvas to asset loading errors and lost context. It asks for console output, failed requests, and a minimal reproduction, then points to the diagnostic decision tree in references/diagnostics.md.
Checks cover canvas dimensions, the render loop, camera setup, materials, picking coordinates, and other likely causes. The skill also calls for retesting the action that failed and nearby states that share its code. It follows the project's installed versions and architecture, and avoids unrelated dependency upgrades.
What it helps with
- trace why a Three.js canvas stays blank
- investigate missing meshes or incorrect colors
- pin down flicker in a rendered scene
- debug object picking and context loss
Example prompts for the agent
- Find why the Three.js canvas is blank and walk through the likely causes.
- Investigate the flicker and incorrect color in this scene.
- Work out why clicking an object selects the wrong position.
How to install threejs-debugging
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-debugging/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-debugging/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a codex2Manually: put the files in place
.agents/skills/threejs-debugging/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a cursor2Manually: put the files in place
.cursor/skills/threejs-debugging/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-debugging2Manually: put the files in place
.github/skills/threejs-debugging/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-debuggingManually: put the files in place
.devin/skills/threejs-debugging/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about threejs-debugging
How do I install threejs-debugging in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-debugging -a claude-code. The skill file is at ~/.claude/skills/threejs-debugging/SKILL.md.
What does threejs-debugging do?
It helps diagnose Three.js rendering faults such as blank canvases, missing meshes, color problems, flicker, picking bugs, and context loss. It gathers symptoms and guides checks that narrow down the cause.
How does the skill investigate a blank canvas?
It checks drawing dimensions, the render loop, renderer creation, camera framing, object visibility, and transforms. Swapping in an unlit diagnostic material can help separate lighting faults from geometry issues.
Source text
SKILL.md · MIT
--- name: threejs-debugging description: "Diagnose Three.js black canvases, missing meshes, wrong colors, flicker, picking bugs, and context loss." --- # Rendering Diagnostics Use the project's installed versions and existing architecture. These instructions supplement the user's task; they do not authorize unrelated changes or external actions. Capture the visible symptom, console errors, failed requests, installed versions, backend, and a minimal reproduction before editing. Use [the symptom tree](references/diagnostics.md) to narrow likely causes. For a blank canvas, first verify nonzero container/drawing dimensions, a live render loop, successful renderer creation, camera projection/framing, object visibility/layers, and valid finite transforms. Replace only the subject material with an unlit diagnostic material to distinguish lighting from geometry problems. For asset failures inspect HTTP status, response content, CORS, decoder paths, and build base path. An HTML fallback response with status 200 is not a valid GLB. For color, trace texture classification through lighting, tone mapping, and output conversion. For flicker inspect coplanar geometry, near/far precision, transparency sorting, duplicate render loops, and competing transform writers. For picking verify canvas/view-relative coordinates, matrices, layers, instancing, and shader deformation mismatch. Reduce the failing scene one feature at a time while preserving evidence. Avoid unrelated dependency upgrades or disabling all error checks to make symptoms disappear. When context/device loss occurs, provide a clear recovery path rather than an unbounded renderer recreation loop. Verify the original failing action after the fix and check adjacent states that share the same code. Explain the cause and evidence, not just the changed line. ## API reference Consult the [official documentation](https://threejs.org/docs/) for exact signatures and revision-specific behavior. If documentation access is unavailable, inspect installed types/source and state any remaining uncertainty.
© cesartevisual · MIT · cesartevisual/threejs-skills