Claude Prompts for Architectural Practice
20 copy-paste Claude prompts for architects: design briefs, code research, schematic narratives, client communication, specifications, and the practice management work that eats studio hours.
In short: This page contains 16 copy-paste ready prompts, organized into 4 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.
Design + Briefs
4 promptsProgramming Brief from Client Conversation
1/16✨ What it does
Claude turns [Paste client meeting notes] into a programming brief with spaces and square footage, adjacencies, acoustic, thermal, and lighting criteria, aesthetic direction, budget, schedule, sustainability, and accessibility, and flags where the client contradicted themselves. Paste the notes, then settle every flagged contradiction before you draw.
[Paste client meeting notes]. Build programming brief: spaces required + sf, adjacency requirements, performance criteria (acoustic / thermal / lighting), aesthetic direction, budget alignment, schedule alignment, sustainability targets, accessibility requirements. Flag where client said opposing things — needs reconciliation.
Pro tip: Clients say contradictory things across meetings ("we want maximum natural light" + "no heat gain"). Surfacing contradictions early = shorter design phase. Hidden until DD = expensive rework.
Schematic Design Narrative
2/16✨ What it does
Claude writes a schematic design narrative for [project] covering design intent in plain language, site response, organization, materiality, sustainability, key moves, and program departures with rationale, for the client and for permit. Name the project, then read it once as if you were the client before you attach it.
Write SD narrative for [project]. Output: design intent (vision in plain language), site response, organizational concept, materiality direction, sustainability strategy, key design moves explained, departures from program (with rationale). Client-presentable + permit-suitable.
Pro tip: SD narrative does double duty: client comprehension + permitting basis. Plain-language client sections + technical permit sections = two-version doc serving both. Most narratives only serve one.
Design Critique + Pinup Prep
3/16✨ What it does
Claude runs a pre-pinup critique of [Paste design description or attach images] on intent versus execution, materials, organizational holes, program violations, code concerns, and what jurors will press hardest. Paste the description, then fix the weakest hole before you pin up.
[Paste design description or attach images]. Pre-pinup critique: design intent vs execution gaps, material/detail issues, organizational logic holes, programmatic violations, code concerns, what jurors will press hardest on. Honest critique = better presentation than peer compliments.
Pro tip: Studio peer critiques = polite. Honest critique catches what jurors will catch + 24 hours earlier. Time to fix before public exposure = saved face + better project.
Material Palette Justification
4/16✨ What it does
Claude justifies the material palette for [project] from materials [list], covering design intent, performance, durability, sustainability, cost, and alternatives you rejected, for a client or sustainability reviewer. List the materials, then keep only the ones you can defend on cost and maintenance.
Justify material palette for [project]. Materials: [list]. Per material: design intent it serves, performance basis, durability + maintenance, sustainability profile, cost positioning, alternatives considered + why rejected. Client + sustainability-minded reviewer expects justification.
Pro tip: Material decisions visible to clients ("why this stone?"). Justification beyond "it looks nice" = professionalism. Performance + sustainability + cost framing = credible.
XML tags are just the start. Learn the full Claude workflow.
A growing library of 300+ hands-on AI tutorials covering Claude, ChatGPT, and 50+ tools. New tutorials added every week.
Code + Compliance
4 promptsCode Research Summary
5/16✨ What it does
Claude researches applicable codes for [Project type, jurisdiction]: occupancy, fire and egress, accessibility, zoning, energy, structure, and MEP intersections, with key sections, design constraints, and where you might need a consultant. Fill type and jurisdiction, then verify every cited section against the current code book.
[Project type, jurisdiction]. Research applicable codes: IBC occupancy classification, fire/egress requirements, accessibility (ADA + state), zoning + use, energy codes, structural standards, mechanical/electrical code intersections. Output: applicable codes + sections, key constraints driving design, where I might conflict, expert review recommended.
Pro tip: Code research at programming = avoid expensive redesign at DD. Ignored at programming = "wait, can't have stair here" at DD. Front-load.
Egress Calculation Verification
6/16✨ What it does
Claude checks egress on [Paste plan + occupancy info] for occupant load, paths, travel distance, common path, dead ends, exit width, signs, and emergency lighting, flags violations, and suggests fixes as a brainstorm to verify. Paste your plan facts, then check each flagged item against the current code.
[Paste plan + occupancy info]. Verify egress: occupant load by room, egress paths, travel distance, common path of travel, dead ends, exit width, exit signs + emergency lighting. Flag code violations + suggest fixes. Always verify against current code; this is brainstorm-and-check.
Pro tip: Egress mistakes = re-permit. Catching at SD = simple. At permit submission = expensive redesign + delay. AI as second-eye is cheap insurance.
Sustainability Scorecard Prep
7/16✨ What it does
Claude builds a LEED, WELL, or Living Building scorecard for project [describe] with a realistic target, easy points, points that need design changes, effort and capital cost, and where stretching without budget usually gets abandoned. Describe the project, then pick a target you can fund, not the highest badge on the list.
Project: [describe]. Help build LEED/WELL/Living Building scorecard: applicable certification level, points easily achievable, points requiring design changes, point cost (design effort + capital), realistic certification target, where to push for higher level. Honest: stretching for cert without budget = abandoned mid-project.
Pro tip: Honest scorecard up front = realistic certification target. Aspirational scorecard without budget = abandoned at DD. Honesty preserves the goal.
Accessibility Audit
8/16✨ What it does
Claude audits [Paste design/plan] for ADA and state accessibility on door clearances, levers, mounting heights, slope, parking, and restrooms, with risk areas and fixes, and flags designer defaults that fail code. Paste the plan, then cross-check every flagged item against current ADAAG and your state amendments.
[Paste design/plan]. ADA + state accessibility audit: common-fail areas (door clearances, lever hardware, mounting heights, slope, parking, restrooms), risk areas, suggested fixes. Flag where designer-default isn't code-compliant. Always cross-check with current ADAAG + state amendments.
Pro tip: Accessibility violations costly + create risk. Catching at design = simple fix. Catching post-construction = retrofit + lawsuits. AI audit = cheap pre-permit pass.
Client + Project Communication
4 promptsClient Meeting Agenda
9/16✨ What it does
Claude builds a client meeting agenda for [phase] with pre-reads, decisions first then information then actions, decision rights, time boxes, expected outcomes, and follow-up commitments. Fill your phase, then send the agenda before the meeting so the room is not circular.
Client meeting agenda for [phase]. Output: pre-read materials, agenda items in order (decisions needed first, info-share later, action items last), decision rights per item, time allocation, expected outcomes, follow-up commitments. Meetings without agenda = circular conversation + no decisions.
Pro tip: Meeting where decisions deferred = lost cycle. Agenda forcing decisions = momentum. Hour-long agenda-less meeting = same outcome as 20-min agenda-driven meeting.
Decision Document for Client
10/16✨ What it does
Claude writes a decision document for [describe] with the decision, three options, pros and cons, a recommendation, a deadline, delay consequences, and a sign-off line so a verbal call does not get reopened. Describe the decision, then get the signed line before you proceed.
Decision document. Decision: [describe]. Output: decision being made, options considered (3 typical), pros/cons each, recommendation with rationale, deadline by which client must decide, consequences of delay. Sign-off line. Verbal decisions get re-litigated; written ones don't.
Pro tip: "I thought we decided X" = endless rework. Written decision documents signed = closure. Sounds bureaucratic; saves projects.
Bad News Communication
11/16✨ What it does
Claude drafts bad-news client copy for [describe] such as over budget, a schedule slip, or a code change that cut scope, leading with the news, why, three paths, your recommendation, and an ask for a response. Describe the news, then send it the same day; do not bury it in an update.
Need to deliver bad news to client: [describe — over budget, schedule slip, code constraint changed scope]. Help me draft message. Output: lead with the news (no burying), context for why, options going forward (3 with tradeoffs), my recommendation, ask for response. Honest + solutions-oriented.
Pro tip: Bad news buried in email = trust loss when found. Bad news led with + options framed = professional. Clients respect architects who handle hard news directly.
Site Visit Report
12/16✨ What it does
Claude turns [Paste site visit notes] into a formal report with date and attendees, observations by trade, drawing deviations and severity, clarifications, action items and owners, photo references, and the next visit, for permit and claims. Paste the notes, then assign an owner on every action item before you file it.
[Paste site visit notes]. Convert to formal site visit report. Output: date + attendees, observations by trade, deviations from drawings + severity, clarifications needed, action items + owners, photographs reference, next visit. Documents what + when + who said. Permit + claim trail.
Pro tip: Site visit reports = legal record. Inconsistent reports = exposed during dispute. Consistent format = defensible practice.
These prompts give you the what. Tutorials give you the why.
Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.
Practice Operations
4 promptsFee Proposal Letter
13/16✨ What it does
Claude writes a fee proposal for [project type, scope, schedule] with services per SD, DD, CD, and CA, fee per phase, additional-services rates, reimbursables, milestones, payment terms, and exclusions, precise enough for a contract and still readable. Fill type, scope, and schedule, then have counsel review the exclusions before you send it.
Fee proposal for [project type, scope, schedule]. Output: scope of services per phase (SD/DD/CD/CA), fee per phase, additional services framework (with rates), reimbursables, schedule milestones, payment terms, exclusions. Legal-precise + readable.
Pro tip: Vague fee proposals = scope creep without comp. Specific scope per phase + change-order framework = profitable + clear. Boring fee proposals serve you.
Specification Section Writing
14/16✨ What it does
Claude writes a CSI MasterFormat spec section for [system] with Part 1 general (scope, references, submittals), Part 2 products, and Part 3 execution, naming products where it helps, in an AIA-compatible form. Name the system, then check every named product against what you actually intend to specify.
Write CSI MasterFormat spec section for [system]. Output: Part 1 (general — scope, references, submittals), Part 2 (products — manufacturers, materials, performance), Part 3 (execution — installation, testing, cleanup). Specific products named where appropriate. AIA-compatible.
Pro tip: Specifications are legal docs. AI draft = first pass; expert review essential. CSI structure consistent = contractor pricing accurate; non-standard format = inflated bids from contractor uncertainty.
RFI Response Drafting
15/16✨ What it does
Claude drafts an RFI response to [paste] with clarified intent, a design decision if needed, drawing or spec references, who else to notify, schedule impact, and fee impact, and tells you to defer to the engineer if you are guessing. Paste the contractor question, then send only what you can stand behind.
RFI from contractor: [paste]. Help draft response. Output: clarification of intent, design decision if needed, drawing/spec reference, who else needs notification, schedule impact assessment, fee impact (if any). Architect liability concern: don't guess; if uncertain, defer to engineer.
Pro tip: Casual email response to RFI = liability. Formal RFI response = record. Always defer to engineer of record on structural/MEP; architect coordinates but doesn't guess on others' disciplines.
Project Post-Mortem
16/16✨ What it does
Claude runs a post-mortem on [completed project] covering budget versus actual, schedule, fee profitability, scope-creep cost, what went well, what failed, and lessons for the next job. Name your finished project, then put one lesson on the next kickoff agenda.
Post-mortem on [completed project]. Output: budget vs actual, schedule vs actual, fee profitability, scope creep cost, what went well, what failed, lessons applied to next project. Studios that don't post-mortem = repeat mistakes. Project as data.
Pro tip: Architecture firms famously bad at post-mortems (move to next project, don't analyze). Disciplined post-mortems = compounding learning + improving fees. Most lucrative habit firms ignore.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides