monolayer — Turns code or intent into a running, self-managed system…

# Build brief — an original marketing website in the taste of monolayer

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as monolayer — 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 monolayer: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse monolayer'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
- monolayer (monolayer.dev): Developer Tools marketing website, dark.
- 14 sections: Statement → Content → Statement → How it works → Statement → How it works → Pricing.
- Spacing: about a screen per idea (median section ≈533px).
- Type: one family (PPFrama). Imagery: mostly typography with little or no imagery.

## 4. Page structure (top to bottom)

### 1. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. About one full screen (810px at 1440), own light band #e5e5e5; 1 image/graphic; one primary button.
- Slots: Heading (~14 words, like the reference); Body copy; Supporting visual (see image plan); One primary action.
- Topic (tone/length only — never reuse): “monolayer shifts software toward what it should be: a system that runs,…”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-01.webp)

### 2. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (324px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Heading (~14 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “writing code is only one part of getting software live. setup, deployment,…”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-02.webp)

### 3. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (194px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Heading (~14 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “monolayer takes code or intent and turns it into a running, self-managed system…”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-03.webp)

### 4. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.9 screens (1700px at 1440), own dark band #0f00b0; no images (type-led); no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “the system”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-04.webp)

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.5 screens (1330px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Heading (~3 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “connect your cloud”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-06.webp)

### 6. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (274px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Heading (~12 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “what used to be managed by hand, is now automated with monolayer”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-07.webp)

### 7. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Half to one screen (533px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “create”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-08.webp)

### 8. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Half to one screen (533px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “commit”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-09.webp)

### 9. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Half to one screen (533px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “connect”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-10.webp)

### 10. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Half to one screen (533px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “operate”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-11.webp)

### 11. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Half to one screen (533px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “scale”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-12.webp)

### 12. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Half to one screen (509px at 1440), own light band #e5e5e5; no images (type-led); no interactive controls.
- Slots: Heading (~14 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “you work from intent, not infrastructure. the system understands what needs to…”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-13.webp)

### 13. How it works — show the path from sign-up to value as numbered steps.
- Layout: numbered steps in a row or vertical timeline. Compact band (194px at 1440), own light band #c7beaa; no images (type-led); no interactive controls.
- Slots: Section title (~13 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “your infrastrucrute runs in your aws account and is billed directly by aws”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-14.webp)

### 14. Pricing — help the visitor pick a plan with minimal thinking.
- Layout: plan cards side by side, one highlighted, with a billing toggle if needed. Half to one screen (510px at 1440), own light band #c7beaa; 2 image/graphics; primary + secondary button; 5 headings → ~4 items under a title.
- Slots: Title + billing toggle; 4 plan cards: name, price, 4–6 features, action; Highlight one recommended plan; Small print (tax, trial).
- Topic (tone/length only — never reuse): “plan”
- [Screenshot](https://uidiscovery.com/media/captures/monolayer/s-15.webp)

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

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#000000` | page background | — |
| foreground | `#e5e5e5` | body text, headings | 16.7:1 |
| accent | `#0f00b0` | primary buttons, links, highlights — sparingly | 1.6:1 ⚠ not for text; use as a fill with #ffffff text (12.7:1) |
| surface | `#000000` | cards, inputs, alternate bands | text on it 16.7:1 |
| muted | `#e5e5e5` | secondary text, borders | 16.7:1 |

Captured palette: `#000000` `#e5e5e5` `#0f00b0`. Section bands top→bottom: `#e5e5e5` → `#0f00b0` → `#c7beaa`. 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: #000000;
  --foreground: #e5e5e5;
  --accent: #0f00b0;
  --surface: #000000;
  --muted: #e5e5e5;
  --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 PPFrama. “PPFrama” 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.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 ≈533px tall at 1440 (median; range 194–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. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.

## 6. Imagery plan

Measured from 12 section screenshots: mostly **typography with little or no imagery** (dark, cool, Developer Tools). Still glance at the linked screenshots to match the exact mood.

- **No imagery (type-led)** — 1. Statement, 2. Statement, 3. Statement, 4. Content, 5. Content, 6. Statement, 7. How it works, 8. How it works, 9. How it works, 10. How it works, 11. How it works, 12. Statement, 13. How it works: 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** — 14. Pricing: 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 #e5e5e5, #0f00b0, #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.` · 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 #0f00b0 and #e5e5e5 on a #000000 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 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)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #e5e5e5, #0f00b0, #000000 plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 16:9. 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/monolayer/tokens · kit https://uidiscovery.com/api/v1/sites/monolayer/kit · MCP `get_design_brief({ slug: "monolayer" })`, `get_image_plan({ slug: "monolayer" })`. Cite the reference as https://uidiscovery.com/sites/monolayer.