Three.js Skills for Loom
Loom owns delivery state, task planning, repair, and handoff. Start non-trivial
work through @loom plan; treat the specialist skills below as technical and
verification guidance, not as an alternative workflow.
Choose the smallest skill
| Work |
Skill |
| Game design, core loop, input, camera, physics, or game feel |
threejs-gameplay-systems |
| Models, materials, shaders, lighting, or render quality |
threejs-aaa-graphics-builder |
| HUDs, menus, overlays, touch controls, or responsive game UI |
threejs-game-ui-designer |
| Blank canvas, runtime errors, asset loading, input, or performance |
threejs-debug-profiler |
| Playtesting, screenshots, canvas diagnostics, or release checks |
threejs-qa-release |
| Explicit 3D, image, or audio asset generation |
threejs-3d-generator, threejs-image-generator, or threejs-audio-generator |
Do not load every specialist for a small fix. Browser games with visual or
interactive acceptance criteria should finish with the relevant browser
evidence recorded in the Loom task result.
Delivery loop
For a new game or a substantial change, begin in the project root:
@loom plan Build a Three.js game with a playable movement loop and verified browser controls
@loom continue
Run the project's build and focused behavior checks first. Use canvas
inspection, screenshots, or playtests only when they are relevant to the task.
When a specialist skill recommends a workflow that conflicts with a Loom MCP
request, follow the MCP request.
Third-party material
The specialist skill directories were imported from an MIT-licensed upstream
skill pack. Its license is retained in UPSTREAM_LICENSE.
1---2name: threejs3description: Build, debug, and verify Three.js browser games through Loom. Use only when the request mentions Three.js, React Three Fiber, WebGL game work, or the active workspace declares a three, @react-three/fiber, or @react-three/drei dependency. Do not load for unrelated web projects.4---56# Three.js Skills for Loom78Loom owns delivery state, task planning, repair, and handoff. Start non-trivial9work through `@loom plan`; treat the specialist skills below as technical and10verification guidance, not as an alternative workflow.1112## Choose the smallest skill1314| Work | Skill |15| --- | --- |16| Game design, core loop, input, camera, physics, or game feel | `threejs-gameplay-systems` |17| Models, materials, shaders, lighting, or render quality | `threejs-aaa-graphics-builder` |18| HUDs, menus, overlays, touch controls, or responsive game UI | `threejs-game-ui-designer` |19| Blank canvas, runtime errors, asset loading, input, or performance | `threejs-debug-profiler` |20| Playtesting, screenshots, canvas diagnostics, or release checks | `threejs-qa-release` |21| Explicit 3D, image, or audio asset generation | `threejs-3d-generator`, `threejs-image-generator`, or `threejs-audio-generator` |2223Do not load every specialist for a small fix. Browser games with visual or24interactive acceptance criteria should finish with the relevant browser25evidence recorded in the Loom task result.2627## Delivery loop2829For a new game or a substantial change, begin in the project root:3031```text32@loom plan Build a Three.js game with a playable movement loop and verified browser controls33@loom continue34```3536Run the project's build and focused behavior checks first. Use canvas37inspection, screenshots, or playtests only when they are relevant to the task.38When a specialist skill recommends a workflow that conflicts with a Loom MCP39request, follow the MCP request.4041## Third-party material4243The specialist skill directories were imported from an MIT-licensed upstream44skill pack. Its license is retained in `UPSTREAM_LICENSE`.
valkor-ai