How to use Graphify with a Large Project? — Multiple Graph Folders

[locus0002]

I am working on a large project where the graphify output was split into type-based folders, with the main graph generated in an AllFolders folder:

graphify-out/
├── Actors/
├── Ai/
├── CommonUI/
├── Components/
├── DataAssets/
├── ...
└── AllFolders/   ← main graph

I modified CLAUDE.md and settings.json as follows:

CLAUDE.md

## graphify

This project has a graphify knowledge graph at graphify-out/.

Graph structure:
- `graphify-out/AllFolders/` → main graph covering all classes (435 files)
- `graphify-out/<TypeFolder>/` → type-scoped graphs (Actors, Ai, CommonUI, Components, DataAssets, etc.)

Rules:
- Before answering architecture or codebase questions, read `graphify-out/AllFolders/GRAPH_REPORT.md` for god nodes and community structure
- For questions scoped to a specific class type, prefer the relevant `graphify-out/<TypeFolder>/GRAPH_REPORT.md` to reduce token cost
- If `graphify-out/AllFolders/wiki/index.md` exists, navigate it instead of reading raw files
- After modifying code files in this session, run `graphify update graphify-out/AllFolders` to keep the main graph current.

settings.json

"command": "[ -f graphify-out/AllFolders/graph.json ] && echo '{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"additionalContext\":\"graphify: Knowledge graph exists. Read graphify-out/AllFolders/GRAPH_REPORT.md for god nodes and community structure. For scoped questions, prefer type-scoped graphs under graphify-out/<TypeFolder>/GRAPH_REPORT.md to reduce token usage.\"}}' || true"

---

Questions

1. How do you generate the wiki after all graphs have already been created? Does it need to be generated per folder, or only for AllFolders?

2. Wiki cost and maintenance — since the wiki appears to be generated by Claude (consuming tokens), is it worth maintaining for a large project? How and when should it be updated, and does it need to be regenerated after every graphify update?

3. Graph update scope — in a large project like this, should only the AllFolders graph be updated after code changes, or should the type-scoped folder graphs also be kept in sync?

Thanks in advance!

[FolatheDuckofDuckingburg]

Hi @locus0002, great setup for handling a large codebase. Here are direct solutions for your multi-folder Graphify architecture:

1. Wiki Generation Scope

Command: Run graphify wiki graphify-out/AllFolders to target the main directory directly.

Scope: Generate this only for AllFolders. Creating individual wikis for type-scoped folders causes massive token redundancy and splits up your navigation index.

2. Wiki Cost & Maintenance

Is it worth it? Yes, but only for onboarding or high-level architecture reviews. For daily context-building, reading the GRAPH_REPORT.md files is much more token-efficient.

Update Frequency: Do not regenerate the wiki after every graphify update. Only rebuild it during major release milestones or when a new core module is introduced.

3. Graph Update Scope

Local Workflow: Developers should only run graphify update graphify-out/AllFolders after local code changes. Updating every single type-scoped folder manually during a dev session is too slow and inefficient.

Automation Solution: Offload the type-scoped graph updates (Actors/, Ai/, etc.) to a GitHub Action / CI pipeline triggered nightly or on merges to the main branch. This keeps the scoped reports fresh without slowing down individual workflows.

Your hook injection in settings.json is a smart touch for managing the token economy. Hope this helps!