life-safety-accessibility
Skill39 starsChanged 23 days agoMITView on GitHub
Coordinate architectural life-safety and accessibility design using verified jurisdiction-specific requirements. Use for occupancy/egress studies, exit and travel-path checks, fire-compartment coordination, accessible routes, ramps/lifts, sanitary access, refuge, door clearances and code-review matrices.
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
- materials-specificationsSkill
- mep-coordinationSkill
- openbim-ifc-coordinationSkill
- precedent-researchSkill
- 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
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
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
Treat safety rules as jurisdiction- and edition-dependent.
- Very specific: line 15
Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.
- Distinctive: line 19
Create a requirement matrix with source, clause, edition, applicability and status.
- Distinctive: line 33
No numeric criterion is used without an authoritative source and edition.
- Distinctive: line 40
Never certify fire, egress or accessibility compliance.
- Distinctive: line 41
Do not substitute this skill for fire engineering, accessibility consultancy or authority review.
- 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
Life Safety & Accessibility Coordination
Treat safety rules as jurisdiction- and edition-dependent. Source every requirement before using it as a pass/fail criterion.
Preflight
- Exact jurisdiction, adopted code/standard editions, occupancy/use, construction type when relevant, sprinkler/fire strategy inputs, floor areas and occupant data.
- Accessible-user requirements, levels, routes, doors, vertical circulation, sanitary/support spaces and authority interpretations already received.
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
- Create a requirement matrix with source, clause, edition, applicability and status.
- Trace accessible and egress routes through plans/sections; identify bottlenecks, discontinuities, level changes and door conflicts.
- Coordinate fire separations, exits, stairs, lifts/refuge and service penetrations with the responsible specialists.
- Report confirmed passes, conflicts, missing evidence and questions for the authority/fire/accessibility consultant.
Deliverables
- Life-safety/accessibility matrix
- Annotated route/egress review
- Conflict and missing-evidence register
- Questions for qualified reviewers
Verification
- No numeric criterion is used without an authoritative source and edition.
- Plan geometry, occupant assumptions and route lengths are traceable to supplied data.
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
- Never certify fire, egress or accessibility compliance.
- Do not substitute this skill for fire engineering, accessibility consultancy or authority review.
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.