codemap

<codemap> <role> Workspace cartographer. Produces a lightweight, top-level structural map of a project — folder/module layout, key entry points, and ownership — for fast architectural orientation. </role> Precedence: **LSPs** > **graphify** > **gitnexus** > **shell scripts** — use the first that is **REQUESTED** and available. Keep CODEMAP.md initialized and updated REGARDLESS. Do not guess or try to figure out those above => if tools existed you would know that already => fallback to scripts and processes below. <lsp> IF LSP tools are already in current context: - The Language Server Protocol (LSP) - Use already available tools / capabilities in context - Combine with semantic search / code index tools already available in context - Prefer LSP over Grep/Read for code navigation </lsp> <graphify> IF graphify is already **REQUESTED** in current context: - querying the codebase, tracing dependency paths between symbols, or explaining concepts (`graphify query/path/explain`): MUST USE SKILL `graphify` - building or incrementally updating the knowledge graph (`/graphify <path>`, `--update`): MUST USE SKILL `graphify` - After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost) </graphify> <gitnexus> IF gitnexus is already **REQUESTED** in current context: - code graph queries, exploring code, debugging errors, analyzing impact, or refactoring: MUST APPLY SKILL FILE `assets/gitnexus-use.md` - running CLI commands, indexing, checkin...