What it does. Treat the model's Three.js knowledge and official documentation as prerequisites. Load only the expertise that changes the visual result.
This pack goes beyond procedural guidance: its working examples and supporting assets contain much of its practical implementation value. When they are relevant, give them particular attention.
Highlights
- Do not load a skill for API setup alone. Inspect the installed Three.js version and use official docs.
- Do not route “make it beautiful” directly to post-processing. Find the missing authored system.
- Prefer one strong, inspectable visual rule over several independent noise layers.
- When adapting a supplied reference, preserve the mechanism that creates its character. Do not reduce it to a generic effect category.
- Keep object-space, world-space, and screen-space systems separate unless the composition explicitly requires coupling.
When to use it. Route ambitious Three.js graphics work to the smallest expert skill set. Use for new visual experiences, graphics rewrites, reference matching, or requests spanning geometry, materials, atmosphere…
Install
npx skills add scottstts/Threejs-Awesome-Graphics-Agent-Skills --skill threejs-skill-router
Or copy the skill folder manually:
git clone https://github.com/scottstts/Threejs-Awesome-Graphics-Agent-Skills.git
cp -r Threejs-Awesome-Graphics-Agent-Skills/skills/threejs-skill-router/ ~/.claude/skills/threejs-skill-router
Source: scottstts/Threejs-Awesome-Graphics-Agent-Skills — 778 stars, MIT, last pushed 2026-08-27.
