structural-coordination
Skill39 starsChanged 23 days agoMITView on GitHub
Coordinate architecture with structural systems at concept through technical design: grids, spans, columns/walls, cores, transfer conditions, openings, floor zones, movement joints, foundations, roof systems and structural interfaces. Use for structural strategy options and architect-engineer coordination, not final engineering design.
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
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are 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.
2
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.
- Very specific: line 34
All capacity/span/load statements are labelled conceptual unless engineer-verified.
- Distinctive: line 40
Do not size structural members for construction or claim adequacy.
- Distinctive: line 41
Do not provide signed/stamped engineering or substitute for structural analysis.
- 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
Structural Coordination
Support multidisciplinary coordination while keeping structural calculations and capacity decisions with qualified structural engineers.
Preflight
- Structural engineer inputs if available, building geometry/use, grids, floor-to-floor heights, major spans, cores, basements, material/system preferences and site/geotechnical constraints.
- Known transfer zones, cantilevers, large openings, facade/support conditions, plant loads and movement/seismic/wind considerations.
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
- Map architectural constraints to a plausible structural grid/system and identify where geometry creates transfers or discontinuities.
- Coordinate columns/walls/cores with rooms, facades, parking, circulation, risers and openings across levels.
- Reserve structural depths and movement/connection zones in sections; flag long spans, cantilevers, penetrations and load-sensitive uses.
- Prepare a decision/request matrix for the structural engineer and update architecture only from confirmed structural information.
Deliverables
- Grid/system option matrix
- Structural coordination overlays/sections
- Openings/transfer/interface register
- Engineer question/decision log
Verification
- Grids and vertical elements align across levels; major penetrations and floor/roof zones are coordinated.
- All capacity/span/load statements are labelled conceptual unless engineer-verified.
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 size structural members for construction or claim adequacy.
- Do not provide signed/stamped engineering or substitute for structural analysis.
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.