aec-core-bim-workflows

Coordinate IFC model creation, enrichment, validation, and geometry workflows across IfcOpenShell, Bonsai, and Blender.

30|4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill aec-core-bim-workflows-impertio-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aec-core-bim-workflows
Source: https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package/tree/main/skills/aec-cross-tech/core/aec-core-bim-workflows
Command: npx skills add https://github.com/Impertio-Studio/Blender-Bonsai-ifcOpenshell-Sverchok-Claude-Skill-Package --skill aec-core-bim-workflows-impertio-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken BIM/IFC outputs by guiding end-to-end workflows that integrate IfcOpenShell, Bonsai, and Blender while enforcing correct execution context, units/contexts, relationship-safe mutations, and spatial hierarchy rules.

Core Features & Use Cases

  • Execution-context guardrails: Selects the right workflow path for standalone IfcOpenShell, Blender-without-Bonsai, or Blender-with-Bonsai so the correct API surface and in-memory model are used.
  • IFC-safe mutation patterns: Ensures all IFC changes use ifcopenshell.api.run() (or Bonsai tool layers) to avoid orphaned/invalid graphs from direct attribute edits.
  • Geometry + placement correctness: Enforces unit assignment and geometric representation contexts before geometry creation, and synchronizes Blender placement back to IFC when Bonsai is active.
  • Spatial hierarchy and property management: Covers spatial containment patterns and property set management across tools, including validation-minded pipelines and batch processing.

Quick Start

Ask Claude to “Create a new IFC4 model from scratch with walls, assign correct units and Body context, generate geometry, then export to Blender and verify spatial containment and required property sets—using ifcopenshell.api.run() for mutations and Bonsai syncing rules when applicable.”

Frequently Asked Questions about aec-core-bim-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an IFC model from scratch using IfcOpenShell and Blender?

To create an IFC model, set up units and geometric representation contexts first, then use ifcopenshell.api.run() for all mutations to ensure spatial hierarchy integrity and valid graph structure. This workflow coordinates IfcOpenShell, Bonsai, and Blender for reliable IFC2X3, IFC4, or IFC4X3 output.

Why does my IFC file have a corrupted spatial hierarchy after editing?

IFC spatial hierarchy corruption typically happens when direct attribute edits bypass relationship management. Use ifcopenshell.api.run() for mutations or Bonsai tool execution layers to maintain graph integrity and preserve spatial containment patterns across your IFC model.

Can I use Bonsai to sync Blender geometry back to an existing IFC model?

Yes, Bonsai synchronizes Blender placement back to IFC when active. The workflow detects execution context to use the correct in-memory model, ensuring geometry extraction and placement correctness while maintaining spatial hierarchy and property set integrity.

What's the best way to batch enrich IFC property sets across multiple models?

Batch property set enrichment requires using ifcopenshell.api.run() for mutations and validating units and geometric contexts beforehand. This approach supports validation-minded pipelines for IFC2X3, IFC4, and IFC4X3 while maintaining spatial hierarchy integrity during batch processing.

Do I need to set up geometric representation context before generating IFC geometry?

Yes, unit assignment and geometric representation contexts must be configured before geometry creation. This prevents failed BIM/IFC production by ensuring correct execution context and placement synchronization when working across IfcOpenShell, Bonsai, and Blender workflows.

Does this IFC workflow support both standalone IfcOpenShell and Blender-integrated BIM authoring?

Yes, execution-context guardrails select the correct workflow path for standalone IfcOpenShell, Blender-without-Bonsai, or Blender-with-Bonsai environments. This ensures the right API surface and in-memory model are used for IFC generation, enrichment, and geometry extraction.