Preview the prompt +
# Build brief — an original marketing website in the taste of Duna
> Reference: https://duna.com · UIDiscovery: https://uidiscovery.com/sites/duna · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/duna/full.png) · [scroll video](https://uidiscovery.com/media/captures/duna/preview.mp4)
## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Duna — 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 Duna: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Duna'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
- Duna (duna.com): Finance marketing website, light.
- 10 sections: Hero → Content → Features → Content → Features → Content → Features → Content → Features.
- Spacing: short, dense bands (median section ≈496px).
- Hero headline: 6 words — short and punchy; keep yours under ~9.
- Type: GT America headings over system sans-serif body. Imagery: mostly typography with little or no imagery, some photography.
## 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 (855px at 1440), page background; 2 image/graphics; 2 text links instead of buttons.
- Slots: Eyebrow / announcement pill (optional); H1 (~6 words, like the reference); Supporting line, 1–2 sentences; Text link action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Defining the future of business onboarding”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-01.webp) · imagery: slot 1
### 2. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (810px at 1440), page background; 3 image/graphics; no interactive controls.
- Slots: Heading (~8 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “Agents collect the evidence. Analysts do the judgement.”
- [Screenshot](https://uidiscovery.com/media/captures/duna/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. About one full screen (920px at 1440), page background; 7 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~3 words, like the reference); 7 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Trusted by leaders”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-03.webp) · imagery: slot 2
### 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. Half to one screen (740px at 1440), page background; 3 image/graphics; 1 text link instead of buttons.
- Slots: Section title (~4 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “AI built for compliance.”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-04.webp) · imagery: slot 3
### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (496px at 1440), page background; 10 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-06.webp) · imagery: slot 4
### 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. Compact band (197px at 1440), page background; 1 image/graphic; 1 text link instead of buttons.
- Slots: Section title (~6 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Save time with automated case management”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-07.webp)
### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (496px at 1440), page background; 6 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-08.webp)
### 8. 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. Compact band (176px at 1440), page background; 1 image/graphic; 1 text link instead of buttons.
- Slots: Section title (~5 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Ensure compliance at every stage”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-09.webp)
### 9. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (496px at 1440), page background; 6 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-10.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 (490px at 1440), own light band #f7f7f5; 4 images/icons (a set of cards or a small gallery); 1 text link instead of buttons.
- Slots: Section title (~3 words, like the reference); 4 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Safe and secure”
- [Screenshot](https://uidiscovery.com/media/captures/duna/s-11.webp)
Inner pages also captured (Product, About, Sign up, Blog, Careers, Contact, Security): https://uidiscovery.com/sites/duna?view=pages
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#ffffff` | page background | — |
| foreground | `#000000` | body text, headings | 21.0:1 |
| accent | `#1b0624` | primary buttons, links, highlights — sparingly | 19.1:1 |
| surface | `#ffffff` | cards, inputs, alternate bands | text on it 21.0:1 |
| muted | `#4d4846` | secondary text, borders | 9.0:1 |
Captured palette: `#ffffff` `#1b0624` `#292421` `#1a1816` `#000000` `#4d4846`. Section bands top→bottom: `#ffffff` → `#f7f7f5`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, neutral, desaturated) and proportions; swap the accent for the user's brand colour.
### Tokens
```css
:root {
--background: #ffffff;
--foreground: #000000;
--accent: #1b0624;
--surface: #ffffff;
--muted: #4d4846;
--font-heading: "Inter Tight", 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 Tight** (Google Fonts) — reference uses GT America. “GT America” is a licensed face — use Inter Tight (or Libre Franklin) as the free stand-in, or license the original.
- Body: **Inter** (Google Fonts) — reference uses system sans-serif. The reference uses the system stack; Inter (or plain system-ui) keeps that neutral feel.
- 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 ≈496px tall at 1440 (median; range 176–920px, captures cap at 1700px) — short, dense bands. Start with 64–80px 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
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
Measured from 8 section screenshots: mostly **typography with little or no imagery**, some photography (light, neutral, desaturated, Finance). Still glance at the linked screenshots to match the exact mood.
### Slot 1 · 1. Hero → photography
- Photography, seen in the capture (land, hill, sunset sunrise). (measured from the screenshot) Count: a set of ~2 in one consistent style. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/duna/s-01.webp)
- **Stock** — “person paying with phone”: [Unsplash](https://unsplash.com/s/photos/person-paying-with-phone?orientation=landscape) · [Pexels](https://www.pexels.com/search/person%20paying%20with%20phone/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/person%20paying%20with%20phone/?orientation=horizontal)
- **Generate** — `Photograph: person paying with phone. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Neutral, desaturated colour grade that sits on #ffffff, #1b0624. 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.`
### Slot 2 · 3. Features → product UI (uncertain)
- Finance features with 7 image elements — most likely product UI screenshots/mockups plus icons. Count: a set of ~7 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/duna/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 light gradient from #ffffff to #ffffff with a soft #1b0624 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: soft natural daylight, airy and high-key. 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.
### Slot 3 · 4. Features → photography
- Photography, seen in the capture (blue sky). (measured from the screenshot) Count: a set of ~3 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/duna/s-04.webp)
- **Stock** — “person paying with phone close up”: [Unsplash](https://unsplash.com/s/photos/person-paying-with-phone-close-up?orientation=landscape) · [Pexels](https://www.pexels.com/search/person%20paying%20with%20phone%20close%20up/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/person%20paying%20with%20phone%20close%20up/?orientation=horizontal)
- **Generate** — `Photograph: person paying with phone close up. Composition: tight crop, identical framing and background across the whole set. Lighting: soft natural daylight, airy and high-key. Neutral, desaturated colour grade that sits on #ffffff, #1b0624. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
### Slot 4 · 5. Content → illustration (uncertain)
- Light Finance section with a few graphics — illustration, icon art or a product shot. Count: a set of ~10 in one consistent style. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/duna/s-06.webp)
- **Stock** — “finance flat illustration”: [Unsplash](https://unsplash.com/s/photos/finance-flat-illustration?orientation=portrait) · [Pexels](https://www.pexels.com/search/finance%20flat%20illustration/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/finance%20flat%20illustration/?orientation=vertical)
- **Generate** — `Flat vector illustration: person paying with phone, friendly simplified shapes, limited palette of #ffffff, #1b0624 plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated mood. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- Uncertain: this could equally be photography, a product shot or icon art — open the reference screenshots and match what you see.
- **No imagery (type-led)** — 2. Content, 6. Features, 7. Content, 8. Features, 9. Content, 10. 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.
### 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 #1b0624 and #4d4846 on a #ffffff background. Lighting: soft natural daylight, airy and high-key; neutral, desaturated 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)
- **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/duna/tokens · kit https://uidiscovery.com/api/v1/sites/duna/kit · MCP `get_design_brief({ slug: "duna" })`, `get_image_plan({ slug: "duna" })`. Cite the reference as https://uidiscovery.com/sites/duna.
