Lovable — App & Website Builder

Platform
Websites
Category
AI
Style
Dark
Type
Camera Plain
Updated
Sep 2026

Build with AI

An original design in the taste of Lovable — structure, tokens, font swaps and an imagery plan (2,249 words).

Paste into any AI tool. Every screenshot in the prompt is a public link the tool can open, and you can attach the screenshot link as a visual reference. It tells the agent to build something original: new copy, your brand, licensed or generated images.

Open in

Long prompts are copied to your clipboard first — paste them in when the tool opens.

Connect via MCP

claude mcp add uidiscovery \
  --env UIDISCOVERY_URL=https://uidiscovery.com \
  -- node /path/to/uidiscovery/mcp/server.mjs

Then ask your agent (it calls get_design_brief({ slug: "lovable" }) and get_image_plan({ slug: "lovable" })):

Use the uidiscovery MCP server: call get_design_brief({ slug: "lovable" }) and get_image_plan({ slug: "lovable" }), look at the preview images, then build an original site for [my brand] that follows the brief. Cite https://uidiscovery.com/sites/lovable.

Download kit ↓Brief as Markdown ↗API docs
Preview the prompt
# Build brief — an original marketing website in the taste of Lovable

> Reference: https://lovable.dev · UIDiscovery: https://uidiscovery.com/sites/lovable · captured 2026-09-21 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/lovable/full.webp) · [scroll video](https://uidiscovery.com/media/captures/lovable/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Lovable — same structure, rhythm and polish, entirely new identity and content.

## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Lovable: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Lovable's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.

## 3. The taste, in short
- Lovable (lovable.dev): AI marketing website, dark.
- 7 sections: Hero → How it works → Features → Logo cloud → Content → Stats → Footer.
- Spacing: about a screen per idea (median section ≈900px).
- Hero headline: 3 words — short and punchy; keep yours under ~9.
- Type: one family (Camera Plain). Imagery: mostly typography with little or no imagery, some abstract 3D / gradient art.

## 4. Page structure (top to bottom)

### 1. Hero — state what the product is and for whom in one glance, and offer the primary action.
- Layout: headline-led stack: eyebrow → H1 → supporting line → actions, with a visual beside or below. About one full screen (900px at 1440), own light band #fcfbf8; 3 image/graphics; 3 buttons (tabs, toggles or per-card actions).
- Slots: Eyebrow / announcement pill (optional); H1 (~3 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Build something Lovable”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-01.webp) · imagery: slot 1

### 2. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. About one full screen (917px at 1440), own light band #fcfbf8; 13 images/icons (a set of cards or a small gallery); no interactive controls; 4 headings → ~3 items under a title.
- Slots: Section title (~4 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “One platform. Endless possibilities.”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-02.webp)

### 3. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Tall, ≈1.9 screens (1700px at 1440), own light band #fcfbf8; 14 images/icons (a set of cards or a small gallery); 5 buttons (tabs, toggles or per-card actions); 6 headings → ~5 items under a title.
- Slots: Section title (~4 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “For building and beyond”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-03.webp) · imagery: slot 2

### 4. Logo cloud — borrow trust from recognisable customers or partners.
- Layout: a single row or wall of monochrome marks with a one-line lead-in. Half to one screen (409px at 1440), own light band #fcfbf8; 6 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: One-line lead-in (e.g. “Trusted by…”); 6–10 monochrome customer/partner marks (your own, with permission).
- Topic (tone/length only — never reuse): “Trusted by top brands”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-04.webp)

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (1120px at 1440), own light band #fcfbf8; 19 image elements (icons, logos, product UI — not 19 photos); 12 buttons (tabs, toggles or per-card actions).
- Slots: Heading (~5 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “The proof is in production”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-05.webp)

### 6. Stats — prove scale or impact with a few big numbers.
- Layout: 3–4 large numerals with short labels in a row. About one full screen (848px at 1440), own light band #fcfbf8; 2 image/graphics; no interactive controls.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “Millions count on Lovable”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-06.webp)

### 7. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. Half to one screen (719px at 1440), own light band #f7f4ed; 25 image elements (icons, logos, product UI — not 25 photos); one primary button, 57 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- Topic (tone/length only — never reuse): “Company”
- [Screenshot](https://uidiscovery.com/media/captures/lovable/s-07.webp)

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#01006b` | page background | — |
| foreground | `#f7f4ed` | body text, headings | 15.8:1 |
| accent | `#f7f4ed` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#1c1c1c` | cards, inputs, alternate bands | text on it 15.5:1 |
| muted | `#616161` | secondary text, borders | 2.8:1 — borders / large text only |

Captured palette: `#01006b` `#010000` `#000000` `#1c1c1c` `#f7f4ed` `#616161`. Section bands top→bottom: `#fcfbf8` → `#f7f4ed`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, cool) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #01006b;
  --foreground: #f7f4ed;
  --accent: #f7f4ed;
  --surface: #1c1c1c;
  --muted: #616161;
  --font-heading: "Manrope", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Manrope", ui-sans-serif, system-ui, sans-serif;
  --radius: 12px; /* calibrate from the screenshot */
}

/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
  --color-background: var(--background);
  --color-foreground: var(--foreground);
  --color-accent: var(--accent);
  --color-surface: var(--surface);
  --color-muted: var(--muted);
  --font-heading: var(--font-heading);
  --font-sans: var(--font-body);
}
```

### Typography
- Headings: **Manrope** (Google Fonts) — reference uses Camera Plain. “Camera Plain” is a licensed face — use Manrope (or Figtree) as the free stand-in, or license the original.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.75rem, 6vw, 5rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.

### Spacing & rhythm
Sections run ≈900px tall at 1440 (median; range 409–1700px, captures cap at 1700px) — roughly a screen per idea. Start with 96–120px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 1 time down the page — use band changes to mark chapters. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows. Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.

## 6. Imagery plan

Measured from 4 section screenshots: mostly **typography with little or no imagery**, some abstract 3D / gradient art (dark, cool, AI). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Hero → abstract 3D / gradient
- Abstract art — gradient, 3D or atmospheric graphics, seen in the capture. (measured from the screenshot) Count: a set of ~3 in one consistent style. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/lovable/s-01.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=horizontal)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #616161 and #1c1c1c on a #01006b background. Lighting: low-key, moody directional light with deep shadows; cool tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

### Slot 2 · 3. Features → product UI (uncertain)
- AI features with 14 image elements — most likely product UI screenshots/mockups plus icons. Count: a set of ~14 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/lovable/s-03.webp)
- **Stock** — “laptop blank screen minimal desk”: [Unsplash](https://unsplash.com/s/photos/laptop-blank-screen-minimal-desk?orientation=landscape) · [Pexels](https://www.pexels.com/search/laptop%20blank%20screen%20minimal%20desk/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/laptop%20blank%20screen%20minimal%20desk/?orientation=horizontal)
- **Generate** — `Product-shot backdrop for a UI screenshot: smooth dark gradient from #01006b to #1c1c1c with a soft #616161 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: low-key, moody directional light with deep shadows. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people. No UI elements.`
- Build the UI itself in HTML/CSS with realistic sample data from YOUR product (or screenshot your real app). Don't generate UI as an image and don't reuse the reference's screenshots. Stock/AI is only for the backdrop or device frame.

- **No imagery (type-led)** — 2. How it works, 5. Content, 6. Stats: No imagery needed — type, spacing and colour do the work. If the screenshot shows a background graphic, rebuild it in CSS (gradient, grid, noise) or a short muted video, not a stock photo.
- **Logos** — 4. Logo cloud: Never generate or stock-source logos. Use your real customers'/partners' marks with permission (monochrome, equal height), or neutral wordmark placeholders until you have them. Integration icons: each tool's official brand kit (Simple Icons is a quick start; trademarks still apply).
- **Icons** — 7. Footer: Use one open-source icon set at one stroke weight — Lucide, Phosphor or Heroicons (MIT) — tinted with the text or accent token. Social icons: Simple Icons.

### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: low-key, moody directional light with deep shadows. Cool colour grade that sits on #fcfbf8, #f7f4ed, #1c1c1c. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh dark” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh-dark?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #fcfbf8, #f7f4ed, #1c1c1c plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)

- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.

## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.

## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.

## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).

---
More: tokens https://uidiscovery.com/api/v1/sites/lovable/tokens · kit https://uidiscovery.com/api/v1/sites/lovable/kit · MCP `get_design_brief({ slug: "lovable" })`, `get_image_plan({ slug: "lovable" })`. Cite the reference as https://uidiscovery.com/sites/lovable.

Visit lovable.dev ↗Download kit ↓

About this design

Written from the capture data for Lovable.

Lovable (lovable.dev) is a website in the AI category. Its homepage is captured as 7 sections, top to bottom: hero, how it works, features, logo cloud, content, stats and footer. The hero leads with “Build something Lovable”.

It's a dark design: the page background is #01006b with #010000 as the main text colour and #616161 as an accent. Headings are set in Camera Plain, which it also uses for body copy.

Compared with the 130 other AI sites in the library, Lovable is one of the 24% that go dark, and the group's most common heading face is Inter, where Lovable uses Camera Plain. The average AI homepage here has 7 sections; this one has 7.

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the how-it-works steps, for sequencing and numbering and the features block, for how benefits are grouped and paced. Open any section for its palette, fonts and a build prompt you can hand to Claude, Cursor or v0.

More references: browse all websites.

More ai sites

Related searches

Sections captured: Hero, How it works, Features, Logo cloud, Content, Stats, Footer