Graph Structure Reference

Project Overview: name, languages, frameworks, description (from project metadata)
Architecture Layers: each layer&#x27;s name, description, and key files (from layers + file nodes)
Key Concepts: important patterns and design decisions (from node summaries and tags)
Guided Tour: step-by-step walkthrough (from the tour section)
File Map: what each key file does (from file-level nodes, organized by layer)
Complexity Hotspots: areas to approach carefully (from complexity values)

The knowledge graph JSON has this structure:

project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}
nodes[] — each has {id, type, name, filePath, summary, tags[], complexity, languageNotes?}
- Node types: file, function, class, module, concept
- IDs: file:path, function:path:name, class:path:name
edges[] — each has {source, target, type, direction, weight}
- Key types: imports, contains, calls, depends_on
layers[] — each has {id, name, description, nodeIds[]}
tour[] — each has {order, title, description, nodeIds[]}

How to Read Efficiently

Use Grep to search within the JSON for relevant entries BEFORE reading the full file
Only read sections you need — don't dump the entire graph into context

Generate a comprehensive onboarding guide from the project's knowledge graph.

The knowledge graph JSON has this structure:

project — {name, description, languages, frameworks, analyzedAt, gitCommitHash}
nodes[] — each has {id, type, name, filePath, summary, tags[], complexity, languageNotes?}
- Node types: file, function, class, module, concept
- IDs: file:path, function:path:name, class:path:name
edges[] — each has {source, target, type, direction, weight}
- Key types: imports, contains, calls, depends_on
layers[] — each has {id, name, description, nodeIds[]}
tour[] — each has {order, title, description, nodeIds[]}

Use Grep to search within the JSON for relevant entries BEFORE reading the full file
Only read sections you need — don't dump the entire graph into context