Storybook — Frontend workshop for UI development

Platform
Websites
Category
Developer Tools
Style
Light
Type
Nunito Sans
Updated
Sep 2026

Build with AI

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

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

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

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

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Storybook — 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 Storybook: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Storybook'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
- Storybook (storybook.js.org): Developer Tools marketing website, light.
- 6 sections: Hero → Showcase → Features → Content → Statement.
- Spacing: long, content-rich sections (median ≈1622px tall at 1440).
- Hero headline: 5 words — short and punchy; keep yours under ~9.
- Type: one family (Nunito Sans). Imagery: mostly product UI screenshots/mockups, 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. Tall, ≈1.8 screens (1622px at 1440), own dark band #0d1026; 83 image elements (icons, logos, product UI — not 83 photos); 5 buttons (tabs, toggles or per-card actions).
- Slots: Eyebrow / announcement pill (optional); H1 (~5 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Build, test & document components”
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-01.webp) · imagery: slot 1

### 2. Showcase — show the product (or the result) itself as proof.
- Layout: a large framed visual with a short caption or heading. Tall, ≈1.9 screens (1700px at 1440), own dark band #0d1026; 47 image elements (icons, logos, product UI — not 47 photos); 16 links (link lists / navigation).
- Slots: Heading (~4 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Develop durable user interfaces”
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-02.webp) · imagery: slot 2

### 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. Tall, ≈1.6 screens (1397px at 1440), own dark band #0d1026; 13 images/icons (a set of cards or a small gallery); 7 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~8 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Test UIs with less effort and no flake”
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-03.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. Tall, ≈1.6 screens (1397px at 1440), own dark band #0d1026; 11 images/icons (a set of cards or a small gallery); 5 buttons (tabs, toggles or per-card actions).
- Slots: Section title (~7 words, like the reference); 9 items: icon or visual + short title + 1–2 line description; Primary + secondary action.
- Topic (tone/length only — never reuse): “Document UI for your team to reuse”
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-04.webp) · imagery: slot 2

### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Tall, ≈1.8 screens (1600px at 1440), own dark band #0d1026; 20 image elements (icons, logos, product UI — not 20 photos); 4 buttons (tabs, toggles or per-card actions).
- Slots: Heading (~6 words, like the reference); Body copy; Supporting visual (see image plan); Primary + secondary action.
- Topic (tone/length only — never reuse): “Share how the UI actually works”
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-05.webp) · imagery: slot 2

### 6. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Tall, ≈1.9 screens (1700px at 1440), own dark band #0d1026; no images (type-led); no interactive controls.
- Slots: Heading; Body copy.
- [Screenshot](https://uidiscovery.com/media/captures/storybook/s-06.webp) · imagery: slot 3

Inner pages also captured (Customers, About, Sign up, Blog, Docs, Changelog): https://uidiscovery.com/sites/storybook?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#ffffff` | page background | — |
| foreground | `#0d1026` | body text, headings | 18.8:1 |
| accent | `#1778e9` | primary buttons, links, highlights — sparingly | 4.3:1 (large text / UI only) |
| surface | `#ffffff` | cards, inputs, alternate bands | text on it 18.8:1 |
| muted | `#0d1026` | secondary text, borders | 18.8:1 |

Captured palette: `#ffffff` `#0d1026` `#1778e9`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, cool) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #ffffff;
  --foreground: #0d1026;
  --accent: #1778e9;
  --surface: #ffffff;
  --muted: #0d1026;
  --font-heading: "Nunito Sans", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Nunito Sans", 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: **Nunito Sans** (Google Fonts) — reference uses Nunito Sans. Free to use — load it directly.
- 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 ≈1622px tall at 1440 (median; range 1397–1700px, captures cap at 1700px) — long, content-rich chapters. Start with 96–128px 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. 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

Best guess: mostly **product UI screenshots/mockups**, some photography (light, cool, Developer Tools). Inferred from element counts, colours and industry — not from the pixels — so open the linked screenshots and match the real style before sourcing anything.

### Slot 1 · 1. Hero → photography
- Photography, seen in the capture (people, adult). (measured from the screenshot) Count: 1–3 key visuals; the rest are icons/avatars. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/storybook/s-01.webp)
- **Stock** — “abstract gradient mesh”: [Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20gradient%20mesh/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20gradient%20mesh/?orientation=horizontal)
- **Generate** — `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Cool colour grade that sits on #0d1026, #1778e9, #ffffff. 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 · 2. Showcase, 3. Features, 4. Features, 5. Content → 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/storybook/s-02.webp) [ref 2](https://uidiscovery.com/media/captures/storybook/s-03.webp) [ref 3](https://uidiscovery.com/media/captures/storybook/s-04.webp) [ref 4](https://uidiscovery.com/media/captures/storybook/s-05.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 #ffffff with a soft #1778e9 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 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 · 6. Statement → photography
- Photography, seen in the capture (people, adult). (measured from the screenshot) Count: 1. Aspect: 4:5. Look first: [ref 1](https://uidiscovery.com/media/captures/storybook/s-06.webp)
- **Stock** — “minimal desk with laptop close up”: [Unsplash](https://unsplash.com/s/photos/minimal-desk-with-laptop-close-up?orientation=portrait) · [Pexels](https://www.pexels.com/search/minimal%20desk%20with%20laptop%20close%20up/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/minimal%20desk%20with%20laptop%20close%20up/?orientation=vertical)
- **Generate** — `Photograph: minimal desk with laptop close up. Composition: simple composition with one focal point. Lighting: soft natural daylight, airy and high-key. Cool colour grade that sits on #0d1026, #1778e9, #ffffff. 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.`


### 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 #1778e9 and #0d1026 on a #ffffff background. Lighting: soft natural daylight, airy and high-key; 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 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 #0d1026, #1778e9, #ffffff 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/storybook/tokens · kit https://uidiscovery.com/api/v1/sites/storybook/kit · MCP `get_design_brief({ slug: "storybook" })`, `get_image_plan({ slug: "storybook" })`. Cite the reference as https://uidiscovery.com/sites/storybook.

Visit storybook.js.org ↗Download kit ↓
storybook.js.org

About this design

Written from the capture data for Storybook.

Storybook (storybook.js.org) is a website in the Developer Tools category. Its homepage is captured as 6 sections, top to bottom: hero, showcase, features, content and statement. We also captured its customers, about, sign up, blog, docs and changelog pages. The hero leads with “Build, test & document components”.

It's a light design: the page background is #ffffff with #0d1026 as the main text colour and #1778e9 as an accent. Headings are set in Nunito Sans, which it also uses for body copy.

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

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