MetroNow

Run the full TIGER defect audit pipeline for a MetroNow service zone — fetch from Overpass, classify defects, analyze history, generate reports.

Diff OSM geometry and attributes against TIGER/Line 2024 to identify import drift, new roads, and name-field artifacts in MetroNow zones.

Generate a MapRoulette challenge from scan results for defect classes with high false-positive rates. Creates GeoJSON tasks constrained to MetroNow zone polygons.

Deep revision history analysis for specific OSM ways — fetches full version history from OSM API v0.6, identifies import bot vs human edits, classifies review status with confidence scores.

Submit corrections to OSM API v0.6 with full community compliance — proper changeset tags, size limits, rate-limit awareness, and dry-run support.

Decompress MetroNow docs so future-you (and fresh AI sessions) can pick the project back up cold without re-deriving everything. Use when the user says docs are confusing, plain, dense, hard to follow, missing context, jargon-heavy, jump straight to conclusions, or are hard to come back to after time away; asks why something is the way it is; says they can't tell what a term means; asks for a walkthrough, explainer, primer, or context refresher; says a section assumes too much; or wants visual aids. Diagnoses missing-middle gaps (undefined jargon, unstated WHY, skipped bridge steps, prose where a picture is needed) and rewrites sections using a fixed template — definition first, then bridge steps, then a load-bearing diagram, then code citations. Outputs to docs/explainers/<topic>.md or in-place edits. No VitePress, no static-site generator — just markdown that GitHub renders.

Unified code review and audit standards for the MetroNow Atlas TIGER Audit Console (https://github.com/AICincy/MetroNow.git). Use this skill when auditing any code in the MetroNow project, doing a PR review, checking code quality, validating accessibility, reviewing Docker config, or when someone asks "review this code," "audit the frontend," "check my PR," "what's wrong with this file," or "does this meet our standards." The codebase is vanilla JavaScript (IIFE pattern, no framework), single-file HTML with inline CSS/JS, IBM Plex typography, Leaflet maps, and an Express.js backend on port 3000 that shells out to the Python `osm` CLI. Covers JS, HTML, CSS, and Dockerfile review with severity-classified findings.

Code review and quality standards for MetroNow Atlas Dockerfile configuration. Use this skill when auditing Dockerfiles, docker-compose files, container configs, or when someone asks "review my Dockerfile," "is this image secure," "optimize my Docker build," or "check my compose file." The runtime is a multi-stage build producing a python:3.12-slim image with Node.js 20 layered in; the Express.js server (web/server.js) listens on port 3000 and shells out to the Python `osm` CLI. Frontend is a single HTML file served by Express. Repo: https://github.com/AICincy/MetroNow.git

Code review and quality standards for MetroNow Atlas CSS. Use this skill when auditing stylesheets, checking design token compliance, validating responsive layout, auditing color contrast, or when someone asks "review my styles," "check the CSS," "is this accessible," or "does this use the right tokens." CSS lives in two places: an inline `<style>` block in `web/public/index.html` and an external `web/public/css/atlas-supplement.css`. Design system uses IBM Plex fonts, warm-neutral editorial palette, and CSS custom properties. Repo: https://github.com/AICincy/MetroNow.git

Code review and quality standards for MetroNow Atlas HTML. Use this skill when auditing HTML files, checking accessibility, validating semantic markup, or when someone asks "review this page," "check the markup," "is this accessible," or "does this meet WCAG." The shipping app is `web/public/index.html` (single file with inline `<style>` and external script tags). Several non-shipping HTML reports live in `docs/`. Repo: https://github.com/AICincy/MetroNow.git

Code review and quality standards for MetroNow Atlas JavaScript. Use this skill when auditing JS files, reviewing atlas.js or atlas-extras.js, checking code quality, evaluating state management, assessing error handling, or when someone asks "review this JavaScript," "audit the frontend," "check this code," or "what's wrong with this function." The codebase is vanilla JS with IIFE closures, Leaflet maps, and a global state object. No framework, no JSX. Repo: https://github.com/AICincy/MetroNow.git

Cross-reference OSM data against CAGIS quarterly road centerlines and ODOT TIMS Road Inventory for ground-truth validation of defect classifications.

Prepare all OSM community requirements before mechanical edits — wiki page, talk-us discussion, import account setup, changeset tag templates. This is mandatory and NOT optional.

Set up and query OSMCha monitoring for MetroNow zone changesets. Post-submission monitoring via REST API, pre-submission scoring via local osmcha Python package.