Prompt library for architects

From the space program below, produce: 1) a table of required adjacencies -
space pair, strength (must touch / near / no relation / keep apart), and the
reason from the program text; 2) spaces whose placement the program leaves
undecided, as questions for the client; 3) conflicts where the program's
stated adjacencies cannot all hold on one floor, if any, quoting the
conflicting lines. Use only the program text. Program: [paste]

Draft a one-page design narrative for a landscape project from the site
inventory facts I paste: existing conditions, constraints, program, and the
design moves we chose. Write in plain professional language for a client
audience - no marketing adjectives, no claims beyond the facts I give you.
Where a fact is missing for a claim the narrative needs, insert
[VERIFY: what's missing] instead of inventing it. Inventory and program:
[paste]

I am an architect starting [project type] for [client type]. Below are my raw
notes and excerpts from client emails, separated by ---. Build a structured
pre-design brief under these headings: Project goals / Spaces and requirements /
Budget and schedule signals / Site facts stated / Constraints stated /
Contradictions between sources, quoting both lines / Decisions the client
assumes are made but never confirmed / Open questions, ranked by rework risk.
Use only what appears in my material; where something is implied but not
stated, put it under Open questions. Write [NEEDS INPUT] where a heading has
nothing. Material: ---[paste]---

Below is a standard section from our past proposals and the priorities of a
new client. Rewrite the section so it speaks to this client's priorities:
reorder points so their top concern comes first, replace generic examples
with the relevant ones from the list I give you, and cut anything that does
not serve this client. Keep every factual claim exactly as written - do not
add projects, numbers, or capabilities. Keep it under [N] words.

Our standard section: [paste]
This client's priorities: [2-4 bullets from the RFP or your calls]
Relevant examples to use: [projects from your portfolio, one line each]

Draft the "Project Understanding and Approach" section of an architecture
proposal, 350-450 words. Use ONLY the facts below - if something important is
missing, insert [GAP: what is missing] instead of inventing it. Mirror the
client's own vocabulary from the RFP excerpt. Structure: what the client is
trying to achieve, the two or three hardest problems in this project, and how
our process addresses each in sequence. Plain professional language, no
superlatives, no "world-class", no "state-of-the-art".

Client and project facts: [paste RFP excerpt or summary]
Our relevant experience: [2-4 comparable projects, one line each]
Our process: [your stage structure, one line per stage]

Write a change narrative for my client from the facts below: what changed,
why, cost and schedule effect as I state them, and what happens next. Open
with the change and its effect in two sentences, then the background.
Neutral tone - no blame, no apology spiral, no minimizing words like "just"
or "small". Keep every figure exactly as I give it. Maximum [250] words.
Facts: [paste]

Prepare a kickoff questionnaire for a [project type] client who is [client
profile]. 20 questions maximum, grouped: how they will use the spaces /
budget and its flexibility / schedule drivers / decision-making and approvals
/ taste and references / fears. Phrase every question for someone with no
construction vocabulary, one line each. End with the three questions I should
ask in person rather than in writing, with one line on why.

I paste open-ended comments from a community engagement session for a
public landscape project. Group them into themes. For each theme: a name,
how many comments fall into it, two verbatim example comments, and any
direct conflicts between themes. Then list every comment that fits no
theme - do not force them. Keep the count honest: the theme counts must sum
to the comments I pasted minus the unthemed ones. Comments: [paste]

Turn my raw site-meeting notes below into: 1) formal meeting minutes
(project, date, attendees, items discussed); 2) a decisions list; 3) an
action items table with owner and due date. Use only what is in the notes;
where an owner or date is missing, write TBC rather than inventing one.

Write 150 words maximum that I can send to my client, who has no construction background, explaining this change: [describe the change]. Cover: roughly why it costs less (or more), what changes visually, and what does not change. No technical jargon without a plain-language gloss, no hype, and end with the one decision I need from them.

Rewrite my technical scheme description for the client, who has no
construction background. Keep every number and dimension unchanged. Replace
jargon with plain equivalents, keeping the technical term in parentheses at
first use. Order: what they will see arriving, how the main spaces work day
to day, what is decided, what is still open and when each open item gets
decided. Maximum [300] words. Description: [paste]

Write an email to my client about a schedule slip. Facts: [what slipped, how
long, why, what continues in parallel, new date]. Open with the revised plan
and new date - not with the problem. Explain the cause in two plain
sentences without blaming anyone. Close with the next concrete step and its
date. Professional, warm, no filler apologies, maximum [180] words. I will
personalize before sending.

I paste sections of the accessibility standard adopted in my jurisdiction,
then describe my design. Produce a screening list: requirement with its
section number quoted, what my description says, and "appears to meet",
"appears short", or "not covered by the pasted text". Use only the pasted
sections - no requirements from memory. This prepares my own verification;
the governing check happens on the adopted edition with my code consultant.
Standard: [paste] Design: [paste]

I am an architect checking egress basics for a [building type] in a jurisdiction that has adopted the [code edition] without amendments (I will verify local amendments separately). Answer these, citing the exact section or table number for each: [your questions]. State the code edition you are citing, and list what I must verify in the adopted local code before relying on any of this.

I paste sections of a design standard or municipal code below. Answer my
question using only the pasted text: quote the governing passage with its
section number, state the answer, and say plainly if the pasted text does
not cover my question. Do not fill gaps from memory - if you are using
anything beyond the pasted text, say so explicitly. Standard text: [paste]
Question: [paste]

Here is the zoning text that applies to my site, and my lot dimensions. Using
ONLY the text I paste, build a buildable envelope worksheet:

- One row per parameter (setbacks by edge, maximum height, FAR, lot coverage,
  parking minimum, any other limit in the text), with the clause number and a
  verbatim quote of the controlling sentence.
- A derived-envelope section: from those parameters and my lot dimensions,
  calculate the maximum footprint and buildable volume, showing the arithmetic.
- An "unclear from provided text" list for anything the text references but
  does not define (overlays, variances, definitions in other sections).

Do not fill gaps from general knowledge of zoning codes. This is a first-pass
worksheet; a licensed professional verifies it against the current local code.

Zoning text: [paste]
Lot dimensions: [paste]

Below I paste sections of the zoning ordinance for my site, copied from the
adopted text, then my proposal's parameters. Build a table: requirement, the
ordinance line quoted verbatim with its section number, required value,
proposed value, and one of "appears to comply", "appears not to comply",
"cannot tell from the pasted text". Use only the pasted text - do not add
requirements from memory. This organizes my own review; it is not a code
check. Ordinance: [paste] Proposal: [paste]

Here is the text of a zoning ordinance section for my site, and my proposed building parameters. Using ONLY the ordinance text I provide, build a table: each requirement with its clause number, my proposed value, and a flag "appears to meet", "appears short" or "unclear from provided text". Do not state that anything complies; this is a first-pass screen. If a requirement cannot be evaluated from the data given, say so.

Turn my dictated notes from today's site visit into a field report: project,
date, weather, work observed by trade, deficiencies observed, directives
given (imperative sentences a contractor can act on), information requested,
next visit. Keep my wording for deficiencies, cleaned only for clarity. Mark
gaps [NEEDS INPUT] instead of inventing. Flag any internal inconsistency in
my notes - dates, counts, names - rather than resolving it silently. Notes:
[paste]

Organize my walkthrough notes into a punch list: items grouped by room, then
by trade within each room; each item gets a number, location, deficiency in
one line, and a reference to spec section or drawing if my notes include
one. Keep my deficiency wording. Mark entries too vague to assign [CLARIFY]
- I will re-walk those. End with a count by trade. Notes: [paste]

Draft a response to the RFI below using only the project documents I paste
with it. Structure: restate the question in one line; answer it citing each
document by name, sheet or section for every statement; if the pasted
documents do not fully answer it, say exactly what is missing instead of
filling the gap. Neutral wording, no fault assignment. I will review and
sign - note at the end what I must verify before issuing. RFI: [paste]
Documents: [paste]

Turn my raw site-meeting notes below into: 1) formal meeting minutes (project, date, attendees, items discussed); 2) a decisions list; 3) an action items table with owner and due date. Use only what is in the notes; where an owner or date is missing, write TBC rather than inventing one.

Compare the submittal below against the specification section I paste.
Return: items that match the spec (reference both), deviations (quote both
sides, classify: substitution request / error / clarification needed), and
items the submittal omits that the spec requires. Phrase every deviation as
a question for my review action - the review stamp decision is mine.
Submittal: [paste] Spec section: [paste]

Below are my architectural notes and the structural engineer's report for
the same project, separated by ===. List only the contradictions between
them: element, what my notes say, what the report says, and severity (stops
coordination / needs a call / minor). Quote both sides verbatim. Do not
propose engineering solutions, and do not flag items that merely appear in
one document and not the other unless they conflict. My notes: [paste] ===
Report: [paste]

I am assembling the consultant team for [project type, size]. For each
discipline I list below, produce the questions their fee proposal must
answer: scope boundaries, deliverables by phase, meetings and site visits
included, exclusions that usually hurt later, and information they will need
from me by [phase]. Format: one table per discipline, question / why it
matters. Do not estimate fees. Disciplines: [list]

Turn my design moves into a concept narrative of about [350] words for
[audience]. I list each move with its reason. Keep my reasoning exactly - do
not add sustainability, wellbeing or community claims I did not make, and do
not reorder cause and effect. Plain professional prose, no marketing
adjectives. Moves: 1. [move] because [reason] 2. ...

You are the client's evaluation committee. Below are the scoring criteria
from the RFP and our draft response section. Score our draft against each
criterion as the committee would: where does it answer the criterion
directly, where is it generic, and where does it claim something without
evidence? Quote the weakest sentences. Then list the three changes that
would most improve the score. Do not rewrite the section - critique it.

Scoring criteria: [paste from the RFP]
Our draft: [paste the section]

I will present [N] design options for the same program. From my descriptions
below, build a comparison table: how each option answers the program, site
response, structural implications I stated, relative cost drivers I stated,
and risks or unknowns. Use only what I wrote - no invented advantages. After
the table, list the decisions the client must make to choose, as numbered
questions. Options: [paste]

Act as a skeptical design jury reviewing my scheme the day before the real
review. From my summary below, write the eight hardest questions I will
face, ordered from most to least damaging, each with one line naming the
weakness behind it. Then pick the two questions I currently cannot answer
from my own summary and say what material would close each. Do not soften
the questions. Scheme: [paste]

The contractor proposed the value-engineering items below. For each, list
what it would change beyond cost: performance, durability, appearance,
code-sensitive aspects to re-verify, and knock-on effects on other trades -
each phrased as a question for my review, not a verdict. Do not accept or
reject any item and do not invent savings figures. Items: [paste]

Here is the sheet list of my design development issue for a [project type].
Against the deliverables an architect would normally include at DD for this
building type, list: sheets or content that seem missing, sheets that look
like construction-document scope arriving too early, and the consultant
drawings I should confirm are coming. Format as three lists, one line each
with the reason. My office standard and the contract govern - mark every
item "confirm against contract". Sheet list: [paste]

Here are the general notes collected from my drawing set. Find: duplicate
notes saying the same thing in different words (quote both), notes that
contradict each other (quote both), and notes that belong in the
specification rather than on drawings. Suggest a merged wording only for
exact duplicates; leave contradictions for my decision. Number every
finding. Notes: [paste]

Build a door and window schedule skeleton from my markup notes below.
Columns: mark, location, nominal size, type, material, fire or acoustic
rating, hardware group, remarks. Fill only cells my notes support; write
[NEEDS INPUT] in every other cell rather than assuming. After the table,
list openings my notes imply but never describe (a room with no door listed,
a habitable room with no window). Notes: [paste]

Draft a permit submission cover letter and document transmittal from the
facts below: project, address, scope summary, the authority's checklist
items I paste, and which documents I am including. The letter is factual and
brief - no persuasion, no compliance claims beyond "submitted for review".
The transmittal lists each document with title, date and sheet count, and
flags checklist items I have not included as "to follow". Facts: [paste]
Authority checklist: [paste] My documents: [paste]

Below are excerpts from my specification section and the notes on my
drawings for the same scope, separated by ===. Find only direct
contradictions: element, what the spec says, what the drawing note says,
quoted verbatim. Classify each: blocks pricing / causes an RFI / cosmetic.
Ignore wording differences that do not change the requirement. Do not
propose which side is right. Spec: [paste] === Drawing notes: [paste]

Draft a letter to my client about additional services. I paste: the original
scope summary, the change requests to date with dates, and the agreement
clause on additional services, quoted verbatim. Structure: what the
agreement covers, what has changed, why the new work falls outside, and the
proposed path - written authorization before work proceeds. Collaborative
but firm; cite the clause exactly once. Maximum [350] words. Facts: [paste]

Act as a skeptical practice principal. Below are an RFP summary and our firm
profile. Score this opportunity 1-5 on each: fit with our built experience,
realistic budget signal, relationship with the client (none / warm / existing),
submission effort for the stated deadline, and probability a local or
incumbent firm is favored. Justify each score in one sentence using only the
facts given. Do not invent facts about our firm or the client. End with a
one-line recommendation: pursue, pursue with conditions, or decline - and the
single strongest reason.

Firm profile: [3-5 lines: size, sectors, comparable projects, location]
RFP summary: [paste or summarize the RFP]

Read the RFP below. Build a compliance matrix as a numbered table with these
columns: requirement (quote the RFP's exact wording), section of our response
that must answer it, mandatory or scored, and what evidence we need to attach.
Include every submission formality: deadline, delivery method, page limits,
required forms, insurance certificates, license numbers. Do not paraphrase
requirements - quote them. If anything is ambiguous or missing from the RFP,
list it under "Questions for the client" instead of guessing.

[paste the full RFP text]

I'm a landscape architect responding to an RFP. Below I paste the RFP text
and bullet-point facts about my firm (size, relevant projects,
certifications, team). Build: (1) a compliance matrix - every stated
requirement, submission item and deadline from the RFP, each with the exact
RFP wording quoted and where my firm facts answer it or a gap flag; (2) a
response outline matching the RFP's required structure, with my facts
slotted in; (3) a list of questions worth sending to the issuing agency
before the deadline. Use only the RFP text and my facts - do not invent
projects, staff or certifications. RFP: [paste] Firm facts: [paste]

Our architecture office ([number] people) is adopting a written AI policy. Write 8 scenario-based training questions to check that staff understood it. The policy's key rules: (a) only approved tools for project data; (b) model-training opt-out on before first use, or a business plan where training is excluded by default; (c) never paste client-confidential documents, personal data or NDA material into unapproved tools; (d) AI output on codes, products, quantities and contract language is a draft verified by a qualified person against the source; (e) significant AI use on a project is logged; (f) no AI imitation of another architect's recognisable work; (g) report mistakes and near-misses without blame. Each question: a realistic office scenario, 3 answer options, the correct option, and a one-sentence explanation tied to the rule letter. Keep each question under 70 words.

Turn these messy notes into one row of an AI use log for a project record. Columns: Date | Project | Person | Tool and plan | Task | Data entered (and confidentiality level) | Output used where | Verification done (by whom, against what) | Risk tier. If a field is missing from the notes, write MISSING rather than inventing it. Then list the missing fields as questions to ask the person.

Notes: "[paste your notes]"

Turn my scattered notes from last week into a Monday project digest. For
each project: status in one line, decisions waiting on me (and who is
waiting), deadlines in the next two weeks, and anything that reads urgent.
Order projects by how much attention they need today. Put notes you cannot
place under "review by hand" instead of guessing. Notes: [paste]

Draft a one-page memo of ground rules for using chat assistants in an
architecture office of [size]. Cover: material that never gets pasted
(client identifying data, anything under NDA, unpublished financials);
account settings to change before first use, naming the model-training
toggle; the rule that anything touching codes, products or contract language
is a draft a licensed professional verifies; and who in the office answers
questions. Plain language. I will align it with our insurer and counsel
before issuing.

Write a project description for my studio's website from the facts I paste:
type, size, location in general terms, design approach, key decisions,
materials. Match the voice of the sample description I include. 150 to 220
words. No superlatives the facts do not support, no client name unless I
marked it approved. Facts: [paste] Voice sample: [paste]

I paste two product data sheets for [product type], separated by ===. Build
a comparison table using only values that appear on the sheets: criterion,
product A, product B, and "not stated" where a sheet is silent. Criteria:
[list]. Flag any criterion where the two sheets report values under
different test standards, and do not convert between standards. Sheet A:
[paste] === Sheet B: [paste]

Here is my room program. 1) Sum the net areas. 2) Apply a grossing factor of [factor] to get gross floor area. 3) The limit is [limit] m2 gross - state whether we fit, and by how much we are over or under. 4) If we are over, calculate how much net area we must cut to fit. 5) State the net-to-gross efficiency as a percentage. Show the arithmetic step by step. I will paste the program below, all areas in m2 net.

Screen my draft plant palette, do not add plants of your own. I paste my
candidate list and the site conditions (location, USDA zone or local
equivalent, soil, sun, moisture, space available, maintenance level). For
each plant return a table row: botanical name as I wrote it; whether that
name looks current or possibly a synonym/misspelling (flag, don't rename);
stated zone fit vs my zone; mature size vs the space I listed; soil and sun
fit; one risk to verify (invasiveness in my region, disease, availability).
End with the list of flags I must verify against my regional flora,
extension service or nursery availability before this palette goes in a
drawing. Site: [paste] Palette: [paste]

Turn my phone-dictated site visit notes into a site observation report under:
Access and approach / Topography and drainage / Existing structures and
condition / Utilities observed / Neighboring context / Vegetation / Items to
verify with a survey or authority. Keep every measurement exactly as I
dictated it; where my notes are ambiguous, list the item under Items to
verify instead of resolving it. Do not infer typical conditions for this
region. Notes: [paste]

Draft an outline specification skeleton for [section]. Structure only:
Part 1 General (submittals, quality assurance, warranties), Part 2 Products
(materials, components, finishes), Part 3 Execution (preparation,
installation, tolerances, protection) - as headings with the questions I
must answer under each. Write [VERIFY] wherever a standard, test value or
code reference belongs; do not supply the reference from memory. One page
maximum.

Translate the specification section below into a plain-language summary for a client who is not a construction professional. Explain what is being specified, the quality level chosen and what it means in practice, and which decisions are still open. Maximum 300 words. Add one line at the end stating that the specification document itself, not this summary, is the binding text.

I will paste excerpts from manufacturer datasheets for [product type, e.g. mineral wool insulation boards] from several manufacturers. Build a comparison table: manufacturer, product line, the performance values stated in each excerpt (with the exact wording), and gaps where an excerpt does not state a value. Add a [VERIFY] row listing what must be confirmed on current manufacturer documentation before any of this enters a specification. Use only the pasted excerpts - no outside knowledge of these products.

I am an architect reviewing a client brief for a new project. I will paste the full brief below. After reading it, give me: 1) the stated space program with areas, as a table; 2) every quantitative requirement (areas, budgets, dates, parking) with the sentence it came from; 3) requirements that conflict with each other, with the arithmetic shown; 4) decisions the brief leaves open that the client must make before schematic design. Quote the brief verbatim for anything you flag, so I can check it in the source.

I will paste a project brief below. List the questions a client must answer before schematic design can start, grouped: budget and program; site and context; operations and users; quality and sustainability expectations. For each, say in one line what it blocks if unanswered. Only ask what the brief genuinely leaves open.

I am an architect reviewing a client brief for a new project. I will paste the full brief below. After reading it, give me: 1) the stated space program with areas, as a table; 2) every quantitative requirement (areas, budgets, dates, performance targets) with the page or section it came from; 3) requirements that conflict with each other; 4) decisions the brief leaves open that the client will need to make before schematic design. Quote the brief verbatim for anything you flag, so I can check it in the source.

I am deciding whether my firm should respond to an RFP. I will paste the full RFP below. Summarize: 1) scope of services; 2) evaluation criteria with any stated weights; 3) minimum qualifications and required team roles; 4) submission requirements, page limits and deadlines; 5) anything unusual for this project type that I should price or clarify before committing. Keep it to one page and cite the RFP section for each point.

I am deciding whether my firm should respond to an RFP. I will paste the relevant excerpt below. Summarize on one page: 1) scope of services; 2) evaluation criteria with stated weights; 3) minimum qualifications; 4) submission requirements and deadlines; 5) anything unusual or risky for a firm my size that I should price or clarify before committing - contract liability terms included. Cite the RFP section for each point.

I am an architect starting site analysis for a [project type] on the site described
below. I will paste my raw material: survey notes, the zoning extract I have
verified, climate notes, and my own site visit observations.

Build a site analysis synthesis with three parts:
1. A table of observations: each site condition, its source in my material
   (quote the line), and the design question it raises.
2. Opportunities and risks: two plain lists, each item tied to a specific
   observation - no generic entries that could apply to any site.
3. Missing information: what an architect would still need to verify before
   schematic design, as a checklist.

Use only the material I paste. If something is not in my material, put it in
the missing-information list instead of guessing. Do not propose a design.

My material: [paste]

Below are my raw notes from client meetings about a [project type]. Draft a space program table: space name, quantity, target area, key adjacencies, special requirements. Where the notes imply a space without naming it, include it flagged [implied]. Where area targets are missing, write [NEEDS INPUT] - do not invent numbers.

Draft an email to my client. Situation: a design milestone will slip by [number] weeks because [reason]. Requirements: open with the revised plan rather than the problem; explain the cause in two sentences without blaming anyone; propose what we will progress in parallel so the end date is protected as far as possible; close with a specific next step and date. Professional, direct, no apologetic filler. Under 250 words. I will review and personalize before sending.

Turn my raw meeting notes, pasted below, into minutes with: attendees; decisions made; open questions; and an action table with columns for item, owner, deadline. Where the notes imply an owner or deadline without stating one, mark it [confirm] rather than guessing. Keep the wording factual - no interpretation of anyone's intent.

I will paste excerpts from the accessibility standard applying to my project, plus a description of the spaces in question. Using only the pasted text, list each requirement with its clause number and phrase it as a yes/no question about my design. Mark questions the pasted text cannot settle "needs full standard". This structures my review - it does not replace it.

I will paste excerpts from the building code that applies to my project, including the edition year and jurisdiction. Answer my questions using ONLY the text I provide. For every answer, quote the exact clause and its number. If the pasted text does not cover my question, say "not covered in the provided text" - do not answer from general knowledge. First question: list every requirement in these excerpts that applies to [describe the element], as a checklist with clause references.

I am an architect starting code research for a project. Act as a research assistant, not a compliance checker. Project: [one-paragraph description - building use, storeys, construction type if known, jurisdiction and adopted code edition]. Produce: (1) a list of the code chapters and section families I most likely need to review for this project type, each with one line on why; (2) for each, the project-specific question I need to answer; (3) a verification list - what I must confirm in the adopted local code and amendments before relying on anything, including the edition year and renumbering risk between editions. Do not state final requirements as settled numbers; frame everything as sections to open and verify.

I asked an AI assistant some building-code questions and got answers with section numbers. Turn the answers I paste below into a verification log table with columns: claim, code edition cited, section cited, what to check at the source, risk if wrong, status (blank for me to fill). Add a final row for jurisdiction amendments. Do not tell me whether the claims are correct - the log is for my own source check.

I am an architect preparing to rely on building-code research. Build me a local-amendment checklist for the following code sections: [code edition and section numbers], in a US jurisdiction whose state adopts the IBC with amendments. List, as a checklist: (1) where state and city amendments are typically published; (2) the specific questions to ask about each of these sections; (3) the renumbering risk - which of these section numbers changed between editions; (4) who to contact when the adopted edition is unclear. Frame every item as something I verify, not something you confirm.

Before I analyze a zoning ordinance, extract every defined or ambiguous term from the ordinance text I paste, and for each term tell me: where it is used, whether the pasted text defines it, and what I need to look up in the full ordinance's definitions chapter before relying on any analysis. Use ONLY the pasted text; do not supply definitions from general knowledge.

I will paste the text of a zoning ordinance section and the basic parameters of a site and proposed building (use, lot area, frontage, height, setbacks, parking). Build a two-column table: each zoning requirement from the pasted text with its clause number, next to my proposed value, marked "appears to meet", "appears short" or "unclear from provided text". This is a first-pass screen to organize my own review. Do not state that anything complies.

Turn my raw site visit notes, pasted below, into a field report: project, date, weather, work observed in progress; items requiring attention with location and the drawing reference where I noted one; open questions for the contractor; photos referenced by my note numbers. Factual wording only - observations, no directives and no acceptance of work.

Organize my raw walkthrough notes, pasted below, into a punch list: items grouped by room, then by trade; each item as location, deficiency, reference to spec or drawing where my notes include one. Keep my wording for deficiencies - clean it only for clarity. Number items. Mark entries too vague to action [CLARIFY] so I can revisit them on site.

I will paste a contractor RFI and the relevant drawing notes and specification clauses. Draft a response that: answers only what was asked; cites the controlling document and clause for each point; states "to be confirmed" where my pasted material does not settle the question. Neutral contractual tone. Note at the end if the question suggests a document conflict I should review. I will review and edit before issuing.

I will paste 1) the specification clauses governing a submittal and 2) the submitted product data. List: each spec requirement next to what the submittal shows, marked "appears to conform", "deviation" or "not addressed"; deviations the contractor flagged versus unflagged ones. Quote both documents. This organizes my review - the review action and stamp are mine.

I will describe the current state of a [project type] design. For each discipline - structural, mechanical, electrical, plumbing, [add others] - list the questions my drawings must answer for that consultant to progress, and the decisions I need FROM them before my next issue. Mark items that typically block others first. Base it only on what I describe.

Turn my coordination meeting notes, pasted below, into a decision log: decision made, who made it, what it affects, drawings or documents to update; a second table of open items with owner and deadline. Where the notes imply a decision without stating it cleanly, put it under open items marked [confirm] - never promote it to decided.

I will paste a value-engineering proposal list. For each item, using only what I paste plus the design intent I describe: what the substitution changes in appearance, performance and maintenance; which stated design intent it touches; what I would need to verify before accepting (testing, warranty, code acceptance). Neutral wording I can send to a client after my review. Mark items needing consultant input [REFER].

Draft a concept narrative for a [project type]. Inputs below: 1) bullet-point facts about site, program and my design moves; 2) one narrative my firm wrote previously, as a style reference - match its tone, never copy its content. Use only facts from input 1; where a topic lacks a fact, write [NEEDS INPUT]. 400-600 words, for a client audience.

I will describe [number] design options for the same brief. Build a comparison table: how each option answers the program; site response; structural implications I listed; rough relative cost drivers; risks and unknowns. Use only what I describe - no invented benefits. Close with the questions the client must answer to choose, as a numbered list.

Act as a skeptical design reviewer. I will describe my concept for a [project type] below. Identify: where stated intent and described execution diverge; program requirements the scheme strains; circulation or organization weaknesses; claims a jury or planning officer would press hardest. Be specific and quote my own description back at me. End with the three hardest questions I should prepare for.

Rewrite the draft text I paste below so it reads like a practicing architect wrote it for a client presentation. Keep every fact, number, dimension and caveat exactly as given. Remove marketing language, repeated ideas and filler phrases. Shorter is better. Flag any sentence whose meaning you were unsure about rather than guessing.

Draft a design statement for a planning submission. I will give you three inputs below: 1) bullet-point facts about the site, context and proposal; 2) the local authority's list of what the statement must address; 3) one design statement my firm wrote previously, as a style reference - match its tone and sentence rhythm, never copy its content. Only use facts from input 1. Where a required topic from input 2 has no matching fact, write the heading and the note [NEEDS INPUT] instead of inventing anything.

Build a construction documents QA checklist for a [project type]: cross-referencing (plans to schedules to details to specs); dimensional completeness; typical coordination failure points between architectural and [consultant disciplines] drawings; common omissions for this building type. Checklist format, grouped by review pass. This structures my review of the set - it cannot see my drawings and verifies nothing itself.

Check the drawing notes against the specification excerpt below and list every contradiction you find as a table: topic, what the drawings say, what the spec says, and which document I should probably correct. Also flag any reference that points to a document that does not exist in the list provided. Do not invent contradictions that are not there.

I will paste the general notes from my drawing set. Find: notes that contradict each other; duplicates with different wording; notes referencing standards or documents inconsistently; notes that belong in the specifications instead. Quote each instance with its note number. Do not rewrite - list for my edit.

Write a complete pyRevit script (IronPython 2.7 compatible) that renumbers all doors in the
active Revit document by the room they open into: each door gets its ToRoom number (phase-aware,
last phase), with an A/B/C suffix when a room has several doors. Requirements: __title__ and
__doc__ header; imports from pyrevit (revit, DB, script); FilteredElementCollector over OST_Doors;
FromRoom fallback when ToRoom is empty; one named Transaction for all writes; write to the Mark
parameter with a read-only guard; skip and report doors with no room; include a DRY_RUN flag
that previews the result without writing. After the script, list your assumptions and what I
must check before running it on a live model.

Using only the Revit MCP read tools, audit this model: which doors are missing a fire rating?
Before querying, check how the fire rating is actually stored: the built-in type parameter,
a shared instance parameter, or another name. Query the whole model, not the active view.
Classify each door: parameter absent, value empty, placeholder value ("-", "N/A", "TBD"),
or rated. Report counts per bucket, the exact parameter name you checked, and the query scope.
Then select the unrated doors in Revit so I can verify them myself. Do not modify anything.
After the summary, list the ways this audit could be wrong or incomplete in this model.

Draft a letter to a client about additional services. Facts below: original scope summary; the requested changes to date with dates; the contract clause covering additional services, quoted. Tone: collaborative and firm. Structure: what was included; what has changed; why the new work sits outside the base fee; the proposed path (estimate first, then authorization). Under 400 words. I will review against the signed contract before sending.

Review this indemnification clause from a client-drafted agreement for architectural services and tell me: 1) each specific risk it creates for my firm, in plain language; 2) how it differs from a negligence-based standard; 3) the questions I should take to my lawyer and insurance broker before signing. Do not rewrite the clause; do not present your analysis as legal advice - frame it as issues to raise with counsel. I will paste the clause below.

You are helping a small architecture practice classify its AI uses by risk. Use three tiers plus a prohibited category:
- Low: internal, no client data, quick reasonableness check by the user.
- Medium: client-facing or informs design decisions; output checked against a trusted source; noted in the project record; PM approval.
- High: informs stamped/sealed documents, life safety, accessibility, code interpretation, structural assumptions or contract language; AI only as an exploratory/checking aid; fully re-verified by a qualified person; logged; architect-of-record approval.
- Prohibited: anything barred by client contract or law, or pasting confidential client data into a tool not on the approved list.

Classify each of these uses. For each, give: tier, one-line reason, the required check. Output a markdown table only, then one line naming any item you were unsure about and why.

[paste your list of AI uses, one per line]

Below is the data-use section of an AI tool's terms that a staff member wants the office to adopt. Read it and fill this table: | Question | Answer from the text | Exact quote | Risk for an architecture firm |. Questions: (1) Does the vendor train on our inputs by default? (2) Can we opt out, and how? (3) How long are inputs retained? (4) Who owns outputs? (5) Can the vendor share data with third parties? (6) Is there a business/commercial plan with different terms? If the text does not answer a question, write NOT STATED - do not guess. After the table, give a verdict in at most 3 lines: approve / approve with conditions / reject, and the conditions.

TERMS EXCERPT:
[paste the data-use section of the tool's terms]

Draft a one-page internal guideline for AI chat tools in an architecture practice of [size] in [country]. Cover: material that must never be pasted (client-confidential documents, personal data, anything under NDA); required account settings before use, with model-training opt-out named explicitly; the rule that AI output on codes, products and contracts is a draft requiring professional verification; who in the office answers questions. Plain language, fits one page. I will adapt it to our insurance and legal advice.

I will paste manufacturer information for [number] candidate products for [application]. Build a comparison table using only the pasted data: key performance values, dimensions, finish options, stated warranty, anything one datasheet covers that another omits. Add a [VERIFY] row listing claims I must confirm directly with each manufacturer - current availability, lead time, local code acceptance and price are always on it.

I am an architect starting my first [building type] project in [country or region]. List what I should research before concept design: regulatory frameworks and review bodies typical for this type; typical functional requirements and adjacencies; common dimensional standards; typical consultants needed; the questions experienced designers of this type ask first. Format as a checklist I can work through, with [VERIFY LOCALLY] on anything jurisdiction-dependent.

I will paste site information below (survey notes, deed description, utility records, my own observations). Build a site constraints summary: dimensions and area; topography; access; utilities; easements or restrictions; anything in the documents that limits buildable area. Quote the source document for each item and list what information is still missing for a [project type].

Draft an outline specification for Section [number and title], in CSI 3-part format (Part 1 General, Part 2 Products, Part 3 Execution), for a [project type and location]. [Scope notes: interior/exterior, finishes, fire ratings.] Keep it an outline: numbered articles and short clauses, not full prose. Where you reference a standard (ANSI, NAAMM, UL and similar), add [VERIFY EDITION] after it, and do not invent product model numbers.

I will paste a product and materials schedule for a project. Draft outline specification sections organized by CSI MasterFormat division. For each section include: section number and title, a short description, the products from my schedule that belong there, and a [VERIFY] list of what must be confirmed with manufacturers or consultants before the section is developed. Do not invent product names, standards or performance values that are not in my schedule.

Below are (A) the general and keyed notes from our drawings and (B) a draft specification section for the same scope. List every inconsistency between them: terminology that differs for the same item, materials mentioned in one but not the other, dimensions or performance requirements that conflict, and notes that reference spec sections that do not exist in the package list I provide. Format as a table: item / what A says / what B says / suggested resolution. Do not rewrite either document.

I will paste a section from our office master specification, then a one-paragraph description of this project's scope. Edit the master down to what this project needs. List every paragraph you deleted and why, every paragraph you modified with before/after text, and anything in the master that looks outdated and should be checked. Do not add new requirements, products or standards.

I will paste a specification package from a previous project that we are using as a reference. For a project of this scope - [describe project type and scope in one sentence] - list: 1) which MasterFormat divisions are covered; 2) divisions this project will likely need that are missing; 3) sections whose requirements look unusual or contradictory, with the clause quoted. Review only - do not rewrite anything.

Review the specification section below as a skeptical senior spec writer. Flag: any product name or model number (each needs manufacturer verification), any code or standard citation (each needs edition and jurisdiction verification), any performance value (each needs a source), warranty terms that differ from standard practice, and any clause that assigns design responsibility to the contractor. Return a numbered list with the quoted text and why it needs attention. You are a reviewer - change nothing.

Draft specification section [number and title, e.g. 08 11 13 Hollow Metal Doors and Frames] in CSI 3-part format (Part 1 General, Part 2 Products, Part 3 Execution) using ONLY the project information I paste below. Where standard practice requires a reference standard, a product, or a performance value that my input does not contain, write [VERIFY: what is needed] instead of a value. Do not cite any code section or ASTM/ANSI standard number unless it appears in my input.

From the specification sections I paste below, extract every submittal requirement into a register: section number, submittal item, type (product data / shop drawings / samples / test reports / closeout), and the exact clause text that requires it. Flag any section that has requirements in Part 2 or Part 3 but no corresponding submittal article, and any duplicate requirements across sections. Extraction only - do not add requirements.

I am an architect reviewing a client brief for a new project. I will paste
the full brief below. After reading it, give me: 1) the stated space program
with areas, as a table; 2) every quantitative requirement (areas, budgets,
dates, parking) with the sentence it came from; 3) requirements that
conflict with each other, with the arithmetic shown; 4) decisions the brief
leaves open that the client must make before schematic design. Quote the
brief verbatim for anything you flag, so I can check it in the source.

I am deciding whether my [N]-person architecture firm should respond to an
RFP. I will paste the relevant excerpt below. Summarize on one page: 1) scope
of services; 2) evaluation criteria with stated weights; 3) minimum
qualifications; 4) submission requirements and deadlines; 5) anything unusual
or risky for a firm my size that I should price or clarify before committing.
Cite the RFP section for each point.

A 16:9 oblique aerial photograph, taken as if from a drone at about 60 metres, of a proposed [primary school / health centre] on a [riverside / edge-of-town] site. The building is a low two-storey courtyard scheme with a sawtooth roof over the larger wing, surrounded by existing [terraced housing / farmland / industrial sheds]. Materials: pale grey fibre-cement panels on the walls, a planted sedum roof on the flat sections, and timber-lined window reveals. Morning light from the east, slight haze towards the horizon. No people, no cars, no text, no watermark. Photorealistic architectural photography.

A clean exploded axonometric diagram of a [three-storey timber-frame community building], viewed from the south-east, with the roof, each floor plate, the structural frame and the ground floor slab separated vertically and aligned on a common axis. Each layer labelled in a small sans-serif font with these exact labels: "Sedum roof", "CLT roof panels", "Second floor", "First floor", "Glulam frame", "Ground floor slab". Thin leader lines from each label to its layer. Flat pastel colours, white background, no shadows, no people, square 1:1 frame.

Use the uploaded 2D floor plan as the exact layout. Produce a 3D isometric cutaway view of this plan seen from above at a 45-degree angle, with walls extruded to a consistent height of about one storey, all door and window openings in the positions shown, and no rooms added, removed, merged or resized. Keep room proportions exactly as drawn. Floors in pale oak, walls in matte white, simple furniture placed only where the plan indicates it. Clean white background, soft shadows, no text or dimensions, square 1:1 frame.

Use the uploaded site photograph as the base. Keep the sky, the neighbouring buildings, the road, the trees, the people and the lighting exactly as photographed; the only change is to add a new building on the [empty plot / fenced site] in the centre of the frame. The new building: a three-storey volume with a flat roof, a brick ground floor in pale buff brick, two upper floors in dark grey standing-seam metal, and regular vertical windows with deep reveals. Match the camera height, perspective, lens and light direction of the photograph. No text, no watermark. Photorealistic architectural photography.

Use the uploaded image as the base. Keep the exact same massing, window positions, floor count, roofline, camera, lighting, site and sky. The only change: replace the [current cladding, e.g. white render] on the upper floors with [new cladding, e.g. vertical untreated larch boards weathered to silver-grey], with the same board direction across every elevation visible in the image. Leave the ground floor, the window frames and everything else exactly as shown. No text, no watermark. Photorealistic architectural photography.

A single 16:9 image divided into three equal panels, side by side, each showing the same [rectangular / L-shaped] site from the same high aerial viewpoint at the same scale. Left panel: one long linear block along the north edge with a courtyard to the south. Middle panel: two parallel blocks with a shared garden between them. Right panel: a compact square block in the centre of the site with open space on all four sides. All three volumes are three storeys, rendered as plain white model massing with no windows, on a neutral grey site plate with existing neighbouring buildings shown in light grey. Soft studio lighting, no text or labels.

A wide 16:9 eye-level photograph of a two-storey [house / community library / small office] on a [sloping suburban / flat rural / tight urban infill] site in [city or region]. The building is a simple rectangular volume with a single-pitch roof falling towards the street, a recessed entrance on the left third of the facade, and a full-height glazed bay on the right. Materials: pale lime-washed brick walls, a dark standing-seam zinc roof, and untreated larch boards on the recessed entrance. Mature trees behind the building, a gravel forecourt in front. Late afternoon sun from the left, long soft shadows. No people, no cars, no text, no watermark. Photorealistic architectural photography.

Draft an outline specification for Section [number - title], in CSI 3-part
format (Part 1 General, Part 2 Products, Part 3 Execution), for a [project
type and location]. [Key conditions: interior/exterior, finishes, fire
ratings.] Keep it an outline: numbered articles and short clauses, not full
prose. Where you reference a standard (ANSI, NAAMM, UL and similar), add
[VERIFY EDITION] after it, and do not invent product model numbers.

Use the uploaded image as the base. Keep the exact same building, massing, window positions, floor count, roofline, materials, site and camera. The only change is time of day: convert the scene to a clear evening about thirty minutes after sunset, deep blue sky, warm interior light visible through the windows on all floors, soft downlighting at the entrance, street lamps on, no illuminated signage. Keep all surroundings in their photographed positions. No people, no cars, no text, no watermark. Photorealistic architectural photography.

Use the uploaded facade photograph as the base. Keep the exact same massing, window positions, window sizes, floor count, roofline, doors, camera and lighting from the photograph. The only change: replace the existing [painted render / tired brick / grey panel] cladding with [new material, e.g. glazed white terracotta baguettes] across the whole facade, with [slim bronze] window frames replacing the existing frames in the same openings. Leave the street, sky, neighbouring buildings and all people and vehicles exactly as photographed. No text, no watermark. Photorealistic architectural photography.

Image A is a photograph of a physical study model; Image B is a photograph of the real site. Use Image A for the building's massing, proportions, window openings and roofline, kept exactly as modelled; do not add floors or openings. Use Image B for the site, surroundings, horizon and lighting. Place the building on the site at the position of the [empty plot / existing car park] in Image B, matched to the camera height and perspective of Image B. Materials: [material 1] walls, [material 2] roof, [material 3] window frames. Keep everything else in Image B exactly as photographed. No people, no cars, no text, no watermark. Photorealistic architectural photography.

Use the uploaded model screenshot as the source of all geometry. Keep the exact same massing, window positions, floor count, roofline, column positions and camera from the screenshot; the only changes are materials, lighting and context. Apply these materials: [material 1, e.g. board-formed concrete] on the ground floor, [material 2, e.g. vertical charred-timber cladding] on the upper floors, [material 3, e.g. slim black aluminium] window frames. Replace the blank model ground with a paved forecourt and low planting. Golden hour backlighting creating long shadows, slight lens flare. No people, no cars, no text, no watermark. Photorealistic architectural photography.

Use the uploaded hand sketch as the only source of geometry. Keep the exact same massing, window positions, floor count, roofline, proportions and camera angle from the sketch. Do not add floors, change the roof pitch, or move openings. Render the building as a finished photograph: walls in rough textured render painted warm white, the roof in dark grey clay tiles, window frames in dark timber. Site as drawn, with the existing [tree / wall / neighbouring building] kept in place. Soft late-morning light from the right. No people, no cars, no text, no watermark. 3:2 landscape frame. Photorealistic architectural photography.