사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/full-stack-skills/threejs-skills --skill threejs-node-tsl시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
When to use this skill
ALWAYS use this skill when the user mentions:
NodeMaterial,TSL, imports fromthree/nodesor WebGPU entry points in docs- Building materials or post effects from nodes instead of string GLSL
WebGPURenderer,PostProcessing(core class) in a node-centric pipeline
IMPORTANT: node-tsl vs materials vs postprocessing
| Situation | Skill |
|---|---|
| Standard PBR tuning, no nodes | threejs-materials |
| TSL graph, NodeMaterial, WGSL path | threejs-node-tsl |
Classic EffectComposer + Pass classes | threejs-postprocessing |
| Node post passes listed under Addons TSL in docs | threejs-node-tsl + threejs-postprocessing awareness |
Trigger phrases include:
- "TSL", "NodeMaterial", "three/nodes", "WebGPU", "node builder"
- "节点材质", "着色语言 TSL"
How to use this skill
- Decide path: WebGPU + nodes vs WebGL + classic materials—do not hybridize blindly.
- Anchor docs: start from Nodes index and TSL.html; use NodeMaterial for material entry.
- Progressive disclosure: keep SKILL.md navigational; long symbol lists live in references/official-links.md and references/tsl-vs-classic.md; see examples/workflow-tsl-entry.md for navigation habits.
- Renderer: enable
WebGPURendererper docs; fall back notes belong in threejs-renderers. - Debugging: use version-stamped examples in three.js repo; avoid copying deprecated import paths.
- Post stack: if user names
PostProcessingcore class vs addon composer, clarify table in threejs-renderers / threejs-postprocessing.
Doc map (official)
| Docs section | Representative links |
|---|---|
| Nodes | https://threejs.org/docs/#Nodes |
| TSL | https://threejs.org/docs/TSL.html |
| NodeMaterial | https://threejs.org/docs/NodeMaterial.html |
| WebGPU renderer | https://threejs.org/docs/WebGPURenderer.html |
Scope
- In scope: Nodes/TSL discovery, architecture, renderer pairing, where to look next, migration hints from ShaderMaterial.
- Out of scope: Pasting entire TSL symbol tables into SKILL.md; guaranteeing API stability across rapid releases—always cite "current docs".
Common pitfalls and best practices
- Three.js node APIs evolve quickly—tie answers to a version or "current docs".
- Do not confuse core
PostProcessingclass with addonsEffectComposer—names collide in conversation. - WGSL vs GLSL expectations differ; TSL abstracts but limits still apply.
- Keep graphs modular; use references for lookup instead of bloating agent context.
Documentation and version
The Nodes index and TSL page are large and fast-moving. Treat https://threejs.org/docs/ as the source of truth for the user’s installed three.js; prefer linking NodeMaterial and WebGPURenderer over paraphrasing long symbol lists.
Agent response checklist
When answering under this skill, prefer responses that:
- Anchor on TSL.html and/or
#Nodesrather than inventing API names. - Contrast threejs-materials (classic) vs node/TSL path explicitly.
- Warn that WebGPU + nodes examples may require recent minors—cite version when known.
- Point to references/tsl-vs-classic.md and references/official-links.md for long lookups.
- Disambiguate core
PostProcessingvs addonEffectComposer(threejs-postprocessing).
References
- https://threejs.org/docs/#Nodes
- https://threejs.org/docs/TSL.html
- https://threejs.org/docs/NodeMaterial.html
- https://threejs.org/docs/WebGPURenderer.html
Keywords
English: tsl, node material, nodes, webgpu, wgsl, three.js shading language, node builder, nodematerial
中文: TSL、节点材质、WebGPU、着色语言、NodeMaterial、three.js