Debug a vibe-coded app without breaking it further
by PaperChaseWebb
12 prompts that make your AI coding tool find the real cause of a bug, change one thing at a time and prove the fix before it moves on.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
debug-a-vibe-coded-app-without-breaking-it.md · 7 KB · direct download, no signup
What you end up with
Bugs get fixed with small, reviewed diffs instead of a three-file rewrite that creates two new problems.
What you get
- 12 prompts in one .md file, each with [placeholders] marked
- A one-page debugging loop: reproduce, isolate, change one thing, verify, commit
- A stop and revert prompt for when the agent starts going in circles
- Notes on switching your tool to ask or plan mode so it reads before it writes
Who it is for
Anyone building with an AI coding tool who has watched it rewrite three files to fix a typo, or fix one bug and quietly cause another. No prior debugging experience needed.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free. Uses the AI coding tool you already pay for.
Time to result: First fix in under 30 minutes
Sample prompts, free to use
Do not edit any files yet. Bug: [describe what happens] when I [steps to trigger it]. Expected: [what should happen instead]. 1. List the 3 most likely causes, ranked, with the file and function you suspect for each. 2. For the top cause, give me one command, log line or browser check that would confirm or rule it out. 3. Wait for me to run it and paste the result before you propose any change.
Forcing a ranked guess plus a test stops the agent from editing on its first hunch.
Make the smallest change that fixes the cause we confirmed. Rules: touch at most [2] files. Do not rename, reformat or reorganize anything unrelated. Do not add new dependencies. After the change: show the diff, tell me exactly how to verify the fix, and name one thing that could have broken because of it. Stop and ask me before running a database migration, deleting files or changing environment variables.
The file limit and the 'what could break' question catch most collateral damage.
Free preview of the file
# Debug a vibe-coded app without breaking it further PaperChase prompt pack, version 1.0. 12 prompts for Cursor, Claude Code, Codex, Windsurf, Bolt, Lovable, Replit or any AI coding tool. ## How to use this pack 1. Commit before every debugging session: `git add -A && git commit -m "before debugging"`. No git? Download a copy of the project folder first. 2. Put your tool in ask, plan or chat mode for prompts 1 to 4. These prompts read code; they should not change it. 3. Replace everything in [square brackets]. Leave the rest as written. The rules are the point. 4. One bug per session. When the bug is fixed, commit, then start a new chat for the next one. Long chats drift. ## The debugging loop Reproduce. Isolate. Change one thing. Verify. Commit. If a step fails twice, go to prompt 8 (Stop and revert). ## Contents 1. Reproduce before you touch anything 2. Read the error like a senior developer 3. Explain this file before you edit it 4. Find code that is never called 5. One change, then prove it 6. Check for packages that do not exist 7. Bisect the bug with git 8. Stop and revert 9. Fix an error that only happens in the production build 10. Untangle a loop of failed fixes 11. Write the test that would have caught it 12. Leave a note for future you
Worth knowing
- Prompts reduce flailing. They do not replace reading the diff before you accept it.
- Some tools ignore 'do not edit' in fully automatic modes. Switch to ask, plan or chat mode for the first prompt.
- Commit before each session. The revert prompt assumes git is there to fall back on.
Questions
Why is this pack free?
It is the starter pack for the PaperChase newsletter. Enter your email and the download link arrives with the first issue. Unsubscribe in one click.
Does it work with Bolt, Lovable or Replit?
Yes. Paste the prompts into the chat panel. Where a browser builder has no git, the pack shows how to download a copy before each session instead.
Details
Version 1.0 · Updated Oct 15, 2026 · Markdown version of this page
License: Personal and commercial use. Do not resell the pack itself. Download terms
Related
Turn a spreadsheet you run by hand into a small web app
A staged plan and prompts for turning the spreadsheet your team edits by hand into a web app with logins, forms and an import of your existing rows.
GitHub release notes bot: draft notes from merged pull requests
A GitHub Action that collects merged pull requests when you push a version tag, groups them by label and opens a draft release with notes written for users.
App Launch Check: a launch review for apps built with AI
Send a repo URL and get a scored report on deploy, domain, payments, legal pages, security basics and AI code mistakes, with a fix list in priority order.