# A CLAUDE.md snippet that makes Claude Code mandatory-use graphify (query/path/explain/wiki) for all cross-module exploration before falling back to grep,   find, or ripgrep.

> Source: <https://gist.github.com/oyilmaztekin/e4bfb7d4a6065c0168b6703b90dee215>
> Published: 2026-05-07 08:56:15+00:00

**Orient with graphify**(`graphify-out/GRAPH_REPORT.md`

, then`graphify query`

/`graphify path`

/`graphify explain`

). For browsing by topic, start at`graphify-out/wiki/index.md`

— each community has its own article linking related nodes.- ....

For any "where is X / what uses Y / how does Z connect" question, **you must use graphify before any grep, find, ripgrep, or Glob/Grep tool call.** Graphify is ~71x cheaper in tokens and surfaces relationships (node → prompt → output model → state field) that grep cannot.

**Required workflow:**

- Start at
`graphify-out/wiki/index.md`

to find the right community, or run`graphify query "<concept>"`

. - Follow relations with
`graphify path <a> <b>`

and`graphify explain <node>`

. - Think in
**communities and relations**, not file paths.

**Grep/find is allowed only as a fallback for:**

- Exact literal hunts (error strings, magic constants, specific config keys).
- Files graphify hasn't indexed (state it explicitly when this happens).
- Verifying a specific line/symbol after graphify has pointed you to the file.

**Subagents must follow the same rule** — when delegating exploration (Explore, general-purpose, etc.), instruct them to use graphify first and treat grep as fallback. Do not let the default Explore agent reflexively grep this repo.

If graphify output looks stale, surface that to the user instead of silently switching to grep.