Decide whether a Next.js 16 project should reach for WebGPU at all, then wire vgpu in: the .wgsl loader (Turbopack/webpack), a "use client" canvas that survives SSR, a prefers-reduced-motion path the library omits, a headless render snapshot in CI. Non-visual uses too — compute shaders (compute/dispatch, storage ping-pong), pixelDiff for visual regression, gpuFrameTime as a CI perf gate, server-side image generation, vgpu/scene. Triggers: "shader", "WGSL", "WebGPU", "vgpu", "compute shader", "GPU compute", "animated hero", "generative background", "raymarch", "aggiungi uno shader", "sfondo generativo", "calcolo su GPU". Does not restate the vgpu API — that is the first-party generated skill (npx skills add vercel-labs/vgpu) and its MCP. Records stack.shaders; no phase bump. Not for CSS/Motion animation (this is the top rung of that ladder), animated icons, maps, React Native, or WGSL tutorials.
npx vgpu docs / examples / check / doctor loop.transitions. If a cheaper tier does the job, that is the answer./plugin install dev-flow@dev-flow # the whole suite
./install.sh --platform claude # or drop dist/vgpu-shaders.skill into Claude Code