building-envelope-performance
Skill39 starsChanged 23 days agoMITView on GitHub
Develop and review facade/roof/foundation envelope strategies for water, air, vapor, thermal, solar, acoustic and durability performance. Use for wall/roof assemblies, glazing, thermal bridges, condensation risk, waterproofing, interfaces, facade details and envelope QA.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectural-drawing-generationSkill
- architecture-orchestratorSkill
- architecture-programmingSkill
- architecture-red-teamSkill
- area-quantity-auditSkill
- autocad-dwg-workflowSkill
- cad-bim-automationSkill
- civil-site-designSkill
- concept-design-reviewSkill
- concept-schematic-designSkill
- construction-administrationSkill
- construction-documentationSkill
- cost-planning-value-engineeringSkill
- drawing-qaSkill
- handover-fm-postoccupancySkill
- interior-fitout-designSkill
- life-safety-accessibilitySkill
- materials-specificationsSkill
- mep-coordinationSkill
- openbim-ifc-coordinationSkill
- precedent-researchSkill
- presentation-reviewSkill
- revit-workflowSkill
- rhino-grasshopper-workflowSkill
- site-analysis-feasibilitySkill
- site-regulation-researchSkill
- structural-coordinationSkill
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.
- Distinctive: line 40
Do not certify facade, waterproofing, hygrothermal, fire or structural performance.
- Distinctive: line 41
Do not fabricate manufacturer values or substitute generic details for project-specific engineering.
- Distinctive: line 45
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Building Envelope Performance
Coordinate continuous performance layers and buildable interfaces; source product and climate data rather than inventing it.
Preflight
- Climate/location, indoor design conditions, exposure, orientation, assembly geometry and structural support.
- Target thermal/air/water/acoustic/fire performance, product data, applicable standards and consultant inputs.
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.
Workflow
- Draw continuity diagrams for water, air, vapor and thermal control layers through representative interfaces.
- Review openings, parapets, balconies, roofs, foundations and material transitions for drainage, movement, thermal bridges and sealant/flashing continuity.
- Evaluate preliminary thermal/moisture risks using verified material properties and climate assumptions; request specialist analysis when needed.
- Translate the strategy into outline details, performance requirements and mock-up/testing questions.
Deliverables
- Envelope control-layer diagrams
- Interface/detail risk register
- Performance requirement matrix
- Testing/mock-up and consultant questions
Verification
- Control layers remain continuous across sections/details and product properties are sourced.
- Condensation/U-value/acoustic/fire statements identify method, inputs and limitations.
For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.
Professional boundaries
- Do not certify facade, waterproofing, hygrothermal, fire or structural performance.
- Do not fabricate manufacturer values or substitute generic details for project-specific engineering.
If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.
On-demand evidence and practice references
Load only the relevant reference. These are original review prompts, not binding code or full-book extraction.
- B01: envelope continuity
- B02: system completeness
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.