Vastspace — Building Next-Generation Space Infrastructure

Platform
Websites
Category
Developer Tools
Style
Light, Minimal, Award winner
Type
Owners, Owners Text
Updated
Sep 2026

Build with AI

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

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Vastspace — 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 Vastspace: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Vastspace'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
- Vastspace (vastspace.com): Developer Tools marketing website, light, minimal, award winner.
- 7 sections: Hero → Features → Content → Blog → Features → Footer.
- Spacing: about a screen per idea (median section ≈900px).
- Hero headline: 4 words — short and punchy; keep yours under ~9.
- Type: one family (Owners). 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 (900px at 1440), own dark band #2a2c2f; 9 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Eyebrow / announcement pill (optional); H1 (~4 words, like the reference); Supporting line, 1–2 sentences; Primary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Building next-generation space infrastructure”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/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. Half to one screen (720px at 1440), own light band #b3aba3; 4 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~14 words, like the reference); 4 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Vast is developing next-generation space stations and space infrastructure…”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/s-02.webp)

### 3. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (900px at 1440), own light band #fdfcf4; 6 images/icons (a set of cards or a small gallery); one primary button.
- Slots: Heading (~3 words, like the reference); Body copy; Supporting visual (see image plan); One primary action.
- Topic (tone/length only — never reuse): “Haven-1”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/s-03.webp)

### 4. Content — supporting content that deepens one idea.
- Layout: text + media block. About one full screen (1062px at 1440), own light band #fdfcf4; 92 image elements (icons, logos, product UI — not 92 photos); primary + secondary button.
- Slots: Heading (~4 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “Haven-1 hardware development progress”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/s-04.webp) · imagery: slot 2

### 5. Blog — signal an active, credible team through recent writing.
- Layout: 3-up card grid: image, title, meta. Tall, ≈1.9 screens (1700px at 1440), own light band #ece8e3; 6 images/icons (a set of cards or a small gallery); one primary button.
- Slots: Title + “All posts” link; 3 post cards: cover image, title, date/author.
- Topic (tone/length only — never reuse): “Updates”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/s-05.webp) · imagery: slot 3

### 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. About one full screen (856px at 1440), own light band #ece8e3; 104 image elements (icons, logos, product UI — not 104 photos); primary + secondary button.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “In the press”
- [Screenshot](https://uidiscovery.com/media/captures/vastspace/s-06.webp)

### 7. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. About one full screen (779px at 1440), own dark band #000000; 6 images/icons (a set of cards or a small gallery); inline form (2 fields, e.g. email capture), 5 buttons (tabs, toggles or per-card actions), 26 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/vastspace/s-07.webp)

Inner pages also captured (About, Sign up, Log in, Docs, Changelog, Careers, Contact, Security): https://uidiscovery.com/sites/vastspace?view=pages

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

Captured palette: `#ffffff` `#2a2c2f` `#ece8e3` `#fdfcf4` `#b3aba3` `#000000`. Section bands top→bottom: `#2a2c2f` → `#b3aba3` → `#fdfcf4` → `#ece8e3` → `#000000`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, neutral, desaturated) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #ffffff;
  --foreground: #000000;
  --accent: #000000;
  --surface: #fdfcf4;
  --muted: #b3aba3;
  --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 Owners. “Owners” 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 ≈900px tall at 1440 (median; range 720–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 4 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; expressive layout and motion are part of the appeal — study the scroll video, but keep motion subtle and respect prefers-reduced-motion. 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 4 section screenshots: mostly **typography with little or no imagery**, some photography (light, neutral, desaturated, Developer Tools). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Hero → 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 ~9 in one consistent style. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/vastspace/s-01.webp)
- **Stock** — “abstract gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20gradient%203d/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20gradient%203d/?orientation=horizontal)
- **Generate** — `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #b3aba3 and #fdfcf4 on a #ffffff background. Lighting: soft natural daylight, airy and high-key; neutral, desaturated 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.`

### Slot 2 · 4. Content → product UI (uncertain)
- Developer Tools content with 92 image elements — most likely product UI screenshots/mockups plus icons. Count: 1–3 key visuals; the rest are icons/avatars. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/vastspace/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 light gradient from #ffffff to #fdfcf4 with a soft #b3aba3 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: soft natural daylight, airy and high-key. Aspect ratio 4:5. 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 · 5. Blog → photography
- Photography, seen in the capture (people). (measured from the screenshot) Count: a set of ~6 in one consistent style. Aspect: 3:2. Look first: [ref 1](https://uidiscovery.com/media/captures/vastspace/s-05.webp)
- **Stock** — “3d glass shapes render editorial”: [Unsplash](https://unsplash.com/s/photos/3d-glass-shapes-render-editorial?orientation=landscape) · [Pexels](https://www.pexels.com/search/3d%20glass%20shapes%20render%20editorial/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/3d%20glass%20shapes%20render%20editorial/?orientation=horizontal)
- **Generate** — `Photograph: 3d glass shapes render editorial. Composition: editorial crop with one clear focal point. Lighting: soft natural daylight, airy and high-key. Neutral, desaturated colour grade that sits on #ece8e3, #000000, #fdfcf4. 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.`

- **No imagery (type-led)** — 2. Features, 3. Content, 6. 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** — 7. 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:
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #2a2c2f, #000000, #fdfcf4 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.` · 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/vastspace/tokens · kit https://uidiscovery.com/api/v1/sites/vastspace/kit · MCP `get_design_brief({ slug: "vastspace" })`, `get_image_plan({ slug: "vastspace" })`. Cite the reference as https://uidiscovery.com/sites/vastspace.

Visit vastspace.com ↗Download kit ↓

40 sections found. 0 selected for comparison.

About this design

Written from the capture data for Vastspace.

Vastspace (vastspace.com) is a website in the Developer Tools category. Its homepage is captured as 7 sections, top to bottom: hero, features, content, blog, features and footer. We also captured its about, sign up, log in, docs, changelog and careers pages, plus 2 more. The hero leads with “Building next-generation space infrastructure”.

It's a light design: the page background is #ffffff with #2a2c2f as the main text colour and #b3aba3 as an accent. Headings are set in Owners, body copy in Owners Text.

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

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 blog teaser, for card anatomy and metadata. 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, Content, Content, Blog, Features, Footer, Content, About, Features, Team, Content, Content, Content, Blog, Content, Content, Content, Blog, Content, Features, Features, Features, Features, Content, Content, Content, Features, Features, Content, Statement, Content, Features, Features, Features, About, Features, Content, Features, Content