Free tool · No signup
Lovable Prompt Generator
Answer a few questions about your app. You get a first prompt that builds your screens, plus follow-up prompts that add data, login and each feature one step at a time.
Your app idea
Your prompts
Paste prompt 1 into a new Lovable project. When it finishes and looks right, send the next one. One step at a time keeps the app from breaking.
1 · First build
Build the first version of GigBook, a web app that helps independent musicians track their gigs, payments and setlists in one place. It is for working musicians who play 4 to 10 shows a month. In this first step, build the screens and navigation only. Use realistic sample data so every screen looks finished. Do not connect a database or login yet. Screens: - Dashboard - Gig list - Gig detail - Setlists - Settings Core features to show on these screens: 1. Add a gig with venue, date, pay and status 2. Mark a gig as paid or unpaid 3. Build a setlist and attach it to a gig 4. See total earnings this month on the dashboard Design: - Bold dark mode: near-black background, one bright accent color, strong headings, high contrast text. - Mobile first. Every screen must work on a 375px wide phone with no sideways scrolling, then scale up to desktop. - Keep buttons, cards, and form fields consistent across every screen. - Include empty states with a short helpful message, not blank areas. Rules: - Build only what is listed above. Do not add extra features or pages. - No fake testimonials, fake user counts, or placeholder lorem ipsum. - When you finish, list what you built and anything you were unsure about.
2 · Connect real data
Replace the sample data in GigBook with a real database (Supabase). Create only the tables these screens need, with clear column names. Show a loading state while data loads and a friendly error message if it fails. Keep the design exactly as it is. Tell me which tables you created and why.
3 · Add sign up and login
Add email sign up, login, logout, and password reset. Logged-out visitors only see a simple landing page and the login screen. Each user must only see and change their own data. Turn on row level security for every table and write the policies for it. Do not change any screen that is not part of login.
4 · Finish: Add a gig with venue, date, pay and status
Make this feature work fully from start to finish: Add a gig with venue, date, pay and status. Handle the empty state, the loading state, and errors with clear messages. Validate every form field and show what is wrong next to the field. Only change the files this feature needs. Then explain how to test it in 3 steps.
5 · Finish: Mark a gig as paid or unpaid
Make this feature work fully from start to finish: Mark a gig as paid or unpaid. Handle the empty state, the loading state, and errors with clear messages. Validate every form field and show what is wrong next to the field. Only change the files this feature needs. Then explain how to test it in 3 steps.
6 · Finish: Build a setlist and attach it to a gig
Make this feature work fully from start to finish: Build a setlist and attach it to a gig. Handle the empty state, the loading state, and errors with clear messages. Validate every form field and show what is wrong next to the field. Only change the files this feature needs. Then explain how to test it in 3 steps.
7 · Finish: See total earnings this month on the dashboard
Make this feature work fully from start to finish: See total earnings this month on the dashboard. Handle the empty state, the loading state, and errors with clear messages. Validate every form field and show what is wrong next to the field. Only change the files this feature needs. Then explain how to test it in 3 steps.
8 · Phone and polish pass
Review every screen at 375px wide. Fix anything that overflows, text that is too small, and buttons smaller than 44px tall. Make sure every image has alt text and every form field has a label. List each fix you made.
9 · Security check before launch
Do a security review before I share this app. Check that no secret keys are in the frontend code, every table has row level security, and every form is validated on the server too. List any problem you find and fix it, one at a time.
How to use the generator
- Describe your app in the form, or edit the example to match your idea.
- Copy prompt 1 into a new Lovable project and let it build.
- Check the result. When it looks right, send the next prompt. Repeat until the last one.
Questions about Lovable prompts
What is a Lovable prompt generator?
It turns your app idea into the text you paste into Lovable. This one gives you a first prompt that builds your screens, then a set of follow-up prompts that add real data, login, each feature, and a final phone and security check, in that order.
How do I write a good first prompt for Lovable?
Say what the app does, who it is for, which screens it has, and the few features that matter most. Describe the look in plain words. Tell it what not to build. Specific prompts get closer on the first try and waste fewer credits.
Should I build my whole app in one prompt?
No. Big all-in-one prompts are where AI builders break things. Build the screens first with sample data, then connect the database, then add login, then finish one feature at a time. Check the app after every step before you send the next prompt.
Does this generator use AI or cost credits?
No. It builds the prompts from a template in your browser, so it is free and instant and nothing you type is sent anywhere. Sending the prompts to Lovable uses your Lovable credits as normal.
Do these prompts work in Bolt, v0, Replit, or Cursor?
Yes. The staged plan works in any AI app builder. Lovable connects to Supabase for data and login, so if your builder uses a different database, change that one word in the data prompt.
Is this an official Lovable tool?
No. It is a free tool made by Digital Alchemy, an independent AI education studio. Lovable is a trademark of its owner.