bonsai-impl-clash
Installation
SKILL.md
Bonsai Clash Detection Implementation
Version: Bonsai v0.8.x | IfcClash (from IfcOpenShell v0.8.x) | Blender 4.2.0+ | Python 3.11 Module path:
bonsai.bim.module.clash— NEVERblenderbim.bim.module.clashEngine: IfcClash — frontend for FCL (Flexible Collision Library)
Critical Warnings
- ALWAYS save IFC files to disk BEFORE running clash detection. IfcClash reads files from disk, NOT from Blender's in-memory model.
- ALWAYS define BOTH Group A and Group B in every clash set, even for intra-model checks (e.g., structural vs. MEP in the same file).
- ALWAYS use
filter_groupsto limit clash scope. Unfiltered detection on large models produces excessive runtime and noise. - ALWAYS use
bim.smart_clash_groupfor result sets exceeding 50 clashes. Manual review of hundreds of individual clashes is impractical. - NEVER expect real-time clash checking. Clash detection is a batch operation — there is NO live monitoring.
- NEVER use
collisionmode withallow_touching=Truefor detecting hard overlaps — this generates false positives where elements share surfaces. Useintersectionmode instead. - ALWAYS specify an output path (
.bcfor.json) before executing clash detection. - ALWAYS use
bonsai.*imports. NEVER useblenderbim.*— renamed in 2024 (v0.8.0+).
Related skills
More from openaec-foundation/blender-bonsai-ifcopenshell-sverchok-claude-skill-package
blender-syntax-materials
>
3blender-core-gpu
>
3blender-agents-code-validator
>
3blender-syntax-panels
>
3blender-errors-data
>
3blender-syntax-data
Covers Blender data management including collections, library overrides, asset system, linked libraries, BlendDataLibraries, data block creation and removal, fake users, and data transfer between files. Activates when managing Blender collections, linking/appending data, working with library overrides, or using the asset system.
3