Add Database Persistence
0/5 steps0%

Step 1 of 5

Inventory unpersisted state

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

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule
Audit the app and produce a table of every piece of state that should persist but currently does not: the data (e.g. tasks, profile edits, settings), where it lives now (useState/localStorage/nowhere), what user action creates or changes it, and whether refresh loses it. Test by performing each action then refreshing. Mark each row KEEP-LOCAL (genuinely UI-only) or PERSIST.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A verified inventory of state with PERSIST/KEEP-LOCAL decisions.

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent