precedent-research
Skill39 starsChanged 23 days agoMITView on GitHub
Research and compare architectural precedents by typology, climate, program, circulation, structure, envelope, materials, construction, performance and design intent. Use for precedent studies, case-study matrices, design references, lessons learned, and evidence-backed concept inputs.
In this repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- architectural-drawing-generationSkill
- architecture-orchestratorSkill
- architecture-programmingSkill
- architecture-red-teamSkill
- area-quantity-auditSkill
- autocad-dwg-workflowSkill
- building-envelope-performanceSkill
- cad-bim-automationSkill
- civil-site-designSkill
- concept-design-reviewSkill
- concept-schematic-designSkill
- construction-administrationSkill
- construction-documentationSkill
- cost-planning-value-engineeringSkill
- drawing-qaSkill
- handover-fm-postoccupancySkill
- interior-fitout-designSkill
- life-safety-accessibilitySkill
- materials-specificationsSkill
- mep-coordinationSkill
- openbim-ifc-coordinationSkill
- presentation-reviewSkill
- revit-workflowSkill
- rhino-grasshopper-workflowSkill
- site-analysis-feasibilitySkill
- site-regulation-researchSkill
- structural-coordinationSkill
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use precedents as evidence and transferable lessons, not as designs to copy.
- Very specific: line 15
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.
- Distinctive: line 34
Do not infer hidden structural, cost or performance data from photographs.
- Distinctive: line 41
Do not present resemblance to a precedent as proof of performance or compliance.
- Distinctive: line 45
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Architectural Precedent Research
Use precedents as evidence and transferable lessons, not as designs to copy.
Preflight
- Project type, scale, climate, site/context and design question.
- Which attributes matter: plan, section, circulation, facade, structure, envelope, material, public realm, flexibility, sustainability or delivery.
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.
Workflow
- Find primary project sources, architect/engineer documentation, reputable publications and drawings where legally available.
- Extract comparable facts into a matrix; distinguish documented fact from visual interpretation.
- Identify transferable principles and failure risks; explain why each precedent is relevant to this project.
- Translate findings into design criteria rather than stylistic imitation.
Deliverables
- Sourced precedent matrix
- Diagram brief for plan/section/massing comparisons
- Transferable principles
- Open questions and evidence gaps
Verification
- Citations identify project/source and date where available.
- Do not infer hidden structural, cost or performance data from photographs.
For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.
Professional boundaries
- Respect copyright; summarize and diagram rather than reproducing protected drawing sets.
- Do not present resemblance to a precedent as proof of performance or compliance.
If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.
If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.