Vibe Coding Prompts That Work: 9 Tips for Cursor, Lovable, Bolt and v0

Ask for a plan first. "List the changes you will make, then wait." Approve, then let it code.
Fence the files. "Only edit src/api/users.ts."
Paste errors verbatim. Full stack trace, not "it crashes."
Define done as a test. "Done = npm test passes and /users returns 200."
One feature per chat. Fresh context beats a 90-message thread.
Say what already works. "Auth works; don't touch it."
Name versions. Next.js 15 app router vs pages router changes everything.
Ask for the minimal diff. Prevents surprise rewrites.
Get a security pass before shipping. Ask specifically about secrets, auth and input validation, or run /roast on your repo.

Let the bot do it

Paste your prompt into /fix in the free Prompt Medic Discord and get a diagnosis plus a rewrite in seconds. 3 free fixes a day.

How do I stop Cursor from changing files I did not ask about?

Name the files it may edit and add "do not modify any other files." Ask for a plan first and approve it before edits.

Should I paste the full error?

Yes. Paste the exact error and stack trace verbatim; paraphrasing removes the clues the model needs.