How do I write a good Lovable prompt?

Describe one concrete outcome, give real content and constraints, and say what NOT to touch. Plan first for anything non-trivial, then build in small steps.

How do I get Lovable to follow my design properly?

Give Lovable concrete references — a screenshot, a site to draw from, exact colours and fonts — and store them in Project knowledge so every prompt is checked against the same design rules.

How do I give Lovable a website to use as inspiration?

Paste the site's URL in your prompt and describe which parts to borrow — layout, spacing, tone — Lovable can't literally browse and clone it, so be specific about what you want copied.

How do I get Lovable to copy a design style without copying the website?

Ask for the underlying pattern — layout, spacing, type scale — in your own words and colours, not the site's actual assets, text or exact visual identity.

How do I upload images to Lovable?

Attach images directly in the chat message box — Lovable can use them as design references or as assets to place in your app (e.g. a logo or product photo).

How do I get Lovable to use my logo?

Attach your logo file in chat and tell Lovable exactly where to place it (header, favicon, footer) — it won't guess sizing or position from the file alone.

How do I make Lovable build one feature at a time?

Ask for one clearly-scoped feature per prompt and confirm it works in Preview before moving on — bundling several features into one message makes failures harder to isolate and revert.

How do I stop Lovable changing things I didn't ask it to change?

State explicitly what must stay unchanged in the same prompt, keep requests narrow, and check the diff/preview after each change so unintended edits are caught immediately.

How do I tell Lovable to only edit one section?

Name the exact page, component or element (or select it via the preview toolbar) and explicitly say the rest of the app should stay unchanged.

How do I get Lovable to plan a feature before building it?

Switch to Plan mode and describe the feature there — Lovable will ask questions and lay out a structured plan for you to approve before any code is written.

How do I get Lovable to review existing code before making changes?

Ask Lovable directly, ideally in Plan mode, to look at the relevant files or feature first and summarise how it currently works before proposing any changes.

How do I make Lovable ask me questions before building?

Use Plan mode and explicitly ask Lovable to raise questions or ambiguities before building — it's designed to clarify requirements first rather than guess.

How do I get better results from Lovable prompts?

Be specific and concrete, use real content, plan before building complex features, work in small steps, and review each result in Preview before prompting again.

Why does Lovable misunderstand my prompts?

Usually the prompt is ambiguous, references something that doesn't exist yet, or bundles too many changes at once — narrow it, add references, and split it up.

Should I use screenshots when prompting Lovable?

Yes, for layout and visual matching — a screenshot removes ambiguity that words leave open, especially for spacing, alignment and component styling.

How do I make Lovable match a screenshot?

Attach the screenshot, say precisely what to match (layout, spacing, colours, all of it), and iterate with follow-up prompts comparing Preview against the image side by side.

How do I undo a bad Lovable change?

Open Version history and revert to the version saved right before the bad change — every change Lovable makes is auto-saved as a version, so you can step back without losing later unrelated work.

How do I safely make large changes to a Lovable project?

Plan the change first, bookmark a known-good version before starting, break it into small ordered steps, and check Preview between each step so you can revert cleanly if one goes wrong.

How do I get Lovable to use a specific font?

Q: How do I give Lovable my brand colours?

Give exact hex codes in your prompt or Project knowledge, name which role each colour plays (primary, accent, background), and ask Lovable to apply them via the Tailwind/shadcn theme, not one-off styles.

Last checked 31 Aug 2026

Short answer

Name the exact font (e.g. from Google Fonts) and tell Lovable to load it and apply it across the theme, not just the current page.

Name the font and its source

Use "Inter" from Google Fonts as the body and heading font across the whole site. Load it properly (not just referenced by name) and apply it via the Tailwind theme.

If the font is a paid/licensed font rather than a free Google Fonts entry, say so and provide the font files or an existing embed method (e.g. Adobe Fonts kit) — Lovable can't source a licensed font on your behalf.

Specify weights and where each is used

Fonts often need multiple weights (400 regular, 600 semibold, 700 bold for headings). If you only ask for "Inter" without weights, you may get a default weight everywhere, including headings that look better bolder. Be explicit:

Headings: Inter, weight 700. Body text: Inter, weight 400. Buttons: Inter, weight 600.

Apply at theme level

As with colours, fonts should be set once in the Tailwind theme configuration so every component inherits them, rather than being set per-page. Ask: "set this as the default font in the theme" if you notice only part of the site updated.

What usually goes wrong

Font only changes on one page — ask for a theme-level, global change.
Fallback font shows briefly or permanently — if the font isn't loading correctly (e.g. a licensing/CDN issue), the browser falls back to a default sans-serif; ask Lovable to verify the font is actually loading, not just referenced in CSS.
Font looks different from the reference — screenshots of a font in use can look different depending on the exact weight and letter-spacing; give exact values if precision matters.
Using a font that doesn't support your language's characters — check the chosen font has the character set you need if the site isn't English-only.

For the full brand picture, pair this with /questions/how-do-i-give-lovable-my-brand-colours and store the font choice in Project knowledge alongside your colour palette.

Sources

Prompting best practices

Was this answer helpful?