bim-clash-detection

Solid

BIM clash detection skill for identifying and managing coordination conflicts between disciplines

AI & Automation 1,160 stars 71 forks Updated today MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
68
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# BIM Clash Detection Skill ## Purpose The BIM Clash Detection Skill identifies and manages coordination conflicts between building disciplines including hard clashes, soft clashes, and workflow clashes. ## Capabilities - Hard clash detection (physical interference) - Soft clash detection (clearance violations) - Workflow clash detection (sequencing) - Clash grouping and prioritization - Resolution tracking - Report generation with visualization - BCF format export - Multi-model coordination ## Usage Guidelines ### When to Use - Coordinating multi-discipline models - Identifying design conflicts - Managing clash resolution - Documenting coordination issues ### Prerequisites - BIM models available - Coordination matrix defined - Tolerance settings established - Resolution workflow defined ### Best Practices - Run regular detection cycles - Prioritize clashes by impact - Track resolution status - Document resolutions ## Process Integration This skill integrates with: - BIM Coordination - Shop Drawing Review ## Configuration ```yaml bim-clash-detection: clash-types: - hard - soft - clearance tolerances: hard: 0 soft: 50 # mm clearance: 100 # mm output-formats: - html - bcf - json ``` ## Output Artifacts - Clash reports - BCF issue files - Resolution logs - Coordination matrices

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
4 months ago
Last Updated
today
Language
JavaScript
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

check-bin-obj-clash

Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. Only activate in MSBuild/.NET build context. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, missing outputs in multi-project builds, multi-targeting builds where project.assets.json conflicts. Diagnoses when multiple projects or TFMs write to the same bin/obj directories due to shared OutputPath, missing AppendTargetFrameworkToOutputPath, or extra global properties like PublishReadyToRun creating redundant evaluations. DO NOT USE FOR: file access errors unrelated to MSBuild (OS-level locking), single-project single-TFM builds, non-MSBuild build systems. INVOKES: dotnet msbuild binlog replay, grep for output path analysis.

3,219 Updated today
dotnet
AI & Automation Listed

bim-scripting

Revit API fundamentals, Dynamo for Revit, pyRevit framework, IFC schema and openBIM, model checking, automated documentation, clash detection, and BIM interoperability tools for AEC computational design

1 Updated today
marcinfinitesimal533
AI & Automation Solid

building-code-checker

Building code compliance checking skill for IBC occupancy, construction type, and area requirements

1,160 Updated today
a5c-ai
AI & Automation Listed

merge-conflict-resolution

Detect, classify (porcelain status; complexity: trivial, semantic, structural, delete-modify), and resolve git merge conflicts through per-file strategy selection (accept-ours, accept-theirs, manual-merge, rebase), manual conflict hunk parsing, and post-resolution verification (orphaned markers, build, tests). Use when a branch has conflicts with its merge target or when rebasing onto an updated base. This skill MUST be consulted because silently dropping changes is non-negotiable; every conflict resolution must account for both sides.

5 Updated 3 days ago
synaptiai
AI & Automation Solid

ifc-model-analyzer

IFC model analysis skill for validation, property extraction, and model comparison

1,160 Updated today
a5c-ai