# Vibe Coding Bug Report Formatter

Converts a vague description of something broken in your AI-built app into a precise, structured prompt that gets AI app builders to fix the right thing on the first try.

## Prompt

You are an expert at writing precise bug-fix prompts for AI app builders like Lovable, Bolt, and Replit, which need very specific instructions to fix the right thing.

What's broken (in your own words, however vague): {{vague_bug_description}}
What page/feature this is on: {{page_or_feature}}
What you expected to happen: {{expected_behavior}}
What actually happens instead: {{actual_behavior}}

Do the following:
1. Rewrite the bug description into a precise, unambiguous statement an AI app builder can act on directly, removing vague language like 'it's not working' in favor of exact observed behavior.
2. Suggest 2-3 likely technical causes in plain language (e.g., a missing state update, a broken API call, a styling conflict) based on the symptom described, without assuming access to the actual code.
3. Write the final ready-to-paste prompt formatted the way AI app builders respond best to: state the exact problem, the exact expected behavior, the specific page/component affected, and an instruction to fix only this issue without changing unrelated functionality.
4. Add one line reminding the builder tool to preserve all existing working features while making this fix, since these tools sometimes make broader unintended changes.

## Best for

Non-technical and semi-technical builders using AI app builders (Lovable, Bolt, Replit, v0, Cursor) who struggle to describe bugs precisely enough to get a clean, targeted fix instead of unrelated changes.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Describe the bug in your own words, even vaguely, along with which page or feature it's on.
- State clearly what you expected versus what actually happened.
- Copy the final ready-to-paste prompt directly into your AI app builder's chat.
- If the fix doesn't work on the first try, paste the builder's response back in and ask for a revised version of the bug prompt.

## Customization tips

- If you can see any error message in the browser console, include it even if you don't understand it, since it significantly improves cause diagnosis.
- For bugs that only happen on certain devices or browsers, mention that specifically so the prompt includes it as a reproduction detail.
- If this is the second or third attempt to fix the same bug, mention what was tried before so the AI app builder doesn't repeat a failed approach.

## Example input

What's broken: The signup button doesn't seem to do anything sometimes. Page/feature: Sign Up page. Expected: Clicking Sign Up should create the account and redirect to the dashboard. Actual: Sometimes nothing happens when clicked, no error shown.

## Example output

A precise rewrite stating the sign-up button intermittently fails to trigger account creation with no visible error, likely causes suggested including an unhandled async error being silently swallowed or a form validation blocking submission without displaying feedback, a final ready-to-paste prompt specifying the exact page, expected versus actual behavior, and an instruction to fix only the sign-up flow, plus a closing reminder to preserve all other existing working pages and features.