Cursor rule

1---
2description: graphify knowledge graph context
3alwaysApply: true
4---
5 
6This project may have a **local** graphify knowledge graph at `graphify-out/` (gitignored — not in the repo). Each developer generates it with `pnpm graphify:update`.
7 
8**MANDATORY: Before using Read, Grep, Glob, or Bash to explore the codebase, you MUST run graphify first:**
9- `graphify query "<question>"` — scoped subgraph for any codebase or architecture question
10- `graphify path "<A>" "<B>"` — dependency path between two symbols
11- `graphify explain "<concept>"` — all nodes related to a concept
12 
13This applies to YOU and to every subagent you spawn. Include this rule explicitly in every subagent prompt that involves code exploration. Do not skip graphify because files are "already known" or because you are executing a plan — the graph surfaces cross-file dependencies and INFERRED edges that grep and Read cannot find.
14 
15Only use Read/Grep/Glob directly when:
161. graphify has already oriented you and you need to modify or debug specific lines
172. `graphify-out/graph.json` does not exist yet — run `pnpm graphify:update` locally first (output is gitignored)
18 
19- If `graphify-out/wiki/index.md` exists, navigate it instead of reading raw files
20- Read `graphify-out/GRAPH_REPORT.md` only for broad architecture review when query/path/explain do not surface enough context
21- After modifying code files locally, run `graphify update .` to refresh your local graph (AST-only, no API cost). Do not commit `graphify-out/`.
22