Install the complete pack for Claude Code
Run the agent-specific command published by the repository:
npx skills@latest add linegel/threejs-complete-set-of-skill --skill '*' -g -a claude-code -y
This requests every skill, global scope, the Claude Code target, and non-interactive installation. Inspect the command output and the actual Claude Code skill directory after it finishes. A successful package command does not prove that the current agent session discovered the installed files.
Install the complete pack when broad routing is required. threejs-choose-skills chooses from the installed skill inventory and should not be treated as a replacement for its destination skills.
Use the supported manual folder layout
For a manual personal installation, clone the repository and symlink or copy the required skills/<name>/ directories into ~/.claude/skills/. For a project-specific installation, use the project's .claude/skills/ directory.
A symlink keeps one maintained source, while a copied folder becomes an independent version that needs an update policy. Preserve each complete directory from skills/ rather than extracting only SKILL.md; bundled references and agent metadata may be required. Repository examples, labs, reviews, and generated media stay in the checkout and are not installed skill payload.
Do not paste the full pack into CLAUDE.md. Project instructions should state when and where to load skills, while the skill folders retain the detailed technical contract. Existing project rules continue to own generic application architecture and repository workflow.
Verify discovery with broad and focused requests
First test the router without asking for code:
Use $threejs-choose-skills to route a Three.js WebGPU/TSL product viewer that
needs an inspection camera, procedural material response, shadows, final output,
and visual validation. Return selected, deferred, gaps, handoffs, resources,
passes, output, and verification fields used by the route.
Then test one direct owner:
Use $threejs-camera-controls-and-rigs to audit the existing product-inspection
camera. Preserve application UI ownership and report projection, depth,
interaction, and lifecycle assumptions before proposing changes.
The broad result should select the smallest useful skill intersection and report gaps without inventory padding. The focused result should not require the router to rediscover an already-known owner.
Correct common discovery problems
- Files exist but the skill is invisible: verify the actual global or project skill path used by the current Claude Code setup.
- Only the router was installed: install the complete pack or reduce the requested scope to installed owners.
- Manual copy is stale: compare its revision and files with the intended repository source.
- Existing instructions conflict: resolve the project authority explicitly instead of concatenating two incompatible rule sets.
- The agent loads every skill: require a routing result first and pass only selected owner contracts into implementation.
The installed skill pack does not prove native WebGPU support. Record the resolved package, initialize WebGPURenderer, and verify the actual backend before making a canonical WebGPU claim. If WebGPU is unavailable, report the blocker unless the user explicitly asks for fallback teaching.
Know what this setup does not provide
The pack does not include a Claude subscription, hosted runtime, managed support, production assets, or a finished renderer migration. It also does not guarantee that an external installer and every Claude Code release use an identical directory policy. The verification step is therefore part of installation, not optional troubleshooting.