agentleFS
Sign inStart free
adeerkhanadeerkhan/vitruvius/skills/civil/SKILL.md

civil

Skill10 starsChanged 5 days agoMITView on GitHub

Civil and structural engineering research. Use when the user invokes /civil or asks about civil/structural engineering topics — buildings and bridges, steel/concrete/timber/masonry structures, foundations and geotech, seismic and wind design, transportation, water resources — or asks to verify a structural claim. Dispatches to the shared engineering-research method with the civil evidence landscape.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Code provisions: verify the standard exists, read the actual provision, and cite section + edition.

    line 39
  2. Distinctive:

    Loads: every load must state its basis and combination with the governing standard and section — ASCE 7 for buildings, AASHTO LRFD for …

    line 42
  3. Distinctive:

    Follow the method's artifact contract.

    line 59
  4. Very specific:

    If research hits an evidence dead-end — no code provision, paper, or dataset addresses the question after exhausting the discovery layers — …

    line 71
  5. Distinctive:

    Do not invoke gap-analysis automatically.

    line 74

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- VITRUVIUS-COMPILED-SKILL:BEGIN v1 sha256=c782646707e95f4fcf53d068fef47b5b263ffd9f08bd973b58a59e6a2e095732 -->

Civil / Structural Engineering Research

Activate the /skill:engineering-research method and run it with this domain payload. Do not restate the research loop here.

Evidence landscape

  • Codes/standards: AISC 360 (steel), ACI 318 (concrete), NDS (timber), TMS 402 (masonry), ASCE 7 (loads), AASHTO (bridges), IBC, and the governing jurisdiction's adopted code. When a code governs, cite the exact section — and check which edition the question's jurisdiction has adopted.
  • Primary sources: code commentary, official design guides from the issuing body, geotech reports, manufacturer/connector ICC-ES reports, peer-reviewed structural literature.
  • Prior art / practice: documented failures and forensic studies, post- earthquake/storm reconnaissance reports, trade association guidance.

Verification criteria

  • Code provisions: verify the standard exists, read the actual provision, and cite section + edition. Do not summarize a provision from memory or a title.
  • Loads: every load must state its basis and combination with the governing standard and section — ASCE 7 for buildings, AASHTO LRFD for bridges (wind: Art. 3.8). Do not assume ASCE 7 governs a bridge; units and direction must be explicit.
  • Sign conventions: compression vs tension, moment direction, global vs local axes.
  • Material properties: trace to a named grade + governing spec (e.g. Gr. 50 per ASTM A992, f'c per ACI 318).
  • Design values: factors (phi, omega, LRFD/SFD) must be stated and traced to code, not assumed.
  • Geotech: any soil parameter must be marked verified (from a real report/standard) or inferred (assumed) — never laundered into fact.
  • Calculations: show formula, inputs, and units so the check can be re-run.

Deliverable shape

Follow the method's artifact contract. In the final artifact, end with a Sources section citing code + section + edition for every governing provision, and mark loads, factors, and material properties verified, inferred, or blocked.

Invocation Flags

Accept --deep and --quick flags and pass them through to the engineering-research method. See that skill for flag semantics.

Gap Detection

If research hits an evidence dead-end — no code provision, paper, or dataset addresses the question after exhausting the discovery layers — suggest running /gap-analysis civil <sub-topic> to formally validate and document the gap. Do not invoke gap-analysis automatically; offer it as a next step and wait for the user to confirm.

Scope and Boundaries

  • This skill produces research — it does NOT produce final designs or construction documents.
  • Research-only, not for final engineering sign-off. Licensed engineers must review and approve any design based on this research.

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.

Check your setup, free