What problem does it solve? Building IFC/BIM viewers in the browser is error-prone: developers often use the deprecated web-ifc-three bridge, violate AGPL-3.0 licensing unknowingly, leak WASM memory by never closing models, or crash the browser by loading large IFC files without streaming. This Skill provides correct, current patterns for loading, rendering, and managing IFC models in Three.js. ## Core Features & Use Cases - Two implementation approaches: Low-level geometry extraction with web-ifc (MIT) for full control, or high-level viewer setup with @thatopen/components v3.x including fragments, highlighting, and clipping planes. - Geometry conversion: Converts web-ifc interleaved vertex data and placement transforms into Three.js BufferGeometry meshes with correct materials and colors. - Memory management: Enforces model closing, geometry disposal, and storey-based streaming strategies for files from 10MB to 200MB+. - Use Case: A developer building a web-based BIM viewer needs to load a 120MB IFC file, display its spatial tree by storey, and let users click elements to inspect properties without crashing the browser tab. ## Quick Start Ask the AI to load an IFC building model into a Three.js scene using web-ifc with proper WASM setup and memory cleanup.
