ada-plan-view-accessibility
$
npx mdskill add elizaOS/eliza/ada-plan-view-accessibilityUse this skill for plan-view accessibility checks. It is not a full legal ADA compliance review; apply only the geometric rules provided by the task.
SKILL.md
.github/skills/ada-plan-view-accessibilityView on GitHub ↗
--- name: ada-plan-view-accessibility description: Use when checking simplified ADA-derived plan-view bathroom accessibility constraints such as turning space, door clear width, toilet centerline, grab bars, and lavatory knee/toe clearance. --- Use this skill for plan-view accessibility checks. It is not a full legal ADA compliance review; apply only the geometric rules provided by the task. ## Plan-View Checks - Door clear opening: compare the submitted clear width against the minimum in the rules file, commonly 32 inches. - Door swing: if the rule disallows swing into required fixture clearance, prefer an outward or sliding swing in the repaired layout. Do not leave an inward repaired swing unless you have explicitly modeled and cleared the swing path against fixtures and required clearances. - Turning space: verify that a 60 inch diameter circle fits inside usable floor area. Diameter alone is not enough. Apply the wall/boundary offset from the rules, subtract protected or blocked fixtures such as tubs, and allow overlap with toilet clear floor space only when the rules say so. - Lavatory overlap: allow the turning circle to overlap a lavatory only when plan-view knee/toe clearance is explicitly indicated and meets the required width and depth. - Toilet centerline: measure from the adjacent side wall and keep it inside the rule range, commonly 16 to 18 inches. - Grab bars: classify rear-wall and side-wall bars by orientation/location and compare their plan-view lengths against the minimums. The side-wall grab bar should align with the same adjacent side wall used for the toilet centerline and overlap the toilet use zone. The rear-wall grab bar should align with the rear wall behind the toilet and cross or closely span the toilet centerline. ## Violation Reporting Report one violation per failed rule/element pair. Use stable machine-readable rule names from the rules file, for example: - `door_clear_width_min` - `turning_circle_diameter_min` - `turning_circle_fit_usable_floor` - `toilet_centerline_from_side_wall_range` - `side_grab_bar_length_min` - `rear_grab_bar_length_min` - `side_grab_bar_toilet_side_wall_alignment` - `rear_grab_bar_toilet_centerline_span` - `lavatory_knee_clearance_min` Do not report vertical requirements such as seat height, mounting height, mirror height, signage height, or pipe protection if the task scope excludes them. Use combined rule names for range checks. For example, if the toilet centerline is outside the allowed range, report `toilet_centerline_from_side_wall_range`; do not invent separate `*_min` or `*_max` violation names unless the rules file explicitly asks for them. Use the element id that matches the failed requirement's scope: - For toilet centerline failures, use the toilet id, such as `WC1`. - For room-level turning-circle fit failures, use the room id, such as `bathroom_1`, because the failure is about whether usable floor area can contain the full circle. - For grab-bar length failures, report them only after classifying the actual side-wall and rear-wall grab bars. Do not report grab-bar failures when the classified bars meet the minimum lengths. - For lavatory knee/toe clearance, report a violation only when the lavatory lacks the indicated plan-view knee/toe clearance or the stated width/depth is below the rule minimum. Do not infer a before-repair violation from unrelated fixture graphics when the extracted lavatory metadata satisfies the rule. ## Repair Principles - Preserve existing walls and fixtures whenever a local move or small expansion solves the problem. - Prefer changing door swing/opening representation over redesigning the whole room. - Keep protected fixtures such as tubs in place unless the rules make that impossible. - If the toilet moves, update or validate the grab-bar segments against the repaired toilet position. - Make every repair traceable to a violation or to preserving a valid clearance.
More from elizaOS/eliza
- ac-branch-pi-modelAC branch pi-model power flow equations (P/Q and |S|) with transformer tap ratio and phase shift, matching `acopf-math-model.md` and MATPOWER branch fields. Use when computing branch flows in either direction, aggregating bus injections for nodal balance, checking MVA (rateA) limits, computing branch loading %, or debugging sign/units issues in AC power flow.
- academic-pdf-redactionRedact text from PDF documents for blind review anonymization
- analyze-ciAnalyze failed GitHub Action jobs for a pull request.
- architectural-dxf-extractionUse when extracting plan-view architectural geometry from DXF files with semantic CAD layers, especially when outputs must normalize rooms, doors, fixtures, clearances, and grab bars into machine-checkable JSON.
- attitude-controller-plannerUse this skill when implementing the inner control loop for a quadrotor — attitude (roll/pitch/yaw) PID control and attitude planning (converting desired acceleration to desired Euler angles). Covers gain layout, integral reset pattern, and the attitude planner inverse kinematics.
- azure-bgpAnalyze and resolve BGP oscillation and BGP route leaks in Azure Virtual WAN–style hub-and-spoke topologies (and similar cloud-managed BGP environments). Detect preference cycles, identify valley-free violations, and propose allowed policy-level mitigations while rejecting prohibited fixes.
- box-least-squaresBox Least Squares (BLS) periodogram for detecting transiting exoplanets and eclipsing binaries. Use when searching for periodic box-shaped dips in light curves. Alternative to Transit Least Squares, available in astropy.timeseries. Based on Kovács et al. (2002).
- browser-testingVERIFY your changes work. Measure CLS, detect theme flicker, test visual stability, check performance. Use BEFORE and AFTER making changes to confirm fixes. Includes ready-to-run scripts: measure-cls.ts, detect-flicker.ts
- cache-policy-comparisonCompare and implement eviction policies (LRU, LFU, FIFO, S3FIFO, ARC) for bounded-capacity caches. Use when choosing or implementing an eviction policy for a buffer pool, page cache, CDN edge, or LLM KV cache, or when writing a replay simulator that supports multiple policies. Clarifies recency vs frequency semantics, queue topology, saturating counters, ghost buffers, and the second-chance rule that distinguishes modern FIFO-family policies from classic LRU.
- casadi-ipopt-nlpNonlinear optimization with CasADi and IPOPT solver. Use when building and solving NLP problems: defining symbolic variables, adding nonlinear constraints, setting solver options, handling multiple initializations, and extracting solutions. Covers power systems optimization patterns including per-unit scaling and complex number formulations.