← ClaudeAtlas

atlaslisted

Generate or update a semantic domain map (ATLAS.md) for the project. Maps where to look, entry points, module purposes, key symbols, and integration points. Complements codemap's structural index with the domain knowledge layer.
nicodiansk/turbocharge · ★ 2 · AI & Automation · score 75
Install: claude install-skill nicodiansk/turbocharge
# Atlas — Project Domain Map Generate or update the semantic domain map for this project. **Announce:** "Using atlas to map this project's domain." ## The Iron Law ``` NO ATLAS WITHOUT READING THE CODEBASE FIRST ``` Do not generate from assumptions or memory. Read the actual code, configs, and docs. ## Step 1: Detect Mode - If ATLAS.md does NOT exist in the project root → **Generate mode** - If ATLAS.md exists → **Update mode** ## Step 2: Read the Codebase Regardless of mode: 1. Read project structure (directory listing, key config files) 2. Read CLAUDE.md if it exists — understand what's already documented (don't duplicate it) 3. Read entry points (main files, CLI entry, API routers, job schedulers) 4. Read domain models (data classes, schemas, database models) 5. Scan integration configs (env files, connection strings, external service clients) ### Step 2b: Read Codemap Index (if available) If `.codemap/.codemap.json` exists in the project root: 1. Read `.codemap/.codemap.json` — it contains a manifest with `directories` (list of indexed paths) and `stats` (total files, total symbols). 2. For each directory in the manifest, read `.codemap/<dir>/.codemap.json` — each contains `files` with symbol entries (name, type, lines, language). 3. Use this data to pre-populate: - **Module Map** — each directory with its file count and key files - **Key Symbols** — pick the 20-30 most important symbols (classes, exported functions) with their `file:line-range` 4. You s