5-step workflowpersistence database crud state refresh guided-flow Debugging

Add Database Persistence

Your app forgets everything on refresh: move state into a real database with working CRUD.

Run this as a guided flow on Flows — verify gates and recovery prompts included →

Flows@flows12d ago

0 runs0 forks0

Chain

Inputs

Step 1

flow-add-database-persistence-1-inventory-unpersisted-state

Step 2

flow-add-database-persistence-2-design-models-and-endpoints

Step 3

flow-add-database-persistence-3-wire-writes-to-the-backend

Step 4

flow-add-database-persistence-4-wire-reads-with-proper-states

Step 5

flow-add-database-persistence-5-persistence-qa-pass

Final output

Workflow inputs

No inputs required — hit Run to stream each step in order.

Each step streams from its model and feeds the next. BYOK — you pay your provider directly. Add a key in Settings if a step needs one.

Step 1 · Find everything the app forgets - the full list, not samples.

flow-add-database-persistence-1-inventory-unpersisted-state

Claude Sonnet 4.6→ {{step_1}}

Awaiting upstream steps…

Step 2 · Give each PERSIST item a schema and API before wiring.

flow-add-database-persistence-2-design-models-and-endpoints

Claude Sonnet 4.6→ {{step_2}}

Awaiting upstream steps…

Step 3 · Every create/edit/delete must hit the database, not just state.

flow-add-database-persistence-3-wire-writes-to-the-backend

Claude Sonnet 4.6→ {{step_3}}

Awaiting upstream steps…

Step 4 · The UI must load truth from the backend with honest states.

flow-add-database-persistence-4-wire-reads-with-proper-states

Claude Sonnet 4.6→ {{step_4}}

Awaiting upstream steps…

Step 5 · Prove the app remembers everything, everywhere.

flow-add-database-persistence-5-persistence-qa-pass

Claude Sonnet 4.6→ {{step_5}}

Awaiting upstream steps…

About this workflow

Your app forgets everything on refresh: move state into a real database with working CRUD.

What happens when you run it

1
Find everything the app forgets - the full list, not samples.
Runs flow-add-database-persistence-1-inventory-unpersisted-state on Claude Sonnet 4.6
2
Give each PERSIST item a schema and API before wiring.
Runs flow-add-database-persistence-2-design-models-and-endpoints on Claude Sonnet 4.6
3
Every create/edit/delete must hit the database, not just state.
Runs flow-add-database-persistence-3-wire-writes-to-the-backend on Claude Sonnet 4.6
4
The UI must load truth from the backend with honest states.
Runs flow-add-database-persistence-4-wire-reads-with-proper-states on Claude Sonnet 4.6
5
Prove the app remembers everything, everywhere.
Runs flow-add-database-persistence-5-persistence-qa-pass on Claude Sonnet 4.6

Best for

•Recurring tasks you currently copy-paste between tools.
•When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
•Fork and adapt if your inputs differ materially from the author's use case.

Models used

Claude Sonnet 4.6