From eb020d88a71cf5b9fcf92d55f31a743bc4fb23f5 Mon Sep 17 00:00:00 2001 From: bastien Date: Wed, 15 Apr 2026 20:18:40 +0200 Subject: [PATCH] docs(claude): rewrite graphify context navigation guidelines 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 --- CLAUDE.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index d036e07..c4ac55e 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -50,11 +50,10 @@ Apply unless repo-specific instructions override. 3. Track → mark done as you go. 4. Summarize → high-level summary at each major step. --## Context Navigation --When you need to understand the codebase, docs, or any files in this project: --1. ALWAYS query the knowledge graph first: `/graphify query "your question"` --2. Only read raw files if I explicitly say "read the file" or "look at the raw file" --3. Use `graphify-out/wiki/index.md` as your navigation entrypoint for browsing structure +## Context Navigation (graphify) +- Use `/graphify query` ONLY for large-scope tasks: multi-file features, complex bug investigations, architectural changes, major refactors. +- For small tasks (hotfix, typo, single-file change, quick lookup): read files directly — do NOT invoke graphify. +- When graphify is used, `graphify-out/wiki/index.md` is the navigation entrypoint. ---