Design Directory - Maintenance Guide for Claude

Purpose

This directory contains all design specifications, technical planning, and product selection documentation for the garage construction project. Design files are organized into Exterior and Interior subdirectories.


Directory Structure

20-Design/
├── Design Notes.md          # Index of all design documents
├── Exterior/                # Exterior design specs
│   ├── Doors/              # Garage door specifications
│   ├── Exterior Lighting/  # Outdoor lighting plans
│   └── pictures/           # Exterior design reference photos
└── Interior/               # Interior design specs
    ├── Electrical Planning.md
    ├── HVAC Strategy.md
    ├── Insulation Strategy.md
    ├── Insulation Execution.md
    └── [other interior specs]

Critical Workflow: Document Design Decisions

IMPORTANT: When updating design documents with final decisions or specification changes, you must also update related documents:

  1. Design decision finalized → Update Decisions Log
  2. Product selected with cost → Update or create order file in Orders
  3. Specification affects timeline → Update Timeline
  4. Design affects other systems → Update related design docs and add cross-references

For every design document update:

  • Is this a decision? → Update Decisions Log
  • Does this have cost implications? → Update/create order file in Orders
  • Does this affect construction timeline? → Update Timeline
  • Does this impact other systems? → Update related design docs
  • Is this a major change? → Update Design Notes index

Design Document Structure

Frontmatter Format

---
title: [System/Area] Planning
type: design
tags: [garage, design, category, subcategory]
status: [planning|research|decided|in-progress|completed]
---

Status Values

  • planning - Early planning phase, multiple options being considered
  • research - Actively researching products, contractors, approaches
  • decided - Final decisions made, ready for procurement/execution
  • in-progress - Design being implemented during construction
  • completed - Design fully implemented and documented

Common Content Sections

Design documents typically include:

  1. Overview/Introduction - What system is being designed and why
  2. Requirements - Technical requirements, code compliance, performance goals
  3. Options Considered - Different approaches evaluated with pros/cons
  4. Recommended Approach - Final decision with justification
  5. Specifications - Detailed technical specs, product selections, capacities
  6. Installation Requirements - How it will be installed, who will do it, when
  7. Cost Estimates - Budget ranges, product costs, installation costs
  8. Checklists - Planning tasks, procurement tasks, installation tasks
  9. Related Documents - Links to orders, contractors, other design docs

Writing for a DIY Audience

IMPORTANT: The project owner installs most systems personally (electrical, insulation, HVAC, network, finish work). Design documents serve as both planning tools AND future installation/troubleshooting references. Write accordingly:

  • Installation sections should be step-by-step — Assume the reader is capable but learning. Include the “why” behind techniques, not just the steps.
  • Specify products with full detail — Model numbers, SKUs, links, specifications. The owner orders materials directly and needs exact product identification.
  • Show DIY vs. professional cost comparisons when both are viable options — Material-only cost for DIY, total cost for professional install. Let the owner make an informed choice.
  • Document for 20-year reference — Include wire routes, circuit numbers, product specs, and installation dates. This information helps diagnose problems decades later.
  • Note code requirements explicitly — The owner follows NEC and local code. Call out specific code sections when relevant so work passes inspection.
  • Include common mistakes and gotchas — Things like “neutral and ground must be separate in a subpanel” save the DIYer from costly errors.

Reference: See content/index.md (Project Philosophy callout) and root CLAUDE.md (Project Philosophy section) for full context.


Design Decision Workflow

Step 1: Document Options

When starting a design decision, document all options considered:

## Options Considered
 
### Option A: [Approach Name]
**Pros:**
- Advantage 1
- Advantage 2
 
**Cons:**
- Disadvantage 1
- Disadvantage 2
 
**Cost:** $X,XXX - $X,XXX
 
### Option B: [Approach Name]
**Pros:**
- Advantage 1
 
**Cons:**
- Disadvantage 1
 
**Cost:** $X,XXX - $X,XXX

Step 2: Make and Document Decision

When decision is finalized, clearly mark it:

## ✅ DECIDED: [Approach Name]
 
**Decision Date:** YYYY-MM-DD
**Rationale:** Why this option was chosen
**Trade-offs Accepted:** What we're giving up for this choice
**Next Steps:** What needs to happen to implement this

Step 3: Update Decisions Log

Add entry to [[10-Planning/Decisions Log]]:

## [System/Area] - [Decision Topic]
 
**Date:** YYYY-MM-DD
**Area:** Interior/Exterior
**Status:** ✅ Decided
 
**Options Considered:**
- Option A: Brief description
- Option B: Brief description
 
**Decision:** Selected Option A because [rationale]
 
**Implications:**
- Cost: $X,XXX
- Timeline: [when it will be implemented]
- Dependencies: [what needs to happen first]
 
**Related:** [[20-Design/Interior/System Planning]]

Step 4: Create/Update Order File

If decision involves purchasing materials:

  1. Create or update order file in [[30-Vendors & Contacts/Orders/]]
  2. Include estimated costs from design document
  3. Link design doc in order file’s related.design frontmatter
  4. Update Orders Index budget summary

Cross-Referencing Between Design Docs

When Designs Interact

Many garage systems interact with each other. When updating one design doc that affects another:

Example 1: Electrical affects HVAC

  • Updating Electrical Planning.md with 240V circuit for mini-split
  • Must also update HVAC Strategy.md to note electrical requirement
  • Add cross-reference links in both documents

Example 2: Insulation affects HVAC sizing

  • Changing insulation R-values in Insulation Strategy.md
  • Affects heat loss calculations in HVAC Strategy.md
  • Update HVAC sizing and add note about insulation dependency

Cross-Reference Format

Use wiki-links with context:

**Electrical Requirements:** This system requires a dedicated 240V 30A circuit. See [[20-Design/Interior/Electrical Planning#mini-split-circuit|Mini-Split Circuit]] for electrical specifications.
 
**Insulation Dependency:** HVAC sizing assumes R-49 ceiling and R-21 walls per [[20-Design/Interior/Insulation Strategy]]. If insulation values change, HVAC must be resized.

Cost Tracking in Design Docs

Cost Estimate Format

For products with defined costs:

**Estimated Cost:** $3,200-3,800 (materials only)
**Installation Cost:** $800-1,200 (professional install)
**Total Project Cost:** $4,000-5,000

For complex systems with options:

### Cost Summary
 
| Approach | Materials | Installation | Total | Notes |
|----------|-----------|--------------|-------|-------|
| DIY All | $1,919-2,933 | $0 | $1,919-2,933 | Requires 2 days labor |
| Hybrid | $525-714 | $1,440-1,920 | $1,965-2,634 | Pro blown, DIY batts |
| Pro All | $0 | $3,500-5,000 | $3,500-5,000 | Turnkey solution |
 
**RECOMMENDED:** DIY All approach for best value

Syncing Costs to Order Files

When design doc has detailed costs:

  1. Ensure matching order file exists in [[30-Vendors & Contacts/Orders/]]
  2. Costs in order file should match or reference design doc estimates
  3. Link design doc in order file: related: design: ["[[20-Design/Interior/System Planning]]"]
  4. Update Orders Index with estimated cost

Product Selection Documentation

When Documenting Product Selections

Include comprehensive details:

### Selected Product: [Product Name]
 
**Manufacturer:** Brand Name
**Model/SKU:** SKU-12345
**Specifications:**
- Spec 1: Value
- Spec 2: Value
- Spec 3: Value
 
**Pricing:**
- Unit Price: $XXX.XX
- Quantity Needed: X units
- Total Cost: $XXX.XX
 
**Vendor:**
- Primary: Home Depot ([link to product page])
- Alternative: Lowe's ([link to product page])
 
**Why This Product:**
- Reason 1
- Reason 2
- Meets [specific requirement]
 
**Installation Notes:**
- Special requirements
- Professional install needed? Yes/No
- Tools required
- Estimated time
 
**Related:**
- Order: [[30-Vendors & Contacts/Orders/Product Order]]
- Design: [[20-Design/Interior/Related Design]]

Checklist Integration

Task Metadata in Design Docs

Use consistent task metadata for integration with todo tracking:

## Checklist
 
### Planning Phase
- [ ] Research product options — stage:: 3
- [ ] Get contractor quotes — stage:: 3
- [ ] Finalize design — stage:: 3
 
### Ordering Phase
- [ ] Order materials — order:: [[30-Vendors & Contacts/Orders/Product Order]] — stage:: 5
- [ ] Schedule delivery — stage:: 5
 
### Installation Phase
- [ ] Install system — stage:: 6
- [ ] Test and verify — stage:: 6
- [ ] Final inspection — stage:: 6

Stage Numbers:

  • stage:: 1 - Foundation/Site Work
  • stage:: 2 - Slab/Radiant
  • stage:: 3 - Framing/Planning
  • stage:: 4 - Envelope (Roof, Siding, Windows)
  • stage:: 5 - Procurement/Ordering
  • stage:: 6 - Installation/Mechanical/Electrical
  • stage:: 7 - Finish/Cleanup

Design Document Patterns

Pattern 1: System Planning Document

Purpose: Plan entire system (HVAC, Electrical, Insulation, etc.)

Key Sections:

  • Overview and requirements
  • System sizing calculations
  • Multiple options with cost comparison
  • Recommended approach (clearly marked ✅)
  • Product specifications
  • Installation requirements
  • Cost summary
  • Checklist with stages

Examples:

  • Interior/Electrical Planning.md
  • Interior/HVAC Strategy.md
  • Interior/Insulation Strategy.md

Pattern 2: Execution/Installation Document

Purpose: Detailed step-by-step installation instructions

Key Sections:

  • Prerequisites
  • Materials list with SKUs and costs
  • Step-by-step installation procedure
  • Quality assurance checks
  • Common issues and solutions
  • Timeline for installation
  • Contractor coordination

Examples:

  • Interior/Insulation Execution.md

Pattern 3: Product Selection Document

Purpose: Document selection of specific products/brands

Key Sections:

  • Requirements driving selection
  • Products evaluated
  • Comparison matrix
  • Selected product with full specs
  • Where to buy and pricing
  • Installation notes

Examples:

  • Exterior/Garage Doors/Door Selection.md
  • Interior/Fire Extinguisher Plan.md

Design Notes Index Maintenance

The Design Notes.md file serves as an index of all design documents.

When to Update Design Notes

  1. Creating new design document → Add entry to appropriate section (Exterior/Interior)
  2. Major status change → Update status indicator
  3. Decision finalized → Mark as decided/completed
  4. Cost estimates added → Add cost range to index

Index Entry Format

### [System/Area Name]
 
**Status:** [Planning|Decided|In Progress|Complete]
**Document:** [[20-Design/Interior/System Planning]]
**Est. Cost:** $X,XXX - $X,XXX
**Summary:** One-sentence description of what this design covers

Common Design Document Updates

Adding Weather Context

When design decisions are influenced by climate/weather:

**Climate Considerations:**
- Michigan winters: -10°F to 30°F typical
- Heating days: October - April (7 months)
- HVAC sizing must account for extreme cold
- Insulation critical for winter comfort and cost control
 
**Weather Impact on Installation:**
- Insulation installation possible in winter with heat
- HVAC outdoor unit must be Hyper-Heat rated for cold climate

Documenting Code Requirements

When design must meet code:

**Code Requirements:**
 
**Michigan Residential Code (IRC) 2015:**
- Ceiling Insulation: Minimum R-49 (Climate Zone 6A)
- Wall Insulation: Minimum R-21 (2×6 construction)
- Air Sealing: Required for all penetrations
 
**Fire Code:**
- Type X fire-rated drywall required for garage ceiling (separating garage from living space above)
- 5/8" thickness minimum
- Proper fire stopping at penetrations
 
**Reference:** See [specific code section] for detailed requirements

Quick Checklist for Design Updates

When creating or updating a design document:

  • Frontmatter includes: title, type: design, tags, status
  • Options considered are documented with pros/cons/costs
  • Final decision is clearly marked with ✅ DECIDED
  • Cost estimates are detailed and current
  • Product selections include: brand, model, SKU, pricing, vendor links
  • Installation requirements and complexity noted
  • Cross-references to related design docs added
  • If decision made: Decisions Log updated
  • If costs estimated: Order file created/updated in Orders
  • If timeline affected: Timeline updated
  • If new document: Design Notes index updated
  • Checklists include stage metadata for task tracking

  • Decisions Log - Track all major design decisions (UPDATE THIS!)
  • Orders Index - Budget tracking for design selections
  • Timeline - Construction schedule
  • Design Notes - Index of all design documents (UPDATE THIS!)
  • Templates/Design Note.md - Design document template (if available)

This file is automatically ignored in Quartz builds but tracked in git for AI assistant reference.