understand-explain

1# /understand-explain
2 
3Provide a thorough, in-depth explanation of a specific code component.
4 
5## Graph Structure Reference
6 
7The knowledge graph JSON has this structure:
8- `project` — {name, description, languages, frameworks, analyzedAt, gitCommitHash}
9- `nodes[]` — each has {id, type, name, filePath?, summary, tags[], complexity, languageNotes?}
10  - Code node types: file, function, class, module, concept
11  - Non-code node types: config, document, service, table, endpoint, pipeline, schema, resource
12  - Domain/knowledge node types: domain, flow, step, article, entity, topic, claim, source
13  - IDs use the node type as prefix, e.g. `file:path`, `function:path:name`, `config:path`, `article:path`
14- `edges[]` — each has {source, target, type, direction, weight}
15  - Key types: imports, contains, calls, depends_on, configures, documents, deploys, triggers, contains_flow, flow_step, related, cites
16- `layers[]` — each has {id, name, description, nodeIds[]}
17- `tour[]` — each has {order, title, description, nodeIds[]}
18 
19## How to Read Efficiently
20 
211. Use Grep to search within the JSON for relevant entries BEFORE reading the full file
222. Only read sections you need — don't dump the entire graph into context
233. Node names and summaries are the most useful fields for understanding
244. Edges tell you how components connect — follow imports and calls for dependency chains
25 
26## Instructions
27…