Q: Coding agents will read Design Context everytime before build?
I like the idea of persistent graph database. I'm on your tier3 and thinking about to upgrade.
But I'm not sure how the agent will read the PRD, each page context, and some 'required or reused UI' such as navbar, sidebar, auth, when they create new page?
Sofiane_Krisspy
Nov 27, 2025A: Excellent question.
Connections are currently made at task planning time: using the relations in the graph, we inject all the required data.
Then a few things happen:
• AI agents like Claude Code can read other files to understand the structure, etc.
• For performance, we build a graph of files and functions via an AST (not yet visible in the UI).
• We introduced parameterizable references on all Reference or Template pages (briefly mentioned in the Vibe Coding tutorial around 2:42).
The krisspy.md file also lets you customize the agent’s instructions.
Another element that has been hidden in the online version is virtual nodes. We connect pages to documentation, with the goal of breaking the “black box” feeling.
These virtual blocks can, for example, represent the PRD. A change to the PRD can trigger an agent that updates the page as needed — this feature will be re-enabled a bit later.
Great concept. This is great product fixing AI problem. I m in :)