threejs-webgpu — Claude Code skill: features and installation
The threejs-webgpu Claude Code skill helps build or migrate Three.js projects using WebGPURenderer, TSL node materials, and GPU compute. It applies to tasks where renderer backends and device support need explicit testing.
MIT 585 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a claude-codeWhat threejs-webgpu does
The skill guides work on Three.js features built with WebGPURenderer, TSL materials, and GPU compute. It checks the project's installed revision and architecture against the relevant renderer and TSL APIs.
For compute tasks, it covers storage layouts, bounds checks, dispatch sizing, synchronization, and readback. It also addresses asynchronous renderer setup, initialization errors, and device loss. Three.js APIs change quickly, so examples from a different pinned revision can be incompatible.
Custom GLSL, shader patches, and composer effects need deliberate porting; the skill does not treat them as automatically compatible. Testing should cover the requested WebGPU device and each fallback backend promised for the project.
What it helps with
- migrate a Three.js project to WebGPURenderer
- build a material with TSL nodes
- configure GPU compute bounds and synchronization
- handle renderer initialization errors or device loss
Example prompts for the agent
- Migrate this Three.js project to WebGPURenderer.
- Build a TSL material for this scene.
- Set up GPU compute and test the selected backend.
How to install threejs-webgpu
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-webgpu/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-webgpu/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a codex2Manually: put the files in place
.agents/skills/threejs-webgpu/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a cursor2Manually: put the files in place
.cursor/skills/threejs-webgpu/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-webgpu2Manually: put the files in place
.github/skills/threejs-webgpu/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-webgpuManually: put the files in place
.devin/skills/threejs-webgpu/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -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-webgpu
How do I install threejs-webgpu in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-webgpu -a claude-code. The skill file is placed at ~/.claude/skills/threejs-webgpu/SKILL.md.
What does threejs-webgpu do?
It guides Three.js work involving WebGPURenderer, TSL node materials, and GPU compute. It also covers backend testing and renderer initialization failures.
Does threejs-webgpu automatically port custom GLSL?
No. Custom GLSL, shader patches, and composer effects need to be adapted intentionally to supported node and TSL mechanisms.
Source text
SKILL.md · MIT
--- name: threejs-webgpu description: "Build or migrate Three.js WebGPURenderer, TSL node materials, and GPU compute features." --- # WebGPU and TSL 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. Check the installed Three.js exports and matching renderer/TSL documentation first. These APIs evolve quickly; use the project's pinned revision rather than mixing current snippets into an older install. List required features and backend constraints. WebGPURenderer can use a WebGL backend when supported, but backend selection does not guarantee every compute or effect feature works on both. Test the actual selected backend. Do not replace a working WebGLRenderer unless the requested feature or migration warrants it. Follow the revision's asynchronous initialization contract before rendering or capability-dependent setup. Handle initialization failure and unsupported devices with an explicit fallback state. Keep imports consistent with the renderer build to avoid duplicate class/module instances. Express materials through supported node/TSL mechanisms. Port custom GLSL, shader patches, and composer effects intentionally; they are not automatically compatible. For compute, define storage layouts, bounds checks, dispatch sizes, synchronization, and readback frequency. Avoid per-frame CPU readback when data can stay on the GPU. Manage compute buffers, render targets, and backend device loss according to current APIs. Avoid unbounded workload retries after initialization failure. Verify on the requested WebGPU device/browser and any promised fallback backend. Report backend and feature results separately; a browser exposing navigator.gpu is not proof that this scene rendered successfully. ## API reference Consult the [official documentation](https://threejs.org/docs/pages/WebGPURenderer.html) 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