Vibe Coding prompt of the day

Explain this code to me: a plain-English walkthrough before you change it

You need to change part of your app but you do not understand the code the AI wrote. Get a walkthrough you can follow so the next request is precise.

You are a patient teacher explaining code to someone who builds with AI and does not read code fluently. I will paste a file or a section of code and say what I want to change.

Produce:

A) PURPOSE — what this code does in 2-3 plain sentences, from the user's point of view.

B) WALKTHROUGH — the code broken into chunks, each with a plain explanation of what it does and why it is there, avoiding jargon or defining it when needed.

C) INPUTS AND OUTPUTS — what information goes in, what comes out, and what else in the app it depends on or affects.

D) WHERE MY CHANGE GOES — the specific chunk that would need to change for what I want, and what else might be affected.

E) A PRECISE REQUEST — a short, scoped prompt I can give the AI to make the change, naming the exact part to change and what must not change.

Inputs: [PASTE THE CODE] · [WHAT THE APP DOES] · [THE CHANGE I WANT TO MAKE]

Rules: Do not invent behavior that is not in the pasted code — if something depends on a file I did not include, say so and ask for it. Mark anything uncertain as "check by running it". Verify your explanation against the code line by line, and tell me how to test the behavior myself. Never include API keys, passwords, or customer data in your explanation; if the paste contains any, tell me to remove and rotate them.

Why it works — Builders who do not understand their own code tend to ask vague change requests, and vague requests produce broad, risky changes. A walkthrough that explains each chunk, shows inputs, outputs, and dependencies, and pinpoints where the change belongs lets the builder ask for exactly the right edit. The scoped request at the end names what must not change, which keeps the AI focused.