repo-atlas

# Repo Atlas Build an in-repo persistent context system so engineers and LLM agents can understand any codebase quickly with minimal searching. ## Hard Constraints - Do NOT change product/runtime behavior - No paid/hosted tooling — everything lives in the repo - Zero or minimal dependencies (Python 3 standard library only) - All generated content must reflect real repo specifics, not generic filler ## Workflow ### Phase 1: Reconnaissance Before writing anything, understand the repo: 1. Read the top-level directory structure 2. Identify the repo type: - **App** (web, mobile, desktop) — has screens/views, state managers, routes - **Backend/API** — has controllers, routes, middleware, models - **Library** — has public exports, module structure, build config - **Monorepo** — multiple packages/services - **CLI tool** — has command handlers, argument parsing - **Infrastructure** — has deployment configs, IaC files 3. Identify the primary language(s) and framework(s) 4. Find entrypoints, build configs, CI files 5. Read 5-10 key files to understand architecture patterns ### Phase 2: Run the Generator Script Copy `scripts/generate_atlas.py` (bundled with this skill) to the repo at `scripts/atlas/generate_atlas.py`. Then customize and run it: 1. Copy the script to the target repo 2. Review and adjust the configuration section at the top: - `IGNORE_NAMES` — add repo-specific directory names to ignore (exact segment match) - `TREE_ANNOTATIONS` — add shor...