threejs-particles — Claude Code skill: what it does, how to install
Claude Code skill for building Three.js particle systems, point clouds, and GPU simulations.
MIT 648 installs ★ 26 updated 2026-09-10
npx skills add cesartevisual/threejs-skills --skill threejs-particles -a claude-codeWhat threejs-particles does
The skill guides the coding agent when setting up particle counts, lifetimes, spawn rates, and interaction models. It defines rules for choosing between Points, instanced geometry, and GPU compute paths based on visual requirements and measured bottlenecks.
Instructions cover fixed-capacity buffer allocation, typed array updates, and overdraw management to avoid per-frame object churn. For GPU simulations, the skill configures ping-pong resources, initial conditions, precision requirements, and backend support without unnecessary CPU readbacks.
What it helps with
- build Three.js particle systems
- configure GPU particle simulations
- optimize point clouds and buffers
- manage point size and transparency overdraw
Example prompts for the agent
- Add a GPU-simulated particle system to the scene
- Create a point cloud with spatial chunk streaming
- Set up fixed-capacity particle buffers without frame churn
How to install threejs-particles
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-particles -a claude-code2Manually: put the files in place
~/.claude/skills/threejs-particles/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/threejs-particles/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-particles -a codex2Manually: put the files in place
.agents/skills/threejs-particles/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-particles -a cursor2Manually: put the files in place
.cursor/skills/threejs-particles/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cesartevisual/threejs-skills skills/threejs-particles2Manually: put the files in place
.github/skills/threejs-particles/SKILL.md1Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-particles -a gemini-cli2Platform CLI
gemini skills install https://github.com/cesartevisual/threejs-skills --path skills/threejs-particlesManually: put the files in place
.devin/skills/threejs-particles/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cesartevisual/threejs-skills --skill threejs-particles -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-particles
How to install threejs-particles in Claude Code?
Run npx skills add cesartevisual/threejs-skills --skill threejs-particles -a claude-code, then use ~/.claude/skills/threejs-particles/SKILL.md.
What does threejs-particles do?
It instructs the agent on building particle systems, point clouds, and GPU simulations in Three.js while keeping memory usage and rendering performance in check.
What approaches does the skill enforce?
It dictates fixed-capacity buffer allocation, typed array updates, ping-pong resource management for GPU compute, and spatial chunk streaming for large point datasets.
Source text
SKILL.md · MIT
--- name: threejs-particles description: "Build Three.js particle systems, point clouds, large repeated datasets, and CPU or GPU simulations." --- # Particles and Large Data 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. Define particle count, lifetime, spawn rate, interaction, and target devices before choosing Points, instanced geometry, or a GPU simulation. Choose representation based on appearance and measured bottlenecks; many transparent pixels can cost more than many vertices. Allocate fixed-capacity buffers, recycle slots, and update typed arrays without per-frame object churn. Use deterministic seeds when reproducibility or visual tests matter. Keep application identifiers independent of reused buffer slots. Budget point size and transparent overdraw. Point-size limits vary by device; use quads when larger sprites are necessary. Sort or approximate transparency intentionally. For GPU deformation, maintain conservative bounds and matching interaction behavior. For GPU simulation, define ping-pong resources, initial conditions, precision requirements, and backend support. Reset both simulation state and presentation time. Avoid unnecessary readbacks; if CPU interaction is needed, use coarse proxies or a deliberate sampling strategy. For point-cloud datasets, stream spatial chunks, cull by chunk, and adjust detail to projected size. Preserve coordinate origins and units rather than uploading huge world coordinates blindly. Verify count changes, maximum lifetime, resizing, reset reproducibility, sustained memory use, mobile fill rate, and fallback behavior without the compute path. ## API reference Consult the [official documentation](https://threejs.org/docs/pages/Points.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