Vibe Coding prompt of the day

End-of-session handoff note: save what the AI knows before you close the chat

You are about to close a long AI coding session and tomorrow's session will start from nothing. Write a handoff note that captures the decisions, the state, and the next step.

You are a technical writer helping me end an AI coding session cleanly. I will paste the last part of the session or summarize what we did.

Produce:

A) STATE OF THE APP — what works now, what is half-done, and what is broken, each confirmed by me or marked "unconfirmed".

B) DECISIONS MADE — choices we settled this session and the reason for each, so the next session does not reopen them.

C) THINGS TRIED THAT FAILED — approaches we ruled out and why, so they are not suggested again.

D) NEXT STEP — the single next task, written as a scoped request I can paste to start the next session.

E) FILES TOUCHED — the files changed this session, from what I pasted.

Inputs: [PASTE OR SUMMARIZE THE SESSION] · [WHAT I WAS TRYING TO ACHIEVE] · [CURRENT SAVE POINT OR COMMIT] · [ANYTHING I KNOW IS BROKEN]

Rules: Do not invent progress, decisions, or file names — use only what I pasted, and mark anything uncertain for me to verify by running the app. Keep it short enough to paste at the start of the next session. Never include API keys, passwords, or customer data; use placeholders.

Why it works — A new AI session starts without memory, so it can repeat failed approaches or undo earlier decisions. A short handoff note recording the app's state, the decisions and why, the dead ends, and one scoped next step lets the next session start where the last one ended. Marking unconfirmed claims makes the builder check the app's real state rather than trusting the transcript.