civil-site-design
Skill39 starsChanged 24 days agoMITView on GitHub
Coordinate architectural projects with civil/site engineering: survey and terrain, grading, earthworks, access roads, parking, pedestrian routes, stormwater/drainage, utilities, retaining conditions and Civil 3D workflows. Use for site grading concepts, surface/corridor coordination, utility interfaces and civil-architectural handoff.
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
- 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 replace licensed civil, drainage, road or geotechnical design.
- Distinctive: line 41
Never move survey control or authoritative utility data without explicit verified instruction.
- 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
Civil / Site Design Coordination
Develop and review site/civil concepts while keeping hydrology, road, geotechnical and utility engineering with qualified civil specialists.
Preflight
- Topographic/cadastral survey, coordinate/datum system, existing/proposed surfaces, drainage catchments/outfalls, road/access requirements, utilities and geotechnical information.
- Civil 3D version/workflow when applicable: surfaces, feature lines, alignments, profiles, corridors, pipe/pressure networks and data shortcuts.
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
- Preserve survey control and build an existing-conditions/site-constraints model before proposed grading.
- Coordinate finished-floor levels, accessible entries, roads/parking, slopes, walls/steps and landscape interfaces against proposed surfaces.
- Map stormwater flow paths, utility corridors and service connections; expose conflicts with foundations, trees, public realm and structures.
- For Civil 3D work, inventory dynamic dependencies and data shortcuts before edits; validate surfaces, profiles, corridors and quantities after changes.
Deliverables
- Site/civil coordination plan
- Level/grading interface matrix
- Drainage/utility corridor diagram
- Civil 3D change/verification plan when relevant
Verification
- Coordinates, datum, units, surface versions and level references are explicit.
- Cut/fill, hydraulic capacity, pavement and retaining design are not treated as verified without engineering calculations.
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 replace licensed civil, drainage, road or geotechnical design.
- Never move survey control or authoritative utility data without explicit verified instruction.
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.
- B12: site and landscape
- B15: landscape junction review
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.