Neon — Postgres backends for apps and agents

Platform
Websites
Category
Developer Tools
Style
Dark, Minimal
Type
Inter
Updated
Sep 2026

Build with AI

An original design in the taste of Neon — structure, tokens, font swaps and an imagery plan (2,535 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: "neon" }) and get_image_plan({ slug: "neon" })):

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Neon — 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 Neon: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Neon'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
- Neon (neon.com): Developer Tools marketing website, dark, minimal.
- 10 sections: Hero → Features → Logo cloud → Statement → Stats → Features → Content → Footer.
- Spacing: about a screen per idea (median section ≈787px).
- Hero headline: 12 words — a full sentence; keep yours to one thought.
- Type: one family (Inter). 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 (741px at 1440), page background; 22 image elements (icons, logos, product UI — not 22 photos); 4 text links instead of buttons.
- Slots: Eyebrow / announcement pill (optional); H1 (~12 words, like the reference); Supporting line, 1–2 sentences; Text link action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “The backend for apps and agents, built to scale on Lakebase Postgres.”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-01.webp)

### 2. 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 (638px at 1440), page background; 11 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~14 words, like the reference); 9 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Not just a Database. Neon is a complete backend platform with Authentication,…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-02.webp) · imagery: slot 1

### 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 (1001px at 1440), page background; 13 images/icons (a set of cards or a small gallery); no interactive controls; 4 headings → ~3 items under a title.
- Slots: Section title (~14 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Ready for coding agents. Create and branch environments the way you work with…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-03.webp) · imagery: slot 1

### 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. Tall, ≈1.9 screens (1700px at 1440), page background; 60 image elements (icons, logos, product UI — not 60 photos); 22 buttons (tabs, toggles or per-card actions).
- 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): “Scale from your first users to the Fortune 500. Startups ship on the same Neon…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-04.webp)

### 5. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Tall, ≈1.3 screens (1186px at 1440), own light band #e4f1eb; 1 image/graphic; no interactive controls.
- Slots: Heading (~14 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “The way we build software is changing, but the fundamentals remain the same:…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/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 (787px at 1440), own dark band #18191b; 4 images/icons (a set of cards or a small gallery); primary + secondary button.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “Autoscaling scales compute in real-time following your application. Optimized…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-06.webp)

### 7. 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 (750px at 1440), own dark band #18191b; 1 image/graphic; no interactive controls.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “Backed by giants. First founded by Postgres hackers with decades of expertise,…”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-07.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. About one full screen (1040px at 1440), own light band #e4f1eb; 6 images/icons (a set of cards or a small gallery); 1 text link instead of buttons; 5 headings → ~4 items under a title.
- Slots: Section title (~12 words, like the reference); 4 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Pay for what you use, not for the infrastructure you might need.”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-08.webp) · imagery: slot 1

### 9. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (708px at 1440), own dark band #151617; 4 images/icons (a set of cards or a small gallery); one primary button.
- Slots: Heading (~6 words, like the reference); Body copy; Supporting visual (see image plan); One primary action.
- Topic (tone/length only — never reuse): “The world's most advanced backend platform.”
- [Screenshot](https://uidiscovery.com/media/captures/neon/s-09.webp) · imagery: slot 2

### 10. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. Compact band (391px at 1440), page background; 3 image/graphics; 33 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/neon/s-10.webp)

Inner pages also captured (Blog): https://uidiscovery.com/sites/neon?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#000000` | page background | — |
| foreground | `#ffffff` | body text, headings | 21.0:1 |
| accent | `#ffffff` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#151617` | cards, inputs, alternate bands | text on it 18.1:1 |
| muted | `#303236` | secondary text, borders | 1.6:1 — borders / large text only |

Captured palette: `#000000` `#18191b` `#ffffff` `#e4f1eb` `#151617` `#303236`. Section bands top→bottom: `#000000` → `#e4f1eb` → `#18191b` → `#151617`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, neutral, desaturated) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #000000;
  --foreground: #ffffff;
  --accent: #ffffff;
  --surface: #151617;
  --muted: #303236;
  --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 ≈787px tall at 1440 (median; range 391–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 5 times 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
Flat surfaces, hairline 1px borders in the muted colour, small radii (4–8px), almost no shadow; 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 5 section screenshots: mostly **typography with little or no imagery** (dark, neutral, desaturated, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 2. Features, 3. Features, 8. Features → product UI (uncertain)
- Developer Tools 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/neon/s-02.webp) [ref 2](https://uidiscovery.com/media/captures/neon/s-03.webp) [ref 3](https://uidiscovery.com/media/captures/neon/s-08.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 #000000 to #151617 with a soft #303236 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.

### Slot 2 · 9. Content → abstract 3D / gradient (uncertain)
- Dark Developer Tools section with a few graphics — typically abstract 3D/gradient art or a product shot. Count: a set of ~4 in one consistent style. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/neon/s-09.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=portrait) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=vertical)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #303236 and #151617 on a #000000 background. Lighting: low-key, moody directional light with deep shadows; neutral, desaturated tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 4:5. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

- **No imagery (type-led)** — 1. Hero, 5. Statement, 6. Stats, 7. 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** — 10. 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. Neutral, desaturated colour grade that sits on #000000, #ffffff, #151617. 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)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #000000, #ffffff, #151617 plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated 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/neon/tokens · kit https://uidiscovery.com/api/v1/sites/neon/kit · MCP `get_design_brief({ slug: "neon" })`, `get_image_plan({ slug: "neon" })`. Cite the reference as https://uidiscovery.com/sites/neon.

Visit neon.com ↗Download kit ↓
neon.com

About this design

Written from the capture data for Neon.

Neon (neon.com) is a website in the Developer Tools category. Its homepage is captured as 10 sections, top to bottom: hero, features, logo cloud, statement, stats, features, content and footer. We also captured its blog page. The hero leads with “The backend for apps and agents, built to scale on Lakebase Postgres.”.

It's a dark design: the page background is #000000 with #18191b as the main text colour and #303236 as an accent. Headings are set in Inter, which it also uses for body copy.

Compared with the 66 other Developer Tools sites in the library, Neon is one of the 42% that go dark, and shares the group's most common heading face, Inter. The average Developer Tools homepage here has 8 sections; this one has 10.

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the features block, for how benefits are grouped and paced and the logo cloud, for how social proof is placed without shouting. 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 developer tools sites

Related searches

Sections captured: Hero, Features, Features, Logo cloud, Statement, Stats, Stats, Features, Content, Footer, Content, Content