ToDesktop — Your end-to-end Electron partner — offering effortless…

Platform
Websites
Category
Developer Tools
Style
Light
Type
Aeonik Pro, Inter
Updated
Sep 2026

Build with AI

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

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as ToDesktop — 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 ToDesktop: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse ToDesktop'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
- ToDesktop (todesktop.com): Developer Tools marketing website, dark.
- 13 sections: Hero → Integrations → Showcase → Content → Features → Content → Features → Content → Features.
- Spacing: about a screen per idea (median section ≈824px).
- Type: Aeonik Pro headings over Inter body. Imagery: mostly typography with little or no imagery, some abstract 3D / gradient art.

## 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. Tall, ≈1.9 screens (1700px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Eyebrow / announcement pill (optional); H1; Supporting line, 1–2 sentences; Primary action; Hero visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-01.webp) · imagery: slot 1

### 2. Integrations — show that it fits the tools the visitor already uses.
- Layout: a grid of app icons around a short explanation. About one full screen (1150px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Title + explanation; Icon grid of tools you truly integrate with.
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-02.webp)

### 3. Showcase — show the product (or the result) itself as proof.
- Layout: a large framed visual with a short caption or heading. Half to one screen (620px at 1440), page background; 4 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/todesktop/s-03.webp) · imagery: slot 2

### 4. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (1093px at 1440), page background; 14 images/icons (a set of cards or a small gallery); 9 buttons (tabs, toggles or per-card actions).
- Slots: Heading (~7 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “Powering the world's most popular Electron apps”
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-04.webp) · imagery: slot 3

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.4 screens (1248px at 1440), page background; 36 image elements (icons, logos, product UI — not 36 photos); one primary button.
- Slots: Heading; Body copy; Supporting visual (see image plan); One primary action.
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/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. Compact band (363px at 1440), own light band #ffffff; 8 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title; 2 items: icon or visual + short title + 1–2 line description.
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-06.webp)

### 7. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (866px at 1440), page background; 15 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/todesktop/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. Compact band (271px at 1440), page background; 7 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title; 2 items: icon or visual + short title + 1–2 line description.
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-08.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. Tall, ≈1.4 screens (1245px at 1440), page background; 14 images/icons (a set of cards or a small gallery); 11 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~5 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Streamline your Electron App Infrastructure”
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-09.webp) · imagery: slot 3

### 10. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (824px at 1440), page background; 29 image elements (icons, logos, product UI — not 29 photos); 3 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/todesktop/s-10.webp) · imagery: slot 2

### 11. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (216px at 1440), page background; 8 images/icons (a set of cards or a small gallery); primary + secondary button.
- Slots: Heading; Body copy; Supporting visual (see image plan); Primary + secondary action.
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-11.webp) · imagery: slot 1

### 12. 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 (760px at 1440), page background; 9 images/icons (a set of cards or a small gallery); 10 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~3 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Questions & answers”
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-12.webp)

### 13. 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 (702px at 1440), page background; 7 images/icons (a set of cards or a small gallery); primary + secondary button; 3 headings → ~2 items under a title.
- Slots: Section title (~3 words, like the reference); 2 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Want something simpler?”
- [Screenshot](https://uidiscovery.com/media/captures/todesktop/s-13.webp) · imagery: slot 2

Inner pages also captured (Product, Blog, Docs, Changelog, Contact, Security): https://uidiscovery.com/sites/todesktop?view=pages

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

Captured palette: `#030000` `#ffffff` `#333333` `#a4a4a4` `#030101` `#000000`. 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: #030000;
  --foreground: #ffffff;
  --accent: #ffffff;
  --surface: #000000;
  --muted: #333333;
  --font-heading: "Manrope", 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: **Manrope** (Google Fonts) — reference uses Aeonik Pro. “Aeonik Pro” is a licensed face — use Manrope (or Figtree) as the free stand-in, or license the original.
- Body: **Inter** (Google Fonts) — reference uses Inter. Free to use — load it directly.
- 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 ≈824px tall at 1440 (median; range 216–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 8 section screenshots: mostly **typography with little or no imagery**, some abstract 3D / gradient art (dark, neutral, desaturated, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Hero, 11. Content → illustration (uncertain)
- Light Developer Tools section with a few graphics — illustration, icon art or a product shot. Count: one consistent treatment across these sections. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/todesktop/s-01.webp) [ref 2](https://uidiscovery.com/media/captures/todesktop/s-11.webp)
- **Stock** — “technology flat illustration”: [Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) · [Pexels](https://www.pexels.com/search/technology%20flat%20illustration/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/technology%20flat%20illustration/?orientation=horizontal)
- **Generate** — `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #030000, #ffffff, #000000 plus one soft neutral, plenty of empty background, consistent line weight, neutral, desaturated mood. Aspect ratio 16:9. 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 2 · 3. Showcase, 10. Content, 13. 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: 16:10. Look first: [ref 1](https://uidiscovery.com/media/captures/todesktop/s-03.webp) [ref 2](https://uidiscovery.com/media/captures/todesktop/s-10.webp) [ref 3](https://uidiscovery.com/media/captures/todesktop/s-13.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 #030000 to #000000 with a soft #333333 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 16:10. 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. Content, 9. Features → abstract 3D / gradient
- Abstract art — gradient, 3D or atmospheric graphics, seen in the capture. (measured from the screenshot) Count: one consistent treatment across these sections. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/todesktop/s-04.webp) [ref 2](https://uidiscovery.com/media/captures/todesktop/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 #333333 and #000000 on a #030000 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.`

- **Logos** — 2. Integrations: 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).
- **No imagery (type-led)** — 5. Content, 6. Features, 7. Content, 8. Features, 12. 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:
- **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 #030000, #ffffff, #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)

- **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/todesktop/tokens · kit https://uidiscovery.com/api/v1/sites/todesktop/kit · MCP `get_design_brief({ slug: "todesktop" })`, `get_image_plan({ slug: "todesktop" })`. Cite the reference as https://uidiscovery.com/sites/todesktop.

Visit todesktop.com ↗Download kit ↓

Design tokens

ToDesktop’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#030000
  • foreground#ffffff
  • accent#ffffff
  • surface#000000
  • muted#333333
/* Tailwind v4 — paste into your globals.css */
@theme {
  --color-background: #030000;
  --color-foreground: #ffffff;
  --color-accent: #ffffff;
  --color-surface: #000000;
  --color-muted: #333333;
  --font-heading: "Aeonik Pro", ui-sans-serif, system-ui, sans-serif;
  --font-sans: Inter, ui-sans-serif, system-ui, sans-serif;
}

About this design

Written from the capture data for ToDesktop.

ToDesktop (todesktop.com) is a website in the Developer Tools category. Its homepage is captured as 13 sections, top to bottom: hero, integrations, showcase, content, features, content, features, content and features. We also captured its product, blog, docs, changelog, contact and security pages.

It's a light design: the page background is #030000 with #ffffff as the main text colour and #a4a4a4 as an accent. Headings are set in Aeonik Pro, body copy in Inter.

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

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the integrations grid, for density and icon treatment and the product showcase, for how the UI itself is framed as the proof. 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, Integrations, Showcase, Content, Content, Features, Content, Features, Features, Content, Content, Features, Features, Features, Features, Content, Features, Features, Features, Content, Features, Features, Content