webgpu-claude-skill — Claude Code skill: WebGPU, TSL and WGSL
Gives the agent working knowledge of Three.js on WebGPU: TSL node materials, compute shaders, post-processing, WGSL. Useful when a scene needs GPU compute.
MIT 202 installs ★ 35 updated 2026-10-21
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a claude-codeWhat webgpu-claude-skill does
webgpu-claude-skill teaches the agent how Three.js renders through WebGPU. It covers WebGPU renderer setup, node materials in TSL, compute shaders for work off the render path, post-processing passes and WGSL shaders, with a cheatsheet to look things up. It targets Three.js r183 and later.
The installed skill answers to the name webgpu-threejs-tsl, while the catalogue entry stays behind as a pointer. Cursor rules ship in the upstream repo, and installing the skill does not bring them along.
Plain Three.js scenes that never touch WebGPU are out of scope, and so is GLSL work on WebGL. The manifest says MIT; the repo carries no LICENSE file.
What it helps with
- set up the WebGPU renderer in a Three.js scene
- author a node material in TSL
- run a compute shader for work off the render path
- chain post-processing passes on WebGPU
- wire an existing WGSL shader into the pipeline
Example prompts for the agent
- Set up a Three.js scene with the WebGPU renderer and a TSL node material.
- Port this material to TSL and add a WebGPU post-processing pass.
- Write a WGSL compute shader that updates particle positions on the GPU.
How to install webgpu-claude-skill
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a claude-code2Manually: put the files in place
~/.claude/skills/webgpu-claude-skill/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/webgpu-claude-skill/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a codex2Manually: put the files in place
.agents/skills/webgpu-claude-skill/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a cursor2Manually: put the files in place
.cursor/skills/webgpu-claude-skill/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install podo/design-agent-skills skills/webgpu-claude-skill2Manually: put the files in place
.github/skills/webgpu-claude-skill/SKILL.md1Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a gemini-cli2Platform CLI
gemini skills install https://github.com/podo/design-agent-skills --path skills/webgpu-claude-skillManually: put the files in place
.devin/skills/webgpu-claude-skill/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add podo/design-agent-skills --skill webgpu-claude-skill -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 webgpu-claude-skill
How do I install webgpu-claude-skill in Claude Code?
Run npx skills add podo/design-agent-skills --skill webgpu-claude-skill -a claude-code. The skill file lands at ~/.claude/skills/webgpu-claude-skill/SKILL.md.
What does webgpu-claude-skill do?
It gives the agent knowledge of WebGPU inside Three.js: renderer setup, TSL materials, compute shaders, post-processing and WGSL. Built for Three.js r183 and newer.
Does installing the skill bring the Cursor rules?
No. Those rules live in the upstream repository, and the skills install does not copy them, so Cursor users pull them separately.
Source text
SKILL.md · MIT
--- name: webgpu-claude-skill description: | WebGPU-enabled Three.js skill covering TSL (Three.js Shading Language), node-based materials, GPU compute shaders, post-processing effects, and WGSL integration. Aligned with Three.js r183+. triggers: - "WebGPU" - "TSL Three.js" - "GPU compute shaders" - "WGSL" - "webgpu-claude-skill" das: type: skill category: creative-3d upstream: "https://github.com/dgreenheck/webgpu-claude-skill" upstream_path: "skills/webgpu-threejs-tsl/SKILL.md" version: latest install: false --- # webgpu-claude-skill > Catalogue stub — full skill: [dgreenheck/webgpu-claude-skill](https://github.com/dgreenheck/webgpu-claude-skill) <!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block --> ## Decision tree 1. **Is the full skill already installed?** Upstream names this skill `webgpu-threejs-tsl`, so it installs next to this pointer (the pointer is not replaced). - Global: `f=~/.agents/skills/webgpu-threejs-tsl/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - Project: `f=.agents/skills/webgpu-threejs-tsl/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer"` - `installed` → the skill is installed as `webgpu-threejs-tsl`, invoke it and proceed - `pointer` → go to step 2 2. **Detect scope, then install:** ```bash [ -e ~/.agents/skills/webgpu-claude-skill ] && echo "global" || echo "project" ``` **Global:** ```bash npx skills add dgreenheck/webgpu-claude-skill --skill webgpu-threejs-tsl -g -y ``` **Project:** ```bash npx skills add dgreenheck/webgpu-claude-skill --skill webgpu-threejs-tsl -y ``` > **Claude Code:** send a command as a chat message starting with `!` to run it without leaving the conversation. **Claude Code plugin route:** ``` /plugin marketplace add dgreenheck/webgpu-claude-skill /plugin install webgpu-threejs-tsl@webgpu-threejs-tsl ``` **Heads-up** - **License:** MIT per the plugin manifest; no LICENSE file in the repo <!-- das:install:end --> ## Invoke after install - Skill name: `webgpu-threejs-tsl` - Trigger phrases: "WebGPU", "TSL Three.js", "GPU compute shaders", "WGSL" ## What it does Provides deep knowledge of the WebGPU rendering pipeline within Three.js (r183+), including WebGPU renderer setup, the Three.js Shading Language (TSL) for node-based material authoring, GPU compute shaders for non-rendering workloads, advanced post-processing with WebGPU passes, and WGSL shader integration, with a quick-reference cheatsheet. The upstream repo also ships matching Cursor rules, which the skills install does not copy. Use when building high-performance 3D experiences that require GPU compute or next-generation shader authoring. ## When NOT to use - Standard Three.js scenes without WebGPU — use `cloudai-threejs` instead - GLSL shader work on WebGL — use a standard Three.js skill instead - Architecture/BIM workflows — use `threejs-claude-skill-package` instead
© podo · MIT · podo/design-agent-skills