site-regulation-research
Skill39 starsChanged 24 days agoMITView on GitHub
Research and structure site, zoning, planning, building-code, accessibility, fire, and local-authority constraints with source/date traceability. Use whenever architecture work depends on jurisdictional requirements.
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
- precedent-researchSkill
- presentation-reviewSkill
- revit-workflowSkill
- rhino-grasshopper-workflowSkill
- site-analysis-feasibilitySkill
- structural-coordinationSkill
- sustainability-daylight-energySkill
- visualization-renderingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Do not claim permit approval or definitive compliance.
≈ “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
Site & Regulation Research
Establish exact jurisdiction, project type, stage, and source version/date before treating a rule as applicable. Prefer official authorities, legislation, regulations, adopted plans, and published guidance.
For each material control record topic, requirement, applicability, numeric value if any, source title, clause/page/link/file, date/version, and confidence/status.
Separate confirmed requirement, interpretation, project assumption, and items requiring authority/professional confirmation.
Do not claim permit approval or definitive compliance. Flag planning/legal, accessibility, fire/life-safety, structural, and construction-critical conclusions for competent human review.
Offline source-edition triage
For explicit jurisdiction/source-edition requests, read source selection and limits, then use this skill's own scripts/select_sources.py with a project context. Its bundled references/source-registry.json is citation metadata, not an approved rule pack. The command reports missing/stale/draft/wrong-jurisdiction evidence and never activates a rule or issues compliance PASS. Do not substitute drawing-profile defaults for adopted building regulations.
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.