What problem does it solve? Codebases grow faster than anyone can explain them, and architecture diagrams rot the moment code moves. This Skill turns a repository into a durable, versioned isometric map under .greenline/map/ where prose is authored by reading the code and counts, coverage, and geometry are measured by scanners, so the map stays honest as the code changes. ## Core Features & Use Cases - Authored-plus-measured map state: map.md holds groups, node prose, edges, flows, and coverage globs; snapshot.json holds measured file counts, line totals, the snapshot commit, and per-node prose provenance. - Self-contained viewer: a prebuilt HTML shell renders the map as an isometric city with animated flows tracing real call paths, requiring no build tooling, framework mounting, or server. - Staleness-aware updates: on re-runs it folds git diff through the coverage globs, reports a staleness tier (fresh, current, drifting, stale), re-reads only dirty nodes, and reuses unchanged prose byte-identical. - Use Case: A new engineer joins a team and asks how the repo fits together; the agent reads the code, authors subsystem prose, measures coverage, and produces architecture.html they can open and explore by playing real flows like sign-in or the main create/read loop. ## Quick Start Ask the agent to build an architecture map of this repository so you can see how the codebase fits together.
