sustainability-daylight-energy
Skill39 starsChanged 24 days agoMITView on GitHub
Develop evidence-based passive-design, daylight, solar/shading, energy, embodied-carbon, water and resilience strategies for architecture. Use for climate analysis, sustainability targets, daylight/solar studies, early energy/carbon comparisons and certification coordination.
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
- building-envelope-performanceSkill
- 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
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use measurable targets and verified methods.
- Very specific: line 15
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.
- Distinctive: line 33
Every metric states source, method, units and assumptions.
- Very specific: line 40
Do not claim LEED/BREEAM/Passivhaus/WELL or other certification without the responsible assessor/process.
- Distinctive: line 41
Do not present simplified calculations as code compliance or final energy modelling.
- 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
Sustainability, Climate, Daylight & Energy
Use measurable targets and verified methods; distinguish early design indicators from formal simulation/certification results.
Preflight
- Location/climate file or authoritative climate data, orientation, massing/envelope assumptions, occupancy/use and project sustainability targets.
- Available energy/daylight/LCA model outputs, material quantities, certification framework 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
- Translate climate into passive-design priorities: orientation, form, glazing, shading, thermal mass, ventilation and landscape/water strategies.
- Define metrics and baselines before comparing options; state model/method and all major assumptions.
- Coordinate daylight, overheating, energy, operational carbon and embodied carbon tradeoffs rather than optimizing one metric blindly.
- Record strategies in drawings/specifications and identify where specialist simulation or certification evidence is required.
Deliverables
- Climate/passive-design strategy
- Option performance matrix
- Daylight/solar/energy/carbon study brief
- Sustainability action and evidence register
Verification
- Every metric states source, method, units and assumptions.
- Simulation outputs are not compared when models, weather files, geometry or boundary conditions differ materially.
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 claim LEED/BREEAM/Passivhaus/WELL or other certification without the responsible assessor/process.
- Do not present simplified calculations as code compliance or final energy modelling.
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.
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.

