Step 1 of 6
Define settings sections
Inventory every setting and its backing field before building.
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.
Expected after this step
A control-by-control spec mapped to fields and endpoints.
Should not happen
- ✕Save buttons that show a toast but write nothing
- ✕Password change that does not verify the current password
- ✕Toggles resetting on reload
- ✕Delete account that only redirects home
Verify before continuing
Do not move on until every check is true. The complete button stays locked until then.
Do not continue if…
- !Save buttons that show a toast but write nothing
- !Password change that does not verify the current password
- !Toggles resetting on reload
- !Delete account that only redirects home
If the AI messes this up
Use this when the AI fakes progress or breaks the feature. It forces a real fix.
Some controls have no backing field. Remove them or define the field and where the app uses it - decorative settings are forbidden.