Web 3D Asset Pipeline
Use this skill for shipped 3D assets rather than scene, camera, or gameplay architecture. Preserve established scale, axes, naming, pivots, and material conventions.
Pipeline
- Define the asset's gameplay purpose, visible size, interactions, animation needs, collision role, and target budget.
- Create or acquire the source using the user's requested workflow. Use
generate_canvas_media for saved canvas nodes, generate_3d_asset for standalone assets, or a matching installed reconstruction skill when appropriate.
- Normalize transforms, units, axes, pivots, hierarchy names, and material assignments.
- Ship GLB or glTF 2.0 unless the existing engine has a different established runtime contract.
- Remove unused nodes, duplicate materials, excess geometry, and oversized textures.
- Add collision proxies, LODs, animation clips, or baked-lighting data only when the runtime needs them.
- Integrate through stable asset keys and validate the actual runtime load.
Optimization
- Prefer material and texture reuse over unique resources per mesh.
- Choose geometry compression based on runtime support and decode cost.
- Use KTX2 or BasisU when the loader and asset pipeline already support them.
- Size textures for on-screen use rather than source-art resolution.
- Keep collision meshes simpler than visible geometry.
- Measure before adding LODs or aggressive compression to small assets.
Validation
Check load errors, scale, orientation, pivot behavior, material appearance, animation names, collision alignment, memory or download cost, and disposal. Do not claim visual parity from file metadata alone.
Use ../three-webgl-game/SKILL.md or ../react-three-fiber-game/SKILL.md for runtime scene integration and ../game-playtest/SKILL.md for player-facing verification.
1---2name: web-3d-asset-pipeline3description: Create, prepare, optimize, and integrate browser-game GLB or glTF assets, including transforms, materials, textures, collision, LOD, and runtime validation.4metadata:5 source: https://skillmd.com/skills/whitetowerai/web-3d-asset-pipeline6---78# Web 3D Asset Pipeline910Use this skill for shipped 3D assets rather than scene, camera, or gameplay architecture. Preserve established scale, axes, naming, pivots, and material conventions.1112## Pipeline13141. Define the asset's gameplay purpose, visible size, interactions, animation needs, collision role, and target budget.152. Create or acquire the source using the user's requested workflow. Use `generate_canvas_media` for saved canvas nodes, `generate_3d_asset` for standalone assets, or a matching installed reconstruction skill when appropriate.163. Normalize transforms, units, axes, pivots, hierarchy names, and material assignments.174. Ship GLB or glTF 2.0 unless the existing engine has a different established runtime contract.185. Remove unused nodes, duplicate materials, excess geometry, and oversized textures.196. Add collision proxies, LODs, animation clips, or baked-lighting data only when the runtime needs them.207. Integrate through stable asset keys and validate the actual runtime load.2122## Optimization2324- Prefer material and texture reuse over unique resources per mesh.25- Choose geometry compression based on runtime support and decode cost.26- Use KTX2 or BasisU when the loader and asset pipeline already support them.27- Size textures for on-screen use rather than source-art resolution.28- Keep collision meshes simpler than visible geometry.29- Measure before adding LODs or aggressive compression to small assets.3031## Validation3233Check load errors, scale, orientation, pivot behavior, material appearance, animation names, collision alignment, memory or download cost, and disposal. Do not claim visual parity from file metadata alone.3435Use `../three-webgl-game/SKILL.md` or `../react-three-fiber-game/SKILL.md` for runtime scene integration and `../game-playtest/SKILL.md` for player-facing verification.