Flows workflow logoFlows
Settings/Billing Page
0/6 steps0%

Step 1 of 6

Define settings sections

Inventory every setting and its backing field before building.

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

Prompt Capsule
Define the settings spec. List the sections - Profile (name, email), Security (password change), Preferences (2-3 real toggles/selects used by the app), Plan/Billing (current plan display, upgrade CTA), Danger Zone (delete account) - and for each control: the backing database field, validation rules, and the endpoint that persists it. Cut any control with no real backing field.
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 control-by-control spec mapped to fields and endpoints.

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