Provide exact errors and screenshots for faster debugging
Attaches screenshots, pastes exact error messages from console logs, and points to when it broke.
When to use it
Your app is broken on the published site but works fine in the preview.
Why it is worth it
Concrete evidence helps Lovable pinpoint the issue instead of guessing.
The prompt
My published e-commerce app shows a blank checkout page but works fine in the preview. Here is the exact error from the browser console: TypeError: cartItems is undefined at index-DWQbrtrQQj.js:1847. The checkout worked yesterday. Review what changed in the last day and explain which change broke it before fixing.
Replace e-commerce app with your published app and its exact console error.
What you get
Lovable can pinpoint exactly what changed and broke the feature without guessing.
From docs.lovable.dev/prompting/prompting-debugging