From 6dfa36c1cb5d6686bd849c3dc454332047b7913e Mon Sep 17 00:00:00 2001 From: Hank Date: Thu, 29 Oct 2026 17:41:37 +0800 Subject: [PATCH] =?UTF-8?q?chore(graphify):=20CLAUDE.md=20=E6=96=B0?= =?UTF-8?q?=E5=A2=9E=20graphify=20=E4=BD=BF=E7=94=A8=E8=A6=8F=E5=89=87?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 由 graphify 安裝流程寫入，要求查詢程式碼問題時先用 graphify query， 改完程式碼後執行 graphify update。 Co-Authored-By: Claude Sonnet 5.5 --- CLAUDE.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 3b465f8..a971406 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -213,3 +213,14 @@ - 發現問題直接說，不要繞彎 - 有不確定的地方，明確標注「我不確定，需要你確認」 - 不要重複確認已經決定的技術選擇 + +## graphify + +This project has a knowledge graph at graphify-out/ with god nodes, community structure, and cross-file relationships. + +Rules: +- When graphify-out/graph.json exists, run `graphify query ""` before your first grep, search or source-file read for a codebase question, and put this rule in every subagent prompt that explores code. Read raw files only for lines the graph or an earlier read already located. Use `graphify path "" ""` for relationships and `graphify explain ""` for focused concepts. These return a scoped subgraph, usually much smaller than GRAPH_REPORT.md or raw grep output. +- If graphify-out/wiki/index.md exists, use it for broad navigation instead of raw source browsing. +- Read graphify-out/GRAPH_REPORT.md only for broad architecture review or when query/path/explain do not surface enough context. +- After modifying code, run `graphify update .` to keep the graph current (AST-only, no API cost). +- A committed graphify-out/graph.json is rewritten whole on every build, so a large diff to it in a pull request is expected. Do not flag it as churn or suggest skipping the graph rebuild or its hooks.