agentleFS
aianime0012-coderaianime0012-coder/vitruvius-skills/skills/mep-coordination/SKILL.md

mep-coordination

Skill0 starsChanged 3 months agoMITView on GitHub

Coordinates mechanical, electrical, and plumbing systems with architectural and structural design — riser locations, penetrations, clearance, routing, and clash prevention. Use when integrating MEP into a design, reviewing coordination drawings, resolving conflicts, or planning service spaces and shaft locations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. MakeItEzzz555/Gridline★ 39same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

Files
SKILL.md

MEP Coordination

Plan and review the integration of Mechanical (HVAC), Electrical, and Plumbing systems with architecture and structure. The goal: feasible routing, no clashes, correct clearances, and maintainable service spaces.

When to use

  • Early design: allocating shafts, risers, and plant rooms
  • Design development: reviewing MEP routing against structure and ceilings
  • Checking coordination drawings / 3D federated model
  • Resolving a specific conflict (duct vs beam, pipe vs. wall)

Workflow

  1. Get the program of spaces and the service loads per space (HVAC tonnage/CFM, electrical panel loads, plumbing fixtures). Without loads, coordination checks are guesswork — request the MEP design basis.
  2. Locate the services:
    • Riser shafts: stack plumbing, duct, and electrical vertically; avoid placing a shaft over an interior structural column or a stair well.
    • Plant rooms (mechanical rooms, electrical rooms, data rooms): size, door swing, service access, and code separation.
    • Ceiling zones: depth available vs. duct depth + lighting + sprinklers + structure.
  3. Routing discipline (typical priority): gravity drain (plumb) → duct → pipe → conduit → cable tray → sprinkler. The lower-priority systems route around higher-priority ones; conflicts get resolved by the hierarchy.
  4. Check clearances & access:
    • Duct-to-beam clearance, pipe-to-wall, panel front working space (NEC: 30" x 36" x depth for panels)
    • Equipment access & maintenance space (AHU filters, valve access, condensate drains)
    • Ceiling access panels for valves/dampers/lighting drivers
  5. Cross-discipline checks:
    • Penetrations through rated assemblies need firestopping (coordinate with IBC Ch. 7)
    • Shafts need fire rating; duct penetrations need fire dampers
    • Structural: avoid notching beams/columns; check slab openings vs. rebar
    • Exterior: roof drains, gutter locations, equipment screens, PMT clearance
  6. Output: conflict log + coordination notes, ranked by severity, each with a recommended resolution.

Output format

Coordination Log — L2, corridor ceiling zone (12" cavity)
ID   Type   Location                Conflict                              Resolution
C-1  High   Corridor, Grid B/2      ǫ24" duct vs ǫ24" beam @ 8'-6"        Route duct below beam, drop 12"
C-2  Med    Mech room, grid A/1     Panel board blocked by AHU piping     Relocate panel 3' east
C-3  Low    Restroom R-102          Sanitary vent crosses light fixture   Drop vent 6" at fixture

Edge cases & cautions

  • Use actual sizes, not code minimums — a 24" duct and 12" duct have different impacts; always ask for (or estimate with stated assumption) real sizes.
  • Slope matters — sanitary and storm drains need slope (1/8"–1/4" per foot typical); 100 ft of run costs 12–25" of vertical. In shallow plenums this decides the routing.
  • "Clash-free" is not "coordinated" — code clearance, access, and firestopping requirements are separate from geometric clash.
  • Don't move structural elements without the structural engineer: state "verify with structural" for any beam/column/opening modification.
  • Ceiling-height claims — check actual finished ceiling height vs. the sum of structure + services + lighting; report the available plenum depth honestly.
  • Maintenance access — flag any component that would require demolition for service access.

Files

  • references/mep-cheatsheet.md — typical duct/pipe sizes, clearance requirements, and shaft/plant-room planning rules.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.