bchanot/claude
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(claude): rewrite graphify context navigation guidelines

Browse Source 
Clarify when to use graphify (large-scope tasks only) vs reading
files directly (small tasks). Removes the "always query graph first"
rule that added unnecessary overhead for simple lookups.

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
bastien 2026-04-15 20:18:40 +02:00
parent 616c6e9198
commit 02e4f25f56
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
CLAUDE.md
View File

@ -50,11 +50,10 @@ Apply unless repo-specific instructions override.
3. Track → mark done as you go. 3. Track → mark done as you go.
4. Summarize → high-level summary at each major step. 4. Summarize → high-level summary at each major step.
-## Context Navigation ## Context Navigation (graphify)
-When you need to understand the codebase, docs, or any files in this project: - Use `/graphify query` ONLY for large-scope tasks: multi-file features, complex bug investigations, architectural changes, major refactors.
-1. ALWAYS query the knowledge graph first: `/graphify query "your question"` - For small tasks (hotfix, typo, single-file change, quick lookup): read files directly — do NOT invoke graphify.
-2. Only read raw files if I explicitly say "read the file" or "look at the raw file" - When graphify is used, `graphify-out/wiki/index.md` is the navigation entrypoint.
-3. Use `graphify-out/wiki/index.md` as your navigation entrypoint for browsing structure
--- ---