Brian Lovin — Designer and software engineer living in San Francisco,…

Platform
Websites
Category
Portfolio
Style
Light
Type
Inter
Updated
Sep 2026

Build with AI

An original design in the taste of Brian Lovin — structure, tokens, font swaps and an imagery plan (1,328 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: "brian-lovin" }) and get_image_plan({ slug: "brian-lovin" })):

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Brian Lovin — 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 Brian Lovin: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Brian Lovin'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
- Brian Lovin (brianlovin.com): Portfolio marketing website, light.
- 1 section: About.
- Spacing: long, content-rich sections (median ≈1516px tall at 1440).
- Type: one family (Inter). Imagery: mostly photography.

## 4. Page structure (top to bottom)

### 1. About — tell the story or mission behind the brand.
- Layout: text block with a supporting image. Tall, ≈1.7 screens (1516px at 1440), page background; 11 images/icons (a set of cards or a small gallery); 23 links (link lists / navigation).
- Slots: Heading (~3 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Brian Lovin”
- [Screenshot](https://uidiscovery.com/media/captures/brian-lovin/s-01.webp) · imagery: slot 1

Inner pages also captured (About, Blog): https://uidiscovery.com/sites/brian-lovin?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#ffffff` | page background | — |
| foreground | `#080000` | body text, headings | 20.8:1 |
| accent | `#420000` | primary buttons, links, highlights — sparingly | 17.1:1 |
| surface | `#ffffff` | cards, inputs, alternate bands | text on it 20.8:1 |
| muted | `#230000` | secondary text, borders | 19.6:1 |

Captured palette: `#ffffff` `#420000` `#080000` `#230000`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, warm) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #ffffff;
  --foreground: #080000;
  --accent: #420000;
  --surface: #ffffff;
  --muted: #230000;
  --font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Inter", 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: **Inter** (Google Fonts) — reference uses Inter. Free to use — load it directly.
- 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.5rem, 5vw, 4.25rem), 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 ≈1516px tall at 1440 (median; range 1516–1516px, captures cap at 1700px) — long, content-rich chapters. Start with 96–128px vertical padding per section on desktop and about two-thirds of that on mobile. One continuous background — separate sections with space and type, not colour bands. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.

### Shape, depth & theme
Radii and shadows weren't measured. Read exact corner radius, border and shadow treatment from the screenshots. Light-first; for a dark mode use a near-black (not #000) background, ~90% white text, lift surfaces with lightness not shadow, re-check the accent.

## 6. Imagery plan

Best guess: mostly **photography** (light, warm, Portfolio). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.

### Slot 1 · About → photography
- Portfolio references lean on photography. Count: a set of ~11 in one consistent style. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/brian-lovin/s-01.webp)
- **Stock** — “design studio workspace”: [Unsplash](https://unsplash.com/s/photos/design-studio-workspace?orientation=portrait) · [Pexels](https://www.pexels.com/search/design%20studio%20workspace/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/design%20studio%20workspace/?orientation=vertical)
- **Generate** — `Photograph: design studio workspace. Composition: candid, documentary feel. Lighting: soft natural daylight, airy and high-key. Warm colour grade that sits on #ffffff, #420000. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`


### 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:
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #420000 and #230000 on a #ffffff background. Lighting: soft natural daylight, airy and high-key; warm 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.` · stock: [“abstract gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: design studio workspace, friendly simplified shapes, limited palette of #ffffff, #420000 plus one soft neutral, plenty of empty background, consistent line weight, warm mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“lifestyle flat illustration” on Unsplash](https://unsplash.com/s/photos/lifestyle-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/brian-lovin/tokens · kit https://uidiscovery.com/api/v1/sites/brian-lovin/kit · MCP `get_design_brief({ slug: "brian-lovin" })`, `get_image_plan({ slug: "brian-lovin" })`. Cite the reference as https://uidiscovery.com/sites/brian-lovin.

Visit brianlovin.com ↗Download kit ↓

About this design

Written from the capture data for Brian Lovin.

Brian Lovin (brianlovin.com) is a website in the Portfolio category. Its homepage is captured as 1 section, top to bottom: about. We also captured its about and blog pages.

It's a light design: the page background is #ffffff with #420000 as the main text colour. Headings are set in Inter, which it also uses for body copy.

Compared with the 81 other Portfolio sites in the library, Brian Lovin sits with the 78% that stay light, and shares the group's most common heading face, Inter. The average Portfolio homepage here has 4 sections; this one has 1.

Worth studying here: the about section, for how the company story is told and the blog teaser, for card anatomy and metadata. 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 portfolio sites

Related searches

Sections captured: About, Content, Content, Blog, Content