App builders · guidance updated 22 Nov 2026
Lovable prompt guide
Plan mode asks clarifying questions interactively before proposing plans. Use buzzwords (minimal, premium, playful, calm, bold) with colors and typography to convey aesthetic. Instructions exist at three levels: Workspace (10k, shared), Project (10k, per-project), Personal (private).
How to prompt Lovable
- Plan before prompting: define product purpose, target user, key action, and why users will take it.
- Map user journey visually (3–5 steps from landing to key action) before writing prompts.
- Build one component at a time, not full pages (hero, card, feature section sequentially).
- Use real copy and realistic sample data—never placeholder text or lorem ipsum.
- Speak atomic UI language: buttons, cards, modals, badges, toggles instead of vague descriptions.
- Apply visual direction with buzzwords (minimal, premium, playful, calm, bold, cinematic, expressive) plus concrete colors, typography, and spacing.
- List all states to handle (loading, empty, error, mobile vs desktop) and transitions between sections.
- Use Plan mode for complex changes; let it ask clarifying questions, review the plan, then approve before Build.
- End every prompt with a question asking Lovable to clarify gaps before building.
- Point at specific elements with the preview toolbar when requesting targeted changes.
- Save standing rules, style guides, and coding standards in Instructions (Workspace, Project, or Personal).
- Specify what must stay untouched and what can change in edit requests.
The shape of a good prompt
[Product & user: purpose, target audience, key action, why they'll use it] [User journey: 3–5 logical steps from landing to action] [This prompt's scope: one section or component] [Visual style: buzzwords, mood, palette, typography, spacing] [Structure: sections in order with transitions] [Interactions and states: hover, loading, empty, error, mobile vs desktop] [Data and backend needs: tables, auth, roles, storage] [Boundaries: what must not change] [Clarifying questions for Lovable]
Avoid
- Building a whole product in one prompt; build one component per prompt.
- Generic descriptors (modern, clean) without concrete colors, typography, or buzzwords.
- Placeholder text, lorem ipsum, or vague copy instead of realistic words.
- Edit requests that don't specify what must remain unchanged.
- Repeating standing rules in every prompt; store them in Instructions instead.
- Skipping Plan mode for complex or risky changes that need review.
- Forgetting to ask Lovable clarifying questions, especially in Plan mode.
- Vague UI descriptions like 'a section' instead of atomic terms (card, modal, badge).
Example
Request an app for my dog walking business
Build a booking web app for a solo dog-walking business. Users: dog owners booking walks on their phones, and me (the walker) managing my schedule. Core journey: owner signs up -> adds dog profile (name, breed, notes) -> picks a 30 or 60 min slot from my availability -> gets confirmation; I see today's walks in order. Start with just the public landing page and the booking flow (no admin yet). Visual style: friendly and playful but tidy: warm off-white background, forest-green primary, rounded cards, a rounded sans-serif, generous spacing. Use real copy: headline 'Happy dogs, tired legs', 3 benefit cards, 2 pricing cards (30 min £12, 60 min £20). States: loading skeletons, an empty state when no slots are free, inline form errors. Responsive: mobile-first; booking steps stack on mobile, two columns on desktop. Data: user accounts with email login, tables for dogs, bookings, availability. Ask me any questions you need to fully understand what I want before building.