Flowchart
AI flowchart from a prompt
A Sketvio flowchart is a path a person walks: start, a few actions, one decision, and an end. Yes continues down the spine. No steps left, then rejoins or stops. The model writes the labels. Code owns the geometry.
Written from the Sketvio compilers at Rajosa Tech. Reviewed 20 September 2026.
When to use Flowchart
Use Flowchart when the question is “what happens next?” Onboarding, a support triage, marking a habit, approving a request. You care about order and a fork — not who owns a database table.
Skip Flowchart if you need three product columns (Diagram), four system layers (Architecture), or a screen chrome (Web UI / Mobile UI). Those types will not give you diamonds.
How generate actually works
Pick Flowchart and write the happy path plus one fork. The model returns nodes with kind start, action, decision, or end. The compiler stacks Yes downward and hangs No to the left so the main path stays a line.
We cap the draft at one or two ends and one decision. A second generate on the same board is the right way to add an exception path, not a longer first prompt.
Selecting an arrow used to crash older drafts when width went negative. New connectors start at [0, 0] and carry no start/end bindings. If an old board still errors, redraw that one line.
What lands on the board
One vertical Yes-spine
Start is a teal ellipse. Actions are blue rounded rectangles. The decision is an amber diamond whose label ends with a question mark. End is teal again. That is the whole vocabulary — six to ten nodes, not a novel.
No lives on the left
The No chain sits to the left of the spine so the happy path stays a straight line you can read in one glance. Decision edges are the only labeled arrows: Yes or No. Other edges stay quiet.
Arrows you can select
Connectors are normalized so a click does not throw a “linear element is not normalized” error. Width and height come from the point box. Bindings are left off so Excalidraw does not rewrite the path after generate.
Mark today’s habit
Paste this on a board after you pick Flowchart.
Flowchart: Maya opens HabitFlow, picks Drink water, the app asks if she already logged today. Yes → confirm streak. No → log the cup, then show the new count.
- Start: Open HabitFlow
- Action: Choose Drink water
- Decision: Already logged today?
- Yes spine: Confirm streak → End
- No chain (left): Log the cup → Show new count → End
After the draft
- Change a decision label if the real fork is different.
- Add a second end by hand if No should abandon the flow.
- Keep one decision in the AI draft. Extra diamonds are yours to draw.
- The board autosaves. Come back and the path is still there.
Mistakes that waste a generate
- Do not paste a 20-step SOP. The compiler keeps 6–10 nodes. Split the SOP into two generates.
- Do not ask for three decisions in one prompt. The No chain is built for one fork.
- Do not use Flowchart to draw a database. There is no Data band here.
Related tools
Questions about Flowchart
Why only one decision in the draft?
Two forks turn the compiler into a maze and the No chain stops being a line. Generate the main decision, then draw the exception. The draft is a spine, not the whole SOP.
Can start and end look like regular boxes?
No. Start and end stay ellipses so the eye finds the entrance and the exit. Actions stay rectangles. If you need a box that is “just a state,” use Diagram.
What if I select an arrow and the board errors?
That was a real bug when a connector had a negative width. The current generator normalizes points to start at [0, 0]. If an old board still errors, regenerate on a new board or redraw that one arrow.
Open a board and try Flowchart.
Three starter boards. No card. The draft is editable the moment it lands.
Start free