Build
Build a system from your architecture
A diagram is only half the value; the other half is letting an agent build from it. Type your nodes, export the structured context, and put the agent to work on exactly the right slice.
1
Model and type your nodes
Map domains → entities → functions. Tag each entity's type (service, actor, datastore, job) and status (live / build / plan) so the agent knows what already exists.
2
Draw the dependencies
Directed dependencies tell the agent the data flow and the blast radius of any change — essential context for safe generation.
3
Hand the file to the agent
A plain
↓ Save file is already the blueprint. Or publish the .forai.md extract via Share ▾ → ⇡ Share, or have a connected agent pull it over MCP.
4
Scope the build
Ask the agent to implement only the slice you want — typically the "build" and "plan" items, leaving "live" ones untouched.
Try asking your agent
▸ The MCP examples assume the contextgraph server is connected — see Setting up your MCP. The paste-a-link examples need no setup.
With the MCP server connected
claude "Read my Payments diagram over MCP and implement every entity marked 'build'; leave 'live' ones alone"claude "Stub the 'plan' components in my Orders diagram with TODOs and wire them to their dependencies"Or paste a public link — no MCP needed
claude "From https://ctxgraphai.com/v/ab12cd34.md, generate the API contract for the Payments service from its dependencies"