Add roadmap.md and make the graphify workflow explicit in CLAUDE.md
Commit-by-commit plan (phases A-D) from TODO.md to a merge on main, and rules to query the graph for context and refresh it after every code change. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
6441733160
commit
79f7ebe53e
2 files changed
+83
-1
No files matched your search
@@ -283,5 +283,7 @@ 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).
|
||||
- **Whenever you need context** (where something lives, what depends on it, how two parts relate, what a change could affect), get it from the graph first — `graphify query`, `path` or `explain` — not by browsing or grepping files blindly. This applies to subagents too.
|
||||
- **Whenever you modify code, update the graph before the commit**: run `graphify update .` (AST-only, no API cost) so the graph always matches the committed code. Every commit of [roadmap.md](roadmap.md) ends with it.
|
||||
- A change to docs only (no code) is not picked up by `graphify update .`; refresh the graph with `/graphify --update` when docs were restructured, not for every wording tweak.
|
||||
- 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.
|
||||
Reference in new issue
Block a user