← ClaudeAtlas

map-codebaselisted

(Re)generate the Orchestra codebase map — fan out parallel audit agents across every subsystem and (over)write the reference docs in docs/codebase-map/. Use when the architecture docs are stale, after a big refactor, or to bootstrap the map from scratch. This GENERATES the docs; CLAUDE.md's routing table is what points future work at them.
lcsmas/orchestra · ★ 0 · Code & Development · score 72
Install: claude install-skill lcsmas/orchestra
# Regenerate the codebase map This skill rebuilds the per-subsystem reference docs under **`docs/codebase-map/`**. It audits the **current** source, so run it whenever the map has drifted from reality (after a refactor, a new subsystem, or moved files). It overwrites the docs in place — the prior versions are in git if you need to diff. The docs are consumed via the routing table in the project `CLAUDE.md`, which points future work at the right doc. This skill is the *producer* of those docs. ## Procedure 1. **Re-scan the source layout** so the audit reflects today's tree, not a remembered one: ```bash find src -name '*.ts' -o -name '*.tsx' | sort wc -l src/main/*.ts src/renderer/*.tsx src/renderer/components/*.tsx ``` Read `src/shared/types.ts` first — it's the documented domain backbone and the fastest orientation. Check whether the subsystem split below still holds (new big files may deserve their own doc; merged ones may collapse). 2. **Fan out one audit agent per subsystem, in parallel** (launch them in a single message — independent work). Use the `Explore` agent type (read-only; it locates and reads code). Each prompt should demand: what the subsystem does, how it's built, key functions/exports **with `file:line`**, data shapes, integration points, and non-obvious design decisions / past bug-fixes. The current subsystem → file mapping: | Doc | Cover these files | |---|---| | `workspaces.md` | `src/main/workspaces.