Visualizations & views
On this page
Visualizations & views
Every way VibeMap shows your project visually, in one place — what each view is for and where to find it. · Optional
VibeMap renders your project in several interactive views. Each answers a different question. Use this page to pick the right one.
| View | Where | Answers | Plan |
|---|---|---|---|
| Schema diagram | Schema page | "How do my tables relate?" — an interactive entity-relationship diagram | Starter |
| Graph view | Graph tab on the project Overview | "How do my spec entities connect, and where are the gaps?" — a zoomable node graph with spec-gap outlines | Any |
| In-app UI preview | Preview tab on the Pages page | "What might this screen look like?" — a live Sandpack render of a generated page | Starter |
| Blueprint Preview Map | Prepare for Dev page | "What does my whole build-ready blueprint look like?" — features, roles, pages and data as one wired diagram | Starter (narration Pro) |
| Financial model dashboards | Financial Analysis tab on the Business Case page | "Do the numbers work?" — KPI tiles, pro-forma tables, sensitivity grid, tornado chart | Any |
| Code Map | Codebase page | "How does my spec line up with my real codebase?" — a map of your synced repo | Any |
| Sprint / Kanban tracker | Sprint Planning page | "What order do we build in?" — a board of sequenced work | Pro |
The Plan column is the lowest plan that can open the view — "Any" includes Free. Two things people expect to be gated aren't: the Code Map is not a paid add-on (codebase sync runs on every plan), and the Blueprint Preview Map opens from Starter — it's only the LLM-narrated tour of it that needs Pro.
💡 Tip: The Graph view and the Schema diagram are the two you'll open most while planning — one shows how requirements connect, the other how data connects. The Blueprint Preview Map is the one to open right before handoff, when you want the whole picture in one frame.
Reading the graph gap outlines
The Graph view outlines entities that are missing something the spec expects — a feature with no stories, a story with no criteria, a page tied to no story. Those outlines are the same signals the readiness check uses, shown spatially. Chasing them to zero is a fast way to reach a build-ready spec.
⚡ Power-user hints
- Two graphs, two questions. The Graph tab on the project Overview draws your whole spec; the Graph tab on the Pages page draws page structure only. When you're hunting spec gaps, you want the Overview one.
- The read-only views cost nothing to open. The Graph view and the Blueprint Preview Map are derived from what you've already generated, with no LLM call behind them — so opening them never spends a generation.
- Move the financial levers instead of regenerating. The dashboard's sliders recompute the model in the browser and your positions are saved per project, so you can stress-test pricing without paying for a second run.
What's next
- Close the gaps the views reveal: Prepare for Dev.
- Let the agent point you at gaps automatically: Guided mode.