The hardest part of vibe coding isn't the tool. It's staring at an empty prompt box wondering what to type. This is the library I wish I'd had on day one — 30+ prompts I actually use, organized by what you're trying to build.
Copy them, paste them into Lovable, and swap the bracketed parts for your own. They're starting points, not magic spells.
How to use this library
- Pick a starter prompt for the kind of app you want.
- Ship the first version. Don't tweak the prompt for 20 minutes — send it and see what comes back.
- Layer in feature prompts one at a time. One feature per prompt, always.
- Use the fix and polish prompts when something breaks or feels off.
Starter prompts — SaaS apps
Generic SaaS dashboard
Build a SaaS dashboard for [your audience, e.g. freelance designers] to track [what they track, e.g. client projects]. Include a sidebar with Projects, Clients, Invoices, and Settings. The main view shows a table of projects with status, client name, and due date. Use a clean modern design with a soft neutral palette.
Subscription product with auth
Build a subscription-based [product type, e.g. habit tracker]. Users sign up with email, land on a dashboard, and can create, edit, and delete [items]. Add a pricing page with Free, Pro, and Team tiers. Use Lovable Cloud for auth and database.
AI-powered tool
Build an AI tool that takes [input, e.g. a job description] and returns [output, e.g. 5 tailored interview questions]. One main input field, a Generate button, and a results area. Use Lovable AI to call the model. Add a copy button on each result.
Starter prompts — internal tools
Admin CRUD app
Build an internal admin tool for managing [resource, e.g. team members]. List view with search and filters, detail view, create and edit forms, and delete with confirmation. Protect everything behind email login. Keep the UI dense and functional, not marketing-pretty.
Approval workflow
Build an internal tool where employees submit [request type, e.g. expense reports] and managers approve or reject them. Each request has a status (Pending, Approved, Rejected) and shows in a queue. Email notifications when status changes.
Data entry form with export
Build a simple internal form to capture [data, e.g. customer onboarding info]. Fields: [list 5–8 fields]. Save every submission to the database, show a table of all submissions, and add a button to export the table to CSV.
Starter prompts — landing pages
Product landing page
Build a one-page landing site for [product name], a [one-line description]. Sections: hero with headline, subheadline and CTA; 3-feature grid; testimonials; FAQ; final CTA. Use a [vibe, e.g. warm, friendly, slightly playful] tone. Modern typography, generous whitespace.
Waitlist page
Build a coming-soon waitlist page for [product]. Bold headline, short tagline, single email input with Join Waitlist button, and a small "X people on the list" counter. Save signups to Lovable Cloud. Dark background with one accent color.
Personal portfolio
Build a personal portfolio for a [role, e.g. freelance illustrator]. Sections: hero with name and tagline, About, selected work as a grid of project cards, and a contact form. Editorial typography, neutral palette, lots of room to breathe.
Feature prompts (add one at a time)
- Auth: "Add email/password login and protect the dashboard route. Unauthenticated users get redirected to /auth."
- Database: "Save [items] to a database. Each row has [fields]. Users can only see their own rows."
- File upload: "Let users upload an image on the [page]. Store it in Lovable Cloud storage and show a preview after upload."
- Search: "Add a search box above the [list] that filters by [field] as the user types."
- Filters: "Add filter chips above the table for [field 1], [field 2], and [field 3]. Multiple can be active at once."
- Pagination: "Paginate the [list] with 20 items per page and Previous/Next buttons at the bottom."
- Empty state: "When the [list] is empty, show a friendly empty state with an illustration, a one-line message, and a Create button."
- Email: "When a user [action, e.g. signs up], send them a welcome email with [content]."
- Stripe payments: "Add a Pro upgrade button on the pricing page that opens Stripe Checkout. After success, mark the user as Pro in the database."
- Dark mode: "Add a dark mode toggle in the header. Persist the preference per user."
Fix prompts (when things break)
- "The [thing] isn't working. When I click [button], nothing happens. Check the console logs and fix the root cause — don't just hide the symptom."
- "The page renders blank after I navigate to /[route]. Find out why and fix it."
- "This change broke [other feature]. Revert the part that broke it but keep [the thing I wanted]."
- "The form submits but nothing shows up in the database. Trace it end to end and tell me where it fails."
- "Looks fine on desktop but breaks on mobile at [width]. Fix the responsive layout for [section]."
Polish prompts (when it works but feels off)
- "Make the [section] feel more premium. Better typography, more breathing room, subtler shadows. Keep the same layout."
- "Add a subtle hover and focus state to every interactive element. Nothing flashy."
- "Replace the placeholder copy in [section] with real, specific copy for [audience and product]."
- "Improve the loading and empty states across the app. They should feel intentional, not like missing screens."
- "Audit the spacing and alignment of the [page]. Tighten anything inconsistent."
Three rules that make every prompt work better
- One thing per prompt. "Add auth and a dashboard and Stripe" is three prompts, not one.
- Be specific about the output. "Modern" means nothing. "Soft neutral palette, generous whitespace, serif headings" gives the model something to work with.
- Show, don't just tell. Paste a link to a site you like, or a screenshot, and say "this kind of feel".
For more on writing prompts that actually land, see 7 vibe coding mistakes beginners make and the prompting section of the FAQ.
