Weave — AI to measure engineers and agents

Platform
Websites
Category
Developer Tools
Style
Light
Type
PP Mori, Inter Display
Updated
Sep 2026

Build with AI

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

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Weave — 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 Weave: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Weave'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
- Weave (workweave.dev): Developer Tools marketing website, light.
- 10 sections: Content → Statement → Content → Stats → Features → Content → Features → Footer.
- Spacing: about a screen per idea (median section ≈580px).
- Type: PP Mori headings over Inter Display body. Imagery: mostly typography with little or no imagery, some photography.

## 4. Page structure (top to bottom)

### 1. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (540px at 1440), page background; 6 images/icons (a set of cards or a small gallery); 5 buttons (tabs, toggles or per-card actions).
- Slots: Heading; Body copy; Supporting visual (see image plan); Primary + secondary action.
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-01.webp) · imagery: slot 1

### 2. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (339px at 1440), page background; no images (type-led); primary + secondary button.
- Slots: Heading (~8 words, like the reference); Body copy; Primary + secondary action.
- Topic (tone/length only — never reuse): “Engineering and token intelligence to optimize the SDLC”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-02.webp)

### 3. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Half to one screen (750px at 1440), page background; no images (type-led); no interactive controls.
- Slots: Heading (~7 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Measure your SDLC from prompt to production”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-03.webp)

### 4. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (590px at 1440), page background; no images (type-led); no interactive controls.
- Slots: Heading (~5 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Know where your team stands”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-04.webp)

### 5. 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 (560px at 1440), page background; no images (type-led); no interactive controls.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- Topic (tone/length only — never reuse): “Know where every token goes.”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-05.webp)

### 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. Tall, ≈1.9 screens (1700px at 1440), own light band #eeecea; 1 image/graphic; one primary button.
- Slots: Section title (~12 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; One primary action.
- Topic (tone/length only — never reuse): “Route to the most cost efficient model, without compromising speed or quality.”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-06.webp)

### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (186px at 1440), page background; no images (type-led); one primary button.
- Slots: Heading (~3 words, like the reference); Body copy; One primary action.
- Topic (tone/length only — never reuse): “Agent Wooly”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-08.webp)

### 8. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (580px at 1440), page background; 12 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/weave/s-10.webp)

### 9. 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 (570px at 1440), page background; no images (type-led); one primary button.
- Slots: Section title (~7 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; One primary action.
- Topic (tone/length only — never reuse): “Built for teams that can’t afford compromise”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-11.webp)

### 10. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. About one full screen (809px at 1440), own dark band #161412; 3 image/graphics; 69 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- Topic (tone/length only — never reuse): “Company”
- [Screenshot](https://uidiscovery.com/media/captures/weave/s-12.webp)

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#f5f3f2` | page background | — |
| foreground | `#fb4f1f` | body text, headings | 3.0:1 ⚠ below AA — adjust |
| accent | `#fb4f1f` | none captured — monochrome. Primary buttons invert (foreground fill, background text); add your brand colour only for small highlights | — |
| surface | `#f3f1eb` | cards, inputs, alternate bands | text on it 3.0:1 |
| muted | `#e4e0dd` | secondary text, borders | 1.2:1 — borders / large text only |

Captured palette: `#f5f3f2` `#e4e0dd` `#f3f1eb` `#fb4f1f` `#e0dffe` `#eeecea`. Section bands top→bottom: `#f5f3f2` → `#eeecea` → `#161412`. 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: #f5f3f2;
  --foreground: #fb4f1f;
  --accent: #fb4f1f;
  --surface: #f3f1eb;
  --muted: #e4e0dd;
  --font-heading: "Hanken Grotesk", 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: **Hanken Grotesk** (Google Fonts) — reference uses PP Mori. “PP Mori” is a licensed face — use Hanken Grotesk (or Inter) as the free stand-in, or license the original.
- Body: **Inter** (Google Fonts) — reference uses Inter Display. Free to use.
- 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 ≈580px tall at 1440 (median; range 186–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 3 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
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 6 section screenshots: mostly **typography with little or no imagery**, some photography (light, warm, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Content → photography
- Photography, seen in the capture (cord, yarn, toy). (measured from the screenshot) Count: a set of ~6 in one consistent style. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/weave/s-01.webp)
- **Stock** — “abstract gradient mesh”: [Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=portrait) · [Pexels](https://www.pexels.com/search/abstract%20gradient%20mesh/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/abstract%20gradient%20mesh/?orientation=vertical)
- **Generate** — `Photograph: abstract gradient mesh. Composition: simple composition with one focal point. Lighting: soft natural daylight, airy and high-key. Warm colour grade that sits on #f5f3f2, #fb4f1f, #f3f1eb. 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.`

- **No imagery (type-led)** — 2. Statement, 3. Statement, 4. Content, 5. Stats, 6. Features, 7. Content, 8. Content, 9. 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.
- **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:
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #e4e0dd and #f3f1eb on a #f5f3f2 background. Lighting: soft natural daylight, airy and high-key; warm 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 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: abstract gradient mesh, friendly simplified shapes, limited palette of #f5f3f2, #fb4f1f, #f3f1eb plus one soft neutral, plenty of empty background, consistent line weight, warm 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/weave/tokens · kit https://uidiscovery.com/api/v1/sites/weave/kit · MCP `get_design_brief({ slug: "weave" })`, `get_image_plan({ slug: "weave" })`. Cite the reference as https://uidiscovery.com/sites/weave.

Visit workweave.dev ↗Download kit ↓

Design tokens

Weave’s palette and type, mapped to roles. Drop the rules file into Cursor, Claude Code or Codex so what they build stops looking like a template.

  • background#f5f3f2
  • foreground#fb4f1f
  • accent#fb4f1f
  • surface#f3f1eb
  • muted#e4e0dd
/* Tailwind v4 — paste into your globals.css */
@theme {
  --color-background: #f5f3f2;
  --color-foreground: #fb4f1f;
  --color-accent: #fb4f1f;
  --color-surface: #f3f1eb;
  --color-muted: #e4e0dd;
  --font-heading: "PP Mori", ui-sans-serif, system-ui, sans-serif;
  --font-sans: "Inter Display", ui-sans-serif, system-ui, sans-serif;
}

About this design

Written from the capture data for Weave.

Weave (workweave.dev) is a website in the Developer Tools category. Its homepage is captured as 10 sections, top to bottom: content, statement, content, stats, features, content, features and footer.

It's a light design: the page background is #f5f3f2 with #e4e0dd as the main text colour and #fb4f1f as an accent. Headings are set in PP Mori, body copy in Inter Display.

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

Worth studying here: the statement block, for large-type rhythm, the stats band, for how numbers are sized against their labels and the features block, for how benefits are grouped and paced. 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: Content, Statement, Statement, Content, Stats, Features, Content, Content, Features, Footer