Compare commits
7 Commits
34b4706d00
..
master
| Author | SHA1 | Date | |
|---|---|---|---|
| b93d5ca135 | |||
| beb52eba4c | |||
| df1b5bed9b | |||
| 1958c3f01a | |||
| 6dfa36c1cb | |||
| 2d571cfd52 | |||
| 1c1fe6f651 |
@@ -28,3 +28,6 @@ yarn-error.log
|
||||
/frontend/.env
|
||||
|
||||
|
||||
|
||||
# graphify 知識圖譜輸出(可由 graphify 重建,graph.json 每次整份重寫)
|
||||
/graphify-out
|
||||
|
||||
@@ -213,3 +213,13 @@
|
||||
- 發現問題直接說,不要繞彎
|
||||
- 有不確定的地方,明確標注「我不確定,需要你確認」
|
||||
- 不要重複確認已經決定的技術選擇
|
||||
|
||||
## 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 "<question>"` 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 "<A>" "<B>"` for relationships and `graphify explain "<concept>"` 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).
|
||||
|
||||
Reference in New Issue
Block a user