Diagram
AI relationship diagram from a prompt
A Sketvio diagram is a left-to-right map of people, the app they use, and the data behind it. You write the cast. The layout engine places the boxes so arrows do not pile on top of each other.
Written from the Sketvio compilers at Rajosa Tech. Reviewed 20 September 2026.
When to use Diagram
Use Diagram when the question is “who is involved, and what do they touch?” A pitch, a domain model, or a first cut of a product. You want named entities and a few labeled relationships — not a click path and not a four-layer system map.
Skip Diagram if you need Yes/No branches (that is Flowchart), equal service boxes in Clients → Data bands (that is Architecture), or a screen people can pretend to click (Web UI or Mobile UI).
How generate actually works
You open a board, pick Diagram, and describe the cast in a sentence or two. The model is not asked for coordinates. It returns groups, node ids, and a few edges. A layout pass assigns rows so connected nodes line up, then draws bands and elbows.
If you name Auth as its own group, the compiler folds it into App. That is not the model “being helpful.” It is a rule we added after a four-column draft made every arrow cross a label.
Rajosa Tech built this after pixel JSON from the model produced floating boxes. The useful part of the model is naming. Placement is ours.
What lands on the board
Three columns, not a free cloud
The compiler always builds People, App, and Data. A fourth “Auth” swimlane is folded into App on purpose. Clerk, login, or a session box sits as an amber node inside the app column so the diagram stays readable on a laptop.
Eight to fourteen labeled nodes
Each node is a short name you can still edit. People and data use slate. App services use indigo. Only a highlight — usually auth — uses amber. That palette is the same one you will see if you generate twice.
A few labeled edges, the rest silent
At most four arrows carry a verb such as “uses” or “writes.” The rest stay unlabeled so the page does not become a paragraph of captions. Elbows route when a connection must change both X and Y.
HabitFlow, as a relationship map
Paste this on a board after you pick Diagram.
Diagram HabitFlow. People: Maya (member) and a coach. App: mobile client, streak service, and Clerk auth. Data: Postgres habits and an insights store. Show who uses what.
- People column: Maya, Coach
- App column: Mobile app, Streak service, Clerk (amber)
- Data column: Habits DB, Insights
- A short labeled edge from Maya to Mobile app
After the draft
- Rename a box if the model guessed a role.
- Drag a node if two names feel too close.
- Add a hand-drawn note for the one relationship the draft skipped.
- Share the board URL. You do not export a locked PNG as the source of truth.
Mistakes that waste a generate
- Do not ask Diagram for Yes/No. You will get people and data, not diamonds.
- Do not list twenty microservices. The draft will drop most of them. Draw the rest.
- Do not fight the three columns by renaming a group to “Auth.” The compiler folds it back into App.
Related tools
Questions about Diagram
Why isn’t Auth its own column?
Four columns crowd the canvas and push arrows through labels. Auth is a node inside App. If you need a vendor lane, use Architecture — that type already has a Data band for Postgres and an AI provider.
Can I ask for twenty entities?
The spec caps the draft at 8–14 nodes so the board stays a diagram, not a wall of chips. Add the rest by hand after generate. Extra boxes you draw do not cost another credit.
Does generate spend a credit?
A credit is spent when you create a new board, not when you ask AI on a board you already opened. You start with 3 boards.
Open a board and try Diagram.
Three starter boards. No card. The draft is editable the moment it lands.
Start free