Skip to content
Design
Skill

/ml-for-aec

Computer vision for buildings, image-to-floorplan, generative ML models, performance prediction, structural analysis ML, energy prediction, natural language to design, and point cloud ML for AEC computational design

BOOST
From plugin
computational-design-skills
22318 skills
Install
$ npx -y skills add Abhinavbwj/Claude-skills-for-Computational-Designers --skill ml-for-aec --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/ml-for-aec

Context preview

The summary Claude sees to decide when to auto-load this skill.

Computer vision for buildings, image-to-floorplan, generative ML models, performance prediction, structural analysis ML, energy prediction, natural language to design, and point cloud ML for AEC computational design

SKILL.md

ml-for-aec.SKILL.md
title: Machine Learning for AEC
description: Computer vision for buildings, image-to-floorplan, generative ML models, performance prediction, structural analysis ML, energy prediction, natural language to design, and point cloud ML for AEC computational design
version: 1.0.0
tags: [machine-learning, AI, computer-vision, GAN, diffusion, prediction, classification, point-cloud-ML, NLP, deep-learning]
auto_activate: true
user_invocable: true
invocation: /ml-for-aec

Machine Learning for AEC

Machine learning is reshaping specific domains within Architecture, Engineering, and Construction, though the transformation is uneven. This skill provides a thorough, practitioner-oriented guide to where ML delivers real value in AEC today, the architectures and methods that work, the data challenges that constrain adoption, and practical pipelines for training, deploying, and maintaining ML models in production AEC workflows.

---

1. ML in AEC: Current State

1.1 Where ML Actually Works in AEC Today

ML in AEC is most effective where three conditions converge: (a) sufficient training data exists or can be generated, (b) the task is well-defined with measurable performance metrics, and (c) the cost of errors is manageable or human review is in the loop.

**Proven, deployed applications**:

  • Construction progress monitoring (photo comparison to BIM schedule)
  • Safety monitoring on construction sites (PPE detection, exclusion zones)
  • Defect detection (crack detection in concrete, facade inspections via drone imagery)
  • Document classification (sorting drawings by discipline, type)
  • Energy performance prediction (surrogate models replacing full simulation)
  • Point cloud semantic segmentation (labeling structural elements from LiDAR scans)
  • Cost estimation from early-stage design parameters

**Promising but not yet mature**:

  • Floor plan generation from adjacency programs
  • Automated scan-to-BIM conversion
  • Generative massing from site constraints
  • Structural topology optimization acceleration
  • Natural language to BIM queries

**Overhyped or premature**:

  • Fully autonomous building design from text prompts
  • AI replacing architectural design judgment
  • General-purpose design AI that understands building codes, physics, and aesthetics simultaneously
  • End-to-end text-to-construction-documents

1.2 Data Challenges in AEC

The AEC industry faces unique data challenges that limit ML adoption:

**Small datasets**: Unlike ImageNet (14M images) or web-scale text corpora, AEC datasets are small. A large architecture firm might have 5,000 floor plans in its portfolio. A structural engineering firm might have 2,000 analyzed buildings. These numbers are 3-4 orders of magnitude below what deep learning models typically require.

**Inconsistent labeling**: Building elements are labeled differently across firms, software platforms, and regions. A "wall" in one BIM model might be modeled as a "generic model" in another. Room naming conventions vary wildly. There is no universal taxonomy.

**Domain complexity**: Buildings are multi-physics systems where geometry, structure, thermal behavior, acoustics, daylight, and human experience interact. ML models that capture only one dimension produce solutions that fail on others.

**Proprietary data**: Most building data is proprietary. Firms are reluctant to share project data. Public datasets are limited in size and diversity.

**High-dimensional output**: A floor plan is not a single number or a class label; it is a complex geometric arrangement satisfying dozens of constraints simultaneously. This makes supervised learning difficult because the "ground truth" is itself a design decision, not an objective fact.

1.3 ML Maturity by AEC Subdomain

| Subdomain | ML Maturity | Key Applications | Data Availability | |-----------|-------------|-----------------|-------------------| | Construction safety | High | PPE detection, hazard detection | Moderate (site cameras) | | Defect inspection | High | Crack detection, moisture | Moderate (drone imagery) | | Energy prediction | Medium-High | EUI prediction, load forecasting | Good (simulation data) | | Document processing | Medium | Drawing classification, OCR | Moderate (drawing archives) | | Point cloud processing | Medium | Semantic segmentation, object detection | Growing (LiDAR/photogrammetry) | | Floor plan analysis | Medium | Recognition, evaluation | Limited (CubiCasa5K, RPLAN) | | Structural analysis | Low-Medium | FEA acceleration, damage detection | Limited (simulation data) | | Generative design | Low | Layout generation, massing | Very limited | | Urban analysis | Low-Medium | Land use classification, traffic | Moderate (satellite, GIS) |

1.4 Build vs. Buy Decisions

| Approach | When to Use | Examples | |----------|------------|---------| | **Use off-the-shelf** | Standard CV tasks (object detection, segmentation) with fine-tuning | YOLOv8, Detectron2, Segment Anything | | **Fine-tune pre-trained** | AEC-specific tasks with moderate data (100-10,000 samples) | Fine-tuned ResNet for facade classification, ControlNet for architectural sketches | | **Train from scratch** | Unique data modality or task with no applicable pre-trained model | Custom GNN for floor plan generation, custom PointNet for AEC-specific segmentation | | **Buy commercial** | Mature, productized solutions where accuracy matters and in-house ML capacity is limited | OpenSpace (construction monitoring), Buildots, Avvir |

---

2. Computer Vision for AEC

2.1 Object Detection

Detecting and localizing building elements in images, drawings, or renderings.

**Architectures**:

| Model | Speed | Accuracy | Best For | |-------|-------|----------|----------| | YOLOv8/v9 | Very fast (real-time) | Good | Site safety monitoring, real-time applications | | Faster R-CNN | Moderate | Very good | Drawing element detection, precise localization | | DETR (Detection Transformer) | Moderate | Very good | Complex scenes, variable-

Read more
Ships withcomputational-design-skills

Claude skills for Computational Designers

Get the whole plugin