Node Map

Maintains a persistent, append-only knowledge graph of a codebase — one root index plus one node file per project/folder — so future sessions read a compact map instead of re-reading source code. Use this skill whenever an architectural decision is actually implemented (code committed or files changed after a design decision), when the user runs git commit in a mapped workspace, when the user asks to "map", "index", "graph", or "node" a codebase, when starting work in a workspace that already has a nodemap.json, or alongside readback/ground-truth/mandate/commenter as part of an agent-structure workflow. Trigger proactively after any multi-file change lands — don't wait to…