Prompt library

1. 1

   Choose a feature you want to add or a design style you want to apply from the list on this page.

   This page provides pre-written prompts for many common tasks, saving you time and ensuring the prompt is well-formed for Lovable.

2. 2

   Copy the prompt text for your chosen feature or style.

   The prompts are designed to be directly usable in your Lovable project chat.

3. 3

   Replace any placeholder names, numbers, or examples in the copied prompt with your own specific details (e.g., prices, file limits, column names).

   The prompts are generic templates; customizing them makes the feature fit your app perfectly.

4. 4

   Paste the customized prompt into your Lovable project chat and send it.

   This tells Lovable what to build or change in your app.

5. 5

   Review the result Lovable generates, then proceed with other features or refinements one prompt at a time.

   Working one step at a time helps you manage complexity and ensure each part of your app is built correctly.

6. 6

   If a prompt is large or complex, consider adding 'Ask me any questions you need before building' to the end, or use 'plan mode'.

   This helps ensure Lovable understands your intent before starting a big task, preventing rework.

7. 7

   Save important decisions like your design direction or product context to your project's 'knowledge' section.

   This allows Lovable to automatically build on these decisions in future prompts, maintaining consistency.

Add user accounts to my app. Include signup, login, and forgot password pages that match the app's existing style. Require login before accessing the dashboard. Add a "Sign in with Google" button alongside email and password. Show clear error and success states on every form.

Built-in backend (Cloud)

This is the invisible, ready-to-use server and database that comes with your Lovable project. It handles things like storing information, user accounts, and running app logic without you needing to set up a separate server.

Kanban board

A visual tool for managing tasks, often with columns like 'To Do,' 'In Progress,' and 'Done,' where tasks move from left to right as they are completed.

Glassmorphic

A design style that makes elements look like frosted glass, often with blurred backgrounds and layered, translucent surfaces.

Brutalist

A design style characterized by raw, unfinished textures, strong lines, bold typography, and a focus on functionality over aesthetics, often using stark colors like black and white.

Gamified

Adding game-like elements (like points, badges, or progress bars) to non-game activities to encourage engagement and motivation.

Editorial polish

A design style that mimics the sophisticated look of magazines or newspapers, focusing on clear typography, structured layouts, and rich content presentation.

Magic link

A secure link sent to a user's email that allows them to log in without needing a password, by simply clicking the link.

Role-based access control (RBAC)

A system that assigns different levels of access and permissions to users based on their job role (e.g., 'admin' can do everything, 'viewer' can only see things).

Realtime

When information updates instantly across all connected users or devices, without anyone needing to refresh their screen.

Component set

A collection of pre-designed and reusable building blocks (like buttons, navigation bars, or cards) that maintain a consistent look and feel throughout an app.

Webhook

An automated message sent from one app to another when a specific event happens, allowing apps to communicate and react to each other in real-time.

Edge functions

Small pieces of code that run very close to where your users are located, making your app faster and more responsive, especially for backend logic.

Semantic search

A type of search that understands the meaning and context of your query, rather than just matching keywords, to provide more relevant results.

Feature flag

A software development technique that allows you to turn features on or off in your app without deploying new code, often used for testing or rolling out features gradually.

Rate limiting

A control that restricts how many times a user or system can perform an action within a certain time period, often used to prevent abuse or overload.

• Using placeholders like names, numbers, or examples from the prompt directly without customizing them for your own project.
• Trying to run multiple complex prompts at once instead of one at a time, which can lead to unexpected results or confusion.
• Forgetting to save important project context or design decisions to your project's knowledge, which can lead to inconsistencies in future builds.
• Attempting to use built-in payments or app emails without being on the required plan (Pro or higher for payments, any paid plan for app emails).
• Expecting Lovable to automatically connect to third-party services without explicitly naming the service in your prompt or setting up the connector.