Every edit re-renders the preview instantly. Treat the preview as your compiler — if it looks right in the preview, it's almost certainly right in the code. This tight loop is why non-developers can move so fast in Lovable.
/Signals to watch
- 01Preview pane: The primary source of truth. If it renders, the build succeeded.
- 02Error banner: Red banners point at the exact file and line. Copy the message back into chat verbatim.
- 03Console tab: Runtime errors, network failures, and your own console.logs land here.
- 04Network tab: Use this to confirm API calls fired and returned the data you expect.
Debug faster
When something breaks, share the exact error text back with Lovable. Screenshots also work — you can drag them into chat.
/The 3-attempt rule
If you've prompted the same fix three times without progress, stop. Switch to Chat mode, describe what you've tried, and ask Lovable to propose a different approach. Loops usually mean the diagnosis is wrong, not the fix.