Preview the prompt +
# Build brief — an original marketing website in the taste of Builder.io
> Reference: https://www.builder.io · UIDiscovery: https://uidiscovery.com/sites/builder-io · captured 2026-09-21 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/builder-io/full.webp) · [scroll video](https://uidiscovery.com/media/captures/builder-io/preview.mp4)
## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Builder.io — 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 Builder.io: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Builder.io'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
- Builder.io (builder.io): AI marketing website, dark.
- 12 sections: Hero → Statement → Features → Integrations → Stats → Features → Footer.
- Spacing: about a screen per idea (median section ≈718px).
- Hero headline: 11 words — a full sentence; keep yours to one thought.
- Type: Geist headings over Poppins body. Imagery: mostly typography with little or no imagery.
## 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. Half to one screen (550px at 1440), page background; 19 image elements (icons, logos, product UI — not 19 photos); 2 text links instead of buttons.
- Slots: Eyebrow / announcement pill (optional); H1 (~11 words, like the reference); Supporting line, 1–2 sentences; Text link action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Build software with your team and agents Maya • Designer Semibold”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-01.webp)
### 2. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (275px at 1440), page background; no images (type-led); no interactive controls.
- Slots: Heading (~4 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “One codebase. Every role”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/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. Half to one screen (640px at 1440), page background; 12 images/icons (a set of cards or a small gallery); 4 buttons (tabs, toggles or per-card actions); 4 headings → ~3 items under a title.
- Slots: Section title (~7 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Code the hard parts. Offload the follow-ups.”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-03.webp)
### 4. 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. About one full screen (898px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title (~5 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Production code, edited like design”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-04.webp) · imagery: slot 1
### 5. 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. About one full screen (938px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title (~5 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Publish dynamic content with prompts”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-05.webp) · imagery: slot 1
### 6. 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. About one full screen (830px at 1440), page background; 6 images/icons (a set of cards or a small gallery); 3 text links instead of buttons; 4 headings → ~3 items under a title.
- Slots: Section title (~7 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Build together, from first idea to production”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-06.webp)
### 7. 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. About one full screen (898px at 1440), page background; 12 images/icons (a set of cards or a small gallery); 2 text links instead of buttons.
- Slots: Section title (~9 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Two products to go from idea to production faster”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-07.webp)
### 8. Integrations — show that it fits the tools the visitor already uses.
- Layout: a grid of app icons around a short explanation. Half to one screen (487px at 1440), page background; 23 image elements (icons, logos, product UI — not 23 photos); no interactive controls.
- Slots: Title + explanation; Icon grid of tools you truly integrate with.
- Topic (tone/length only — never reuse): “Works with the stack your teams already use”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-08.webp)
### 9. Stats — prove scale or impact with a few big numbers.
- Layout: 3–4 large numerals with short labels in a row. Half to one screen (655px at 1440), page background; 14 images/icons (a set of cards or a small gallery); primary + secondary button; 6 headings → ~5 items under a title.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “Built for teams shipping at scale”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-09.webp)
### 10. 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. Half to one screen (551px at 1440), page background; 4 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~4 words, like the reference); 4 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Enterprise security & privacy”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-10.webp)
### 11. 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. Half to one screen (718px at 1440), page background; 5 images/icons (a set of cards or a small gallery); 3 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~10 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Most of your team is waiting to contribute. Let them.”
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-11.webp)
### 12. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. About one full screen (825px at 1440), page background; 9 images/icons (a set of cards or a small gallery); inline form (1 field, e.g. email capture), 5 buttons (tabs, toggles or per-card actions), 51 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- [Screenshot](https://uidiscovery.com/media/captures/builder-io/s-12.webp)
Inner pages also captured (Pricing, Product, Customers, About, Sign up, Blog, Enterprise, Careers, Contact, Security): https://uidiscovery.com/sites/builder-io?view=pages
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#0a0a0a` | page background | — |
| foreground | `#faf9f5` | body text, headings | 18.8:1 |
| accent | `#01c8f1` | primary buttons, links, highlights — sparingly | 9.9:1 |
| surface | `#0f0f0f` | cards, inputs, alternate bands | text on it 18.2:1 |
| muted | `#aeadac` | secondary text, borders | 8.8:1 |
Captured palette: `#0a0a0a` `#faf9f5` `#aeadac` `#01c8f1` `#0f0f0f`. 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: #0a0a0a;
--foreground: #faf9f5;
--accent: #01c8f1;
--surface: #0f0f0f;
--muted: #aeadac;
--font-heading: "Geist", ui-sans-serif, system-ui, sans-serif;
--font-body: "Poppins", 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: **Geist** (Google Fonts) — reference uses Geist. Free to use — load it directly.
- Body: **Poppins** (Google Fonts) — reference uses Poppins. Free to use — load it directly.
- 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 ≈718px tall at 1440 (median; range 275–938px, 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. 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
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 8 section screenshots: mostly **typography with little or no imagery** (dark, cool, AI). Still glance at the linked screenshots to match the exact mood.
### Slot 1 · 4. Features, 5. Features → product UI (uncertain)
- AI sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/builder-io/s-04.webp) [ref 2](https://uidiscovery.com/media/captures/builder-io/s-05.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 #0a0a0a to #0f0f0f with a soft #01c8f1 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)** — 1. Hero, 2. Statement, 3. Features, 6. Features, 7. Features, 9. Stats, 10. Features, 11. Features: 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** — 8. Integrations: 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** — 12. 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 #0a0a0a, #01c8f1, #0f0f0f. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. 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)
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #01c8f1 and #aeadac on a #0a0a0a 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 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract dark gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #0a0a0a, #01c8f1, #0f0f0f plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 3:2. 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/builder-io/tokens · kit https://uidiscovery.com/api/v1/sites/builder-io/kit · MCP `get_design_brief({ slug: "builder-io" })`, `get_image_plan({ slug: "builder-io" })`. Cite the reference as https://uidiscovery.com/sites/builder-io.
