Research site context and precedents
Working with AgentReview draft
On this page
Explicitly ask Agent to search and define the question. You can also provide a webpage URL for it to read and summarize.
Define scope
For sites, specify location, boundary and questions. For precedents, specify building type, scale, users or design conditions. Add date requirements when current information matters.
For example: “Find built factory-to-community-space conversions. Compare retained structures and public activity areas; include project and source links.” This gives a clearer comparison than “find good examples.”
Review results and sources
Check the evidence behind each conclusion, then open sources to verify names, locations, dates and approaches. Send a link back with a focused extraction request when more detail is needed.
| Content | What to verify |
|---|---|
| Project facts | Original evidence, dates and consistent definitions |
| Images | Correct project; completed photographs versus renderings or other representations |
| Comparisons | Consistent criteria and contrary evidence |
| Recommendations | What comes from precedents versus inference about your project |
Inaccessible pages, snippets and conflicting sources need further checking before becoming confirmed presentation claims.
Use the research
Select useful evidence and identify what to borrow: spatial organization, materials, circulation or another aspect. Discuss directions using both references and project constraints.
For regulations, provide jurisdiction, building type and purpose; use the relevant code-search capability to check source and scope. General web search is not professional project review.
Code research · Research-to-concept tutorial · Use References · Documentation