Flowstate
how flowstate works
From one question
to a whole canvas.
Nine small stories about how work happens on Flowstate — asking, branching, building, and sharing. Follow one trip to Japan from a single question all the way to a canvas your whole crew can use.
scroll — story 01 is waiting ↓
for the power users
Built for the power users.
pick a way to work · watch Flowstate do the whole thing
step 01 · ask
Drop a question. Anywhere.
No thread to find, no chat to scroll back through. Click an empty spot on the canvas, ask, and the answer lands right next to your question — as a real card you can pick up and move.
question · you
Plan a two-week trip to Japan
step 02 · follow up
Keep asking. It stays wired.
Follow-ups connect to the answer they came from, so the whole line of thought sits together on the canvas — visible at a glance, not buried three screens up a chat.
question · you
Plan a two-week trip to Japan
follow-up · you
What’s the best week in April?
the whole thread, still on the canvas
step 03 · branch
One thought becomes three branches.
When an answer opens new directions, pull them out. Each branch is its own small thread with its own context — sitting side by side, not stacked in one endless scroll.
main thread
Plan a two-week trip to Japan
branch · budget
What should the daily budget be?
branch · itinerary
Tokyo, Kyoto — where else?
step 04 · add sources
Bring your documents in.
Drag PDFs, docs, and sheets straight onto the canvas. They land as cards — sources the AI can actually read, sitting right next to the questions you’ll point at them.
step 05 · ask your sources
Then ask the documents.
Point a question at your files and get an answer with receipts — every claim wired back to the exact cell or page it came from. No “trust me,” just citations.
question → 2 sources
Cheapest week to fly in April?
Fly out Tue Apr 8 — ¥62,400 return, and Kyoto hotels drop 22% that week.
budget.xlsx · B14
kyoto-guide.pdf · p.3
step 06 · make artifacts
Turn answers into artifacts.
A table, a timeline, a calendar — any answer can become a real object on the canvas. Not a paragraph pretending to be a plan, but the actual thing, live and editable.
| City | Nights | ¥ |
|---|---|---|
| Tokyo | 5 | 90k |
| Kyoto | 4 | 70k |
| Osaka | 3 | 52k |
step 07 · update in place
Change your mind. They update.
Ask for one change and the artifact updates in place — same card, same spot, new numbers. Nothing gets regenerated from scratch, and nothing you built goes stale.
question · you
Add three more days in Osaka.
| City | Nights | ¥ |
|---|---|---|
| Tokyo | 5 | 90k |
| Kyoto | 4 | 70k |
| Osaka | 6 | 104k |
| Total | 264k |
step 08 · share it
Share it. All of it.
One link and the whole canvas is theirs too — live cursors, movable cards, every question still wired to its answer. Not a screenshot. Not an export. The real thing.
| Tokyo | 5 | 90k |
| Kyoto | 4 | 70k |
| Osaka | 6 | 104k |
adding flights rn ✈️
step 09 · the showcase
Ask for an interface.
Get an interface.
describe the tool you wish existed — flowstate builds it as a working component, right on the canvas
→ “make us a bill splitter” try me — it works
Bill$84.00
People
4
Each pays$24.15
→ “let the team vote on this”
Kyoto52%
Lisbon31%
Mex. City17%
23 votes · updating live
→ “track my runs this month”
this monthstreak · 12 days 🔥
→ “count down to the flight”
for the vibe coders
Vibe code faster
with Flowstate.
drop in a repo or a skill — flowstate reads it and tells you what you’re actually working with
overview
Paste any GitHub repo and Flowstate reads it for you — what it is, how it’s built, and where to start.
Swiss Design
by zeke
See what any skill actually does — what it changes, what it needs, and whether to trust it — before you run it.