Next step · What to do next

Set up a safe test copy of the site (staging / preview)

What you may see

I want to try changes without risking the live site

Why this step

A separate copy with its own test data and keys lets you and your AI tool break things where it costs nothing.

Before you start

Does your host make a preview for each branch?

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
Set up a safe test copy of the site (staging / preview)

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
A separate copy with its own test data and keys lets you and your AI tool break things where it costs nothing.

DO THESE STEPS, IN THIS ORDER
1. Set up a preview for every branch with its own environment variables: test database, test payment keys, test email recipient.
2. Hide previews from search engines and protect them from the public if they hold private test data.
3. Write the routine: branch, change, preview, test, merge, live.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A change shows on its preview address only, uses test data, and reaches the live site only after merge.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not point previews at the live database.
- 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

Set up a preview for every branch with its own environment variables: test database, test payment keys, test email recipient.
Hide previews from search engines and protect them from the public if they hold private test data.
Write the routine: branch, change, preview, test, merge, live.

Do not do this

Do not send real emails from previews.
Do not point previews at the live database.

Fix it Works in the preview link but not on production (or the other way)

Try another entry