Next step · What to do next

Add a database (so the site can save things)

What you may see

I need to save orders, messages, bookings or users

Why this step

Anything that must be remembered (orders, messages, users) needs a database with clear tables and access rules from day one.

Before you start

List the kinds of things to save and who may see or change each (visitors, customers, staff, only me).

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Add a database (so the site can save things)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Anything that must be remembered (orders, messages, users) needs a database with clear tables and access rules from day one.

DO THESE STEPS, IN THIS ORDER
1. Propose a small set of tables (names, columns, types, relations) for my list, in plain words first, and wait for my approval.
2. Write the setup as migration files with rollback files; keep money as whole units, times as UTC, and ids that are not guessable.
3. Turn on row level security on EVERY table and write the narrowest policies from my access list; test as visitor, customer and staff.
4. Connect the website with only the public key in the browser and server-only keys on the server, and show me where each key is kept.
5. Create test data and a script that resets it; never use real customers for tests.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Each kind of user can do exactly what the list allows, and an anonymous request to private tables returns nothing.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not run anything on a live database yourself.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Propose a small set of tables (names, columns, types, relations) for my list, in plain words first, and wait for my approval.
Write the setup as migration files with rollback files; keep money as whole units, times as UTC, and ids that are not guessable.
Turn on row level security on EVERY table and write the narrowest policies from my access list; test as visitor, customer and staff.
Connect the website with only the public key in the browser and server-only keys on the server, and show me where each key is kept.
Create test data and a script that resets it; never use real customers for tests.

Do not do this

Do not leave any table without access rules.
Do not run anything on a live database yourself.

Try another entry