Next step · What to do next

Write simple handover notes so anyone can run the project

What you may see

In a month I will forget how it works

Why this step

Short, true notes save hours when you return after weeks, change tools, or hand the project to someone else.

Before you start

Who will read this: you, a developer, or a new team member?

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
Write simple handover notes so anyone can run the project

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
Short, true notes save hours when you return after weeks, change tools, or hand the project to someone else.

DO THESE STEPS, IN THIS ORDER
1. Read the project and write a README of under two pages: what it is, how to run it, the folders, the commands (dev, build, test), the list of environment variable NAMES with what each is for, and how to deploy.
2. Add a "how to" list for the five most common jobs (change text, add a product, add a language, rotate a key, restore a backup) and a "when something breaks" page with the first three checks.
3. Check by following the notes yourself in a clean folder and fix every step that fails.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- Someone who has never seen the project can run it and deploy a small change using only the notes.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not write secrets in the notes.
- 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

Read the project and write a README of under two pages: what it is, how to run it, the folders, the commands (dev, build, test), the list of environment variable NAMES with what each is for, and how to deploy.
Add a "how to" list for the five most common jobs (change text, add a product, add a language, rotate a key, restore a backup) and a "when something breaks" page with the first three checks.
Check by following the notes yourself in a clean folder and fix every step that fails.

Do not do this

Do not describe what you hope is true; test every step.
Do not write secrets in the notes.

Try another entry