life-safety-accessibility
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.
MakeItEzzz555 · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add MakeItEzzz555/Gridline --skill life-safety-accessibility技能说明
name: life-safety-accessibility description: 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.
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.