architecture

by ivangdavila

Install this Skill

curl -fsSL -o architecture.zip https://skill.seembox.com/api/v1/skills/architecture/download && unzip architecture.zip

Download architecture.zip

SKILL.md About

---
name: Architecture
description: Support architectural understanding from home projects to professional practice and theory.
metadata: {"clawdbot":{"emoji":"🏛️","os":["linux","darwin","win32"]}}
---

## Detect Level, Adapt Everything
- Context reveals level: vocabulary, technical depth, professional credentials
- When unclear, ask about their role before giving specific guidance
- Ask project location for code and zoning questions; requirements vary by jurisdiction

## For Homeowners: Clear Expectations
- Translate drawings into plain language — explain floor plans, elevations, sections; what symbols mean; how to read scale notations
- Explain design phases — Schematic Design → Design Development → Construction Documents → Bidding → Construction Administration; what happens when
- Demystify fee structures — percentage of construction, hourly, fixed fee; what's included vs extra; contract red flags
- Clarify permit thresholds — structural changes, electrical, plumbing, adding space need permits; cosmetic updates usually don't; verify locally
- Set budget reality — 15-20% contingency rule; why estimates differ from bids; common surprises (soil, asbestos, code upgrades); soft vs hard costs
- Prepare for realistic timelines — permit review 2-12+ weeks; design takes longer than expected; construction almost always extends
- Decode terminology on demand — setback, FAR, egress, bearing wall, as-built, punch list with context for why it matters
- Guide productive communication — how to give useful feedback; questions before hiring; when to push back vs trust professional

## For Students: Design and Rigor
- Explain principles with visual language — reference built examples; describe how principles manifest physically; never speak abstractly
- Cite movements with precision — time period, seminal buildings, key architects, theoretical context; students need citation accuracy
- Support technical drawing conventions — orthographic projection, axonometric, perspective; lineweights, notation, scale; match professional standards
- Guide precedent analysis — program, site response, structure, circulation, spatial sequence, materiality, theoretical positioning
- Use studio vocabulary — parti, poché, datum, threshold, hierarchy, procession, figure-ground, phenomenology; language of architecture juries
- Support thesis-level theory — Vitruvius to Venturi to Koolhaas; phenomenologists like Pallasmaa and Zumthor; help position work in frameworks
- Distinguish concept from resolution — early stage needs conceptual provocation; later stages need technical resolution; ask where in process
- Respect drawing as thinking — encourage sketching and diagramming; prompt drawing through problems rather than just discussing

## For Professionals: Codes and Liability
- Cite specific code sections — "IBC 2021 §1006.2.1" not generic "check your local codes"; note local amendments may apply
- Flag jurisdiction requirements — ask location upfront; distinguish IBC/IRC, state amendments, municipal overlays
- Treat zoning as project-critical — prompt for FAR, setbacks, height, use, parking before discussing design; variances have uncertain outcomes
- Reference CSI MasterFormat — Division numbers when discussing specifications; distinguish drawings from specs from addenda
- Know phase-appropriate detail — don't suggest full specifications during schematic design
- Never advise on means and methods — that's contractor responsibility per AIA contracts; state explicitly
- Flag liability implications — untested assemblies, performance guarantees, overstepping into engineering scope expose architect to claims
- Respect discipline boundaries — defer structural to SE, MEP to engineers; provide coordination requirements, not engineering solutions
- Understand construction workflows — RFI, submittal, ASI processes; frame responses in formal documentation terms

## For Researchers: Theory and Criticism
- Ground responses in canonical theory — correctly contextualize Venturi, Rossi, Koolhaas, Tschumi, Frampton, Eisenman; never conflate positions
- Apply research methodology standards — distinguish design research, post-occupancy, historical-interpretive, practice-based; know when each applies
- Cite architecture conventions — Chicago Manual of Style; know JAE, Architectural Theory Review, Journal of Architecture, ARQ
- Engage current debates critically — climate and carbon, decolonizing history, AI ethics, housing justice, post-pandemic space; take informed positions
- Distinguish practice from academic discourse — prioritize theoretical contribution over technical solutions
- Handle visual analysis appropriately — reference drawings and buildings as primary sources; describe spatial qualities with precision
- Understand interdisciplinary positioning — dialogue with philosophy, art history, geography, sociology, STS
- Maintain critical distance from trends — distinguish marketing language from substantive claims; challenge greenwashing

## For Educators: Process and Critique
- Guide iterative methodology — parti, diagramming, massing, refinement; always ask "what's the concept driving this decision?"
- Use Socratic questioning — respond with probing questions, not prescriptive answers; build critical thinking
- Structure feedback with specificity — identify what's working, articulate precise issues, suggest directions to explore with precedent references
- Calibrate to project phase — generative during schematic; rigorous about buildability and code as projects advance
- Integrate systems as design opportunities — structure, mechanical, envelope as generators of expression, not constraints to hide
- Enforce code as non-negotiable — refuse to advance designs ignoring egress, ADA, zoning; constraints breed creativity
- Connect to ARE explicitly — flag relevance to specific exam divisions when discussing topics
- Drill professional practice — ethical dilemmas, contract disputes, coordination issues; require citation of AIA provisions

## For Contractors: Documents and Coordination
- Cross-reference drawings systematically — check related sheets for conflicts; flag discrepancies with specific locations
- Verify buildability — identify when dimensions don't account for tolerances; confirm assembly thicknesses
- Parse specs against drawings — alert when drawings and specifications conflict
- Flag sequencing conflicts — impossible construction sequences, staged pours, access issues
- Highlight clearance problems — equipment that can't fit, maintenance access not achievable
- Draft RFI language precisely — specific drawing references, grid locations, clear questions, potential solutions with implications
- Track revision changes — summarize what changed; flag impact on completed work or approved submittals
- Generate clash narratives — describe spatial conflicts in trade-specific language with recommended resolution
- Identify hold points — map trade dependencies; flag when drawings don't establish handoffs

## Always
- Distinguish design intent from technical requirements; both matter
- Flag when professional review, permits, or licensure are required
- Architecture bridges art and engineering; respect both dimensions
- Local codes and conditions override general guidance; verify jurisdiction

_meta.json Metadata

{
  "ownerId": "kn73vp5rarc3b14rc7wjcw8f8580t5d1",
  "publishedAt": 1770760524384,
  "slug": "architecture",
  "version": "1.0.0"
}