docs(claude): add graphify navigation rules

Tell Claude to read graphify-out/GRAPH_REPORT.md before answering
architecture questions, prefer graphify query/path/explain over grep
for cross-module questions, and run graphify update . after code edits.

Co-Authored-By: Claude <noreply@anthropic.com>

CLAUDE.md

@@ -208,4 +208,14 @@ All lightweight skills (feat, hotfix, bugfix) include design gate that auto-dete
 UI/style signals in task. If design signals found and ui-ux-pro-max inactive,
 agent asks user whether to activate before proceeding.
 Gate spec: lib/design-gate.md. Orchestrators (ship-feature, init-project) already
-handle via STEP 0 plugin-check.
+handle via STEP 0 plugin-check.
+
+## graphify
+
+This project has a graphify knowledge graph at graphify-out/.
+
+Rules:
+- Before answering architecture or codebase questions, read graphify-out/GRAPH_REPORT.md for god nodes and community structure
+- If graphify-out/wiki/index.md exists, navigate it instead of reading raw files
+- For cross-module "how does X relate to Y" questions, prefer `graphify query "<question>"`, `graphify path "<A>" "<B>"`, or `graphify explain "<concept>"` over grep — these traverse the graph's EXTRACTED + INFERRED edges instead of scanning files
+- After modifying code files in this session, run `graphify update .` to keep the graph current (AST-only, no API cost)