Next step · What to do next

Organise my keys and settings properly (environment variables)

What you may see

My keys are everywhere and I do not know which is which

Why this step

Mixed-up keys cause leaks and outages; one list with names, purposes and places makes both rare.

Before you start

Do you have keys in more than one place (code, chat, notes)?

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
Organise my keys and settings properly (environment variables)

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
Mixed-up keys cause leaks and outages; one list with names, purposes and places makes both rare.

DO THESE STEPS, IN THIS ORDER
1. Search the code for every environment variable it reads and list them (names only) with what each is for and whether it is public or secret.
2. Create a sample file with names and short comments (no values) that is committed, and keep the real file ignored by Git.
3. Check that secret variables are used only in server code, and public ones have the public prefix and contain nothing secret.
4. Help me set the same names for local, preview and production, with separate keys per environment (test keys outside production).
5. Tell me where to keep the real values (a password manager), and how to rotate any key if needed.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The sample file lists all names, nothing secret is in Git or in public code, and each environment has its own keys.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not print values.
- 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

Search the code for every environment variable it reads and list them (names only) with what each is for and whether it is public or secret.
Create a sample file with names and short comments (no values) that is committed, and keep the real file ignored by Git.
Check that secret variables are used only in server code, and public ones have the public prefix and contain nothing secret.
Help me set the same names for local, preview and production, with separate keys per environment (test keys outside production).
Tell me where to keep the real values (a password manager), and how to rotate any key if needed.

Do not do this

Do not reuse production keys in tests.
Do not print values.

Try another entry