web3d-dev

Shape: static. Three fixed questions with fixed seams — runtime, assets, motion — and one shared contract, the clip canon, duplicated into both skills that need it and checked identical.

web3d-runtime

Use when building or fixing a realtime 3D scene on the web with three.js or React Three Fiber — WebGPURenderer and its WebGL2 fallback, TSL node materials and shaders, GPU compute and particles, post-processing, device loss, the frame loop, profiling and frame-time budgets, and degrading to a calm static state. Leads with the silent failures of r186 before the API. NOT for landing-page heroes and scroll motion (sheleg-design), asset files and budgets (web3d-assets), character animation (web3d-animation), or a Quest headset session (xr-dev).

web3d-assets

Use when a 3D asset must get from a source to a realtime web scene within budget — sourcing, generating or buying models, textures and characters; the glTF pipeline (validate, clean, simplify, KTX2 textures, meshopt or Draco); target budgets; loaders and colour spaces; licences and provenance; and ordering through Asset Foundry when its tools are present, or working by its principles when they are not. NOT for scene code or shaders (web3d-runtime), making things move (web3d-animation), operating a Foundry order in flight (asset-foundry), or Quest store assets (xr-dev).

web3d-animation

Use when something must move in a realtime 3D web scene with three.js or React Three Fiber — character rigs and clips, blending and state transitions, retargeting, root motion and foot sliding, morph targets, crowds and instanced animation, vertex-animation textures, procedural or GPU-driven motion. Carries a two-sided animation protocol: the asset half (rig, clip canon, export, budgets) and the runtime half (clock, mixer, blending, GPU paths, pause, reduced motion). NOT for scroll or UI motion on a page (sheleg-design), rendered video (hyperframes, remotion), or Unity and Unreal animators.