Relace — AI Models & Infrastructure for Coding Agents

Platform
Websites
Category
Developer Tools
Style
Light
Type
Parabole Trial Text
Updated
Sep 2026

Build with AI

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

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Relace — 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 Relace: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Relace'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
- Relace (relace.ai): Developer Tools marketing website, dark.
- 9 sections: Hero → Features → Content → Call to action.
- Spacing: about a screen per idea (median section ≈598px).
- Hero headline: 5 words — short and punchy; keep yours under ~9.
- Type: one family (Parabole Trial Text). 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 (1057px at 1440), own light band #fffef2; 1 image/graphic; 2 text links instead of buttons.
- Slots: Eyebrow / announcement pill (optional); H1 (~5 words, like the reference); Supporting line, 1–2 sentences; Text link action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Models built for coding agents”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-01.webp) · imagery: slot 1

### 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. Tall, ≈1.9 screens (1700px at 1440), own light band #fffef2; 5 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~6 words, like the reference); 5 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Everything you need for autonomous codegen”
- [Screenshot](https://uidiscovery.com/media/captures/relace/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 (851px at 1440), own light band #fffef2; 1 image/graphic; no interactive controls.
- Slots: Section title (~10 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “State of the art SLMs as tools for coding agents”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-04.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. About one full screen (947px at 1440), own light band #fffef2; 1 image/graphic; no interactive controls.
- Slots: Section title (~8 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Source control designed for the models using it”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-05.webp)

### 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. Compact band (187px at 1440), own light band #fffef2; no images (type-led); no interactive controls.
- Slots: Section title (~6 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Building blocks for reliability and scale”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-06.webp)

### 6. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (406px at 1440), own light band #fffef2; no images (type-led); no interactive controls.
- Slots: Heading; Body copy.
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-07.webp)

### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (498px at 1440), own light band #fffef2; 4 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “Trusted by trailblazers”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-08.webp) · imagery: slot 3

### 8. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (496px at 1440), own light band #fffef2; no images (type-led); no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Frequently asked questions”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-09.webp)

### 9. Call to action — close the page with one clear next step.
- Layout: short headline + one primary action on a contrasting band. Half to one screen (598px at 1440), own light band #fffef2; 1 image/graphic; 11 links (link lists / navigation).
- Slots: Headline (~4 words, like the reference); One sentence of support; Text link action.
- Topic (tone/length only — never reuse): “Get started in minutes”
- [Screenshot](https://uidiscovery.com/media/captures/relace/s-10.webp) · imagery: slot 4

Inner pages also captured (Pricing, About, Blog, Security): https://uidiscovery.com/sites/relace?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#191918` | page background | — |
| foreground | `#fffef2` | body text, headings | 17.4:1 |
| accent | `#fcaa2d` | primary buttons, links, highlights — sparingly | 9.2:1 |
| surface | `#000000` | cards, inputs, alternate bands | text on it 20.7:1 |
| muted | `#fffef2` | secondary text, borders | 17.4:1 |

Captured palette: `#191918` `#fffef2` `#000000` `#fcaa2d`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, warm) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #191918;
  --foreground: #fffef2;
  --accent: #fcaa2d;
  --surface: #000000;
  --muted: #fffef2;
  --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 Parabole Trial Text. “Parabole Trial Text” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- 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 ≈598px tall at 1440 (median; range 187–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. 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. 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**, some photography (dark, warm, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Hero → photography
- Photography, seen in the capture (land, hill). (measured from the screenshot) Count: 1. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/relace/s-01.webp)
- **Stock** — “abstract gradient mesh dark”: [Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20gradient%20mesh%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20gradient%20mesh%20dark/?orientation=horizontal)
- **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. Warm colour grade that sits on #fffef2, #fcaa2d, #000000. 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)
- Developer Tools features with 1 image elements — most likely product UI screenshots/mockups plus icons. Count: 1. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/relace/s-04.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 #191918 to #000000 with a soft #fcaa2d 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 3 · 7. Content → illustration (uncertain)
- Light Developer Tools section with a few graphics — illustration, icon 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/relace/s-08.webp)
- **Stock** — “technology flat illustration”: [Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=portrait) · [Pexels](https://www.pexels.com/search/technology%20flat%20illustration/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/technology%20flat%20illustration/?orientation=vertical)
- **Generate** — `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #fffef2, #fcaa2d, #000000 plus one soft neutral, plenty of empty background, consistent line weight, warm 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.

### Slot 4 · 9. Call to action → photography
- Photography, seen in the capture (land). (measured from the screenshot) Count: 1. Aspect: 21:9 (background). Look first: [ref 1](https://uidiscovery.com/media/captures/relace/s-10.webp)
- **Stock** — “minimal desk with laptop wide shot dark”: [Unsplash](https://unsplash.com/s/photos/minimal-desk-with-laptop-wide-shot-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/minimal%20desk%20with%20laptop%20wide%20shot%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/minimal%20desk%20with%20laptop%20wide%20shot%20dark/?orientation=horizontal)
- **Generate** — `Photograph: minimal desk with laptop wide shot. Composition: low-detail texture so overlaid text stays readable. Lighting: low-key, moody directional light with deep shadows. Warm colour grade that sits on #fffef2, #fcaa2d, #000000. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 21:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

- **No imagery (type-led)** — 2. Features, 4. Features, 5. Features, 6. Content, 8. Content: 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, glossy glass-like shapes and a smooth gradient in #fcaa2d and #fffef2 on a #191918 background. Lighting: low-key, moody directional light with deep shadows; 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 dark gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-dark-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/relace/tokens · kit https://uidiscovery.com/api/v1/sites/relace/kit · MCP `get_design_brief({ slug: "relace" })`, `get_image_plan({ slug: "relace" })`. Cite the reference as https://uidiscovery.com/sites/relace.

Visit relace.ai ↗Download kit ↓

About this design

Written from the capture data for Relace.

Relace (relace.ai) is a website in the Developer Tools category. Its homepage is captured as 9 sections, top to bottom: hero, features, content and call to action. We also captured its pricing, about, blog and security pages. The hero leads with “Models built for coding agents”.

It's a light design: the page background is #191918 with #fffef2 as the main text colour and #fcaa2d as an accent. Headings are set in Parabole Trial Text, which it also uses for body copy.

Compared with the 66 other Developer Tools sites in the library, Relace sits with the 58% that stay light, and the group's most common heading face is Inter, where Relace uses Parabole Trial Text. The average Developer Tools homepage here has 8 sections; this one has 9.

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 closing call to action, for contrast and copy length. 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, Features, Features, Content, Content, Content, Call to action, Footer, Content