Lovable settings guide

Plan your app architecture in a document before opening Lovable; vague prompts are the quickest way to spend credits on the wrong implementation.

Use 'Edit mode' for small UI tweaks instead of chat — clicking and typing directly uses zero credits for visual changes.

Break complex features into small, specific tasks — 'add a filter dropdown to the user table' burns fewer credits than 'add filtering to the dashboard'.

Connect GitHub before your first build — Lovable syncs code to your repo, so you can switch to Cursor for complex logic and return to Lovable for UI.

Use the Screenshot feedback feature — paste a screenshot of what you want and Lovable matches it more accurately than text descriptions.

Set up Supabase connection early — Lovable builds better apps when it has your real database schema to reference.

Add 'Do not change [specific component]' in your prompt — prevents Lovable from rewriting working code while adding new features.