agentleFS
Sign inStart free
timjrobinsontimjrobinson/Claude-Code-Construction-Manager/CLAUDE.md

Claude-Code-Construction-Manager

CLAUDE.md4 starsChanged 8 months agoMITView on GitHub

Construction project delivery managed through 40+ coordinated Claude Code subagents. Each agent owns a specific discipline, enforcing separation of concerns and quality. @.claude/docs/directory-structure.md @.claude/docs/technical-preferences.md @.claude/docs/coordination-rules.md User-driven collaboration, not autonomous execution. Every task follows: Question -> Options -> Decision -> Draft -> Approval First project? If no project type is configured and no site exists, run /start to begin the guided onboarding flow. All design and engineering documents use Markdown. Each document must include these 8 required sections: @.claude/docs/context-management.md

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every task follows: Question -> Options -> Decision -> Draft -> Approval

    line 28
  2. Distinctive:

    No commits without user instruction

    line 32
  3. Distinctive:

    All design and engineering documents use Markdown.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

Claude Code Construction Team -- Construction Project Agent Architecture

Construction project delivery managed through 40+ coordinated Claude Code subagents. Each agent owns a specific discipline, enforcing separation of concerns and quality.

Project Type

  • Type: [CHOOSE: Shopping Mall / Apartment Block / Mixed-Use / Commercial / Healthcare / Industrial]
  • Scale: [SPECIFY: gross floor area, stories, units]
  • Version Control: Git with trunk-based development
  • BIM Platform: [CHOOSE: Revit / ArchiCAD / Tekla / OpenBIM (IFC)]

Project Structure

@.claude/docs/directory-structure.md

Technical Preferences

@.claude/docs/technical-preferences.md

Coordination Rules

@.claude/docs/coordination-rules.md

Collaboration Protocol

User-driven collaboration, not autonomous execution. Every task follows: Question -> Options -> Decision -> Draft -> Approval

  • Agents may write files directly without asking permission first
  • Multi-file changes should be summarized after completion
  • No commits without user instruction

First project? If no project type is configured and no site exists, run /start to begin the guided onboarding flow.

Project Stages

  1. Feasibility -- site analysis, zoning review, budget viability
  2. Schematic Design -- massing, spatial relationships, concept drawings
  3. Design Development -- detailed design, material selection, systems layout
  4. Construction Documents -- permit-ready drawings and specifications
  5. Bidding/Negotiation -- contractor selection, value engineering
  6. Construction -- site work, inspections, RFIs, change orders
  7. Commissioning/Handover -- systems testing, punch lists, owner training

Design Theory Frameworks

  • Integrated Design Process (IDP) -- all disciplines collaborate from day one
  • Building Information Modeling (BIM) -- single source of truth, clash detection, 4D/5D
  • Lean Construction -- eliminate waste, pull planning, last planner system
  • Value Engineering -- maximize function per cost without sacrificing quality

Document Standards

All design and engineering documents use Markdown. Each document must include these 8 required sections:

  1. Overview -- project scope and objectives
  2. Design Intent -- functional and aesthetic goals
  3. Technical Requirements -- specifications and applicable standards
  4. Calculations -- all engineering math with variables defined
  5. Code Compliance -- applicable building codes (IBC, NEC, NFPA, ADA, local)
  6. Coordination Notes -- interfaces with other disciplines
  7. Material Specifications -- specified materials with approved alternatives
  8. Acceptance Criteria -- testable conditions for completion

Context Management

@.claude/docs/context-management.md

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