From c26d8adcdd20b75467763959d2de84cefad6bb03 Mon Sep 17 00:00:00 2001 From: bastien Date: Wed, 6 May 2026 17:08:52 +0200 Subject: [PATCH] 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 --- CLAUDE.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 19a5dcf..f8060cb 100644 --- a/CLAUDE.md +++ b/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. \ No newline at end of file +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 ""`, `graphify path "" ""`, or `graphify explain ""` 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)