What problem does it solve? Developers using the Three.js WebGPU renderer frequently hit runtime errors from missing async initialization, unsupported browsers, or accidentally using GLSL shaders and WebGL-only APIs like EffectComposer. This Skill provides correct patterns, API references, and anti-patterns to build WebGPU scenes without these pitfalls. ## Core Features & Use Cases - WebGPURenderer Setup: Correct async initialization, browser feature detection with WebGPU.isAvailable(), and automatic WebGLRenderer fallback for unsupported browsers. - TSL and Node Materials: Full reference for Three Shading Language types, operators, geometry/camera nodes, control flow, and node-based material inputs replacing raw GLSL. - Compute Shaders and Post-Processing: GPU compute via computeAsync with storage buffers and atomics, plus the PostProcessing class with bloom, FXAA, and other TSL-based effects. - Use Case: When migrating a WebGL Three.js scene to WebGPU, follow the six-step migration guide to swap imports, materials, post-processing, and animation loops correctly. ## Quick Start Ask the AI to create a Three.js WebGPU scene with a spinning cube, including browser support detection and a WebGL fallback.