example.com

DESIGN.md

Narrative design system document — paste directly into Claude Code, Cursor, or Bolt.

---
version: alpha
name: example.com
description: "Light product system built on #eeeeee with #334488 as the primary CTA accent. Type anchored in system-ui at 24px / weight 700. Extracted automatically from https://example.com/ — rendered styles via getComputedStyle() + CSS custom properties (token-only values may not be painted)."
narrative: |
  example.com is built on a soft, near-white canvas (rgb(238, 238, 238)).
  The system uses rgb(51, 68, 136) as the accent for primary actions and brand signals.
  System-ui as the primary typeface.
  Depth comes from borders and surface contrast rather than shadows — a flat, structural elevation model.
  Motion is minimal — a few targeted transitions, no decorative animation.

colors:
  background: "#eeeeee"
  surface-1: "#eeeeee"
  surface-2: "#eeeeee"
  primary: "#334488"
  on-primary: "#ffffff"
  primary-hover: "#334488"
  hairline: "#e5e7eb"

typography:
  display-xl:
    fontFamily: "system-ui"
    fontSize: 24px
    fontWeight: 700
    lineHeight: normal
    letterSpacing: 0
  body:
    fontFamily: "system-ui"
    fontSize: 16px
    fontWeight: 400
    lineHeight: normal
    letterSpacing: 0

rounded:
  none: 0px
  xs: 4px
  sm: 8px
  md: 14px
  lg: 20px
  xl: 32px
  pill: 9999px

spacing:
  xxs: 2px
  xs: 16px
  sm: 135px
  md: 143px
  lg: 159px
  xl: 167px
  xxl: 183px

components:


extracted_at: "2026-06-14T04:37:47.620Z"
completeness: 13
scoreVersion: "v2"

---

# Design System — example.com
> Extracted automatically by Prism from https://example.com
> Date: 2026-06-14
> Viewport: Desktop 1440x900 + Mobile 390x844
> Values are extracted, not hand-written: rendered styles via getComputedStyle() + colors declared in CSS custom properties (token-only values are marked `(token)` and may not be painted).


## 0. Design DNA

**Density**: sparse  |  **Motion**: still  |  **Weight**: heavy  |  **Aesthetic**: engineering-minimal

| Dimension | Value | Signal |
|---|---|---|
| Canvas | neutral | `#eeeeee` |
| Type posture | sans-led (system-ui) | "Example Domain" |
| Color assertion | single-accent | #334488 |
| Whitespace | sparse | section rhythm 175px |
| Interaction | still | 0 keyframes, 1 transitions |
| Radius language | 8px-rounded | from token scale |

**Prism fingerprint**: `neutral-canvas · sans-display · single-accent · 8px-rounded · still-motion`

> **🤖 TL;DR for AI agents** (read this first — saves you scanning the full doc):
>
> - **Canvas**: `rgb(238, 238, 238)` is the page background. Every component composits against this.
> - **Accent**: `rgb(51, 68, 136)` for primary CTAs ONLY. Never decorative.
> - **Body type**: 16px (token: `typography.body`). Default for ALL text not in a heading role.
> - **Section rhythm**: 175px between major bands. Card padding: 159px.
> - **Default radius**: 8px on buttons/inputs. Pills (`9999px`) only for icon-buttons or status chips.
> - **Forbidden**: Do NOT introduce heavy box-shadows — this system relies on borders for separation
>
> **Before generating UI**: import this DESIGN.md, scan §2 (Color Palette) + §4 (Components) + §10 (Agent Guide). Skip §11–12 unless extending.

## 1. Visual Theme & Atmosphere

example.com sits on a off-white canvas (`#eeeeee`), a neutral foundation calibrated for sustained reading and component contrast. 

The system font stack (system-ui) trades brand voice for performance and platform familiarity. 

Body text reads in Pure Black (`#000000`) (contrast ratio 19.7:1, well above WCAG AA). **#334488** (`#334488`) provides interactive distinction without visual aggression. Shadow is absent by design — depth is conveyed through borders, spacing, and color differentiation rather than light simulation. 


**Key Characteristics:**
- Background: Off-White (`#eeeeee`)
- Accent: #334488 (`#334488`)

## 2. Color Palette & Roles

### Background & Surface
- **Off-White** (`#eeeeee`): Page background (primary)

### Text & Content
- **Pure Black** (`#000000`): Primary body text

### Accent & Interactive
- **#334488** (`#334488`): Interactive / accent

## 3. Typography Rules

### Font Families
- **Primary**: `system-ui`

### Typography Hierarchy

| Role | Font | Size | Weight | Line Height | Letter Spacing | Notes |
|------|------|------|--------|-------------|----------------|-------|
| Display Hero | system-ui | 24px | 700 | normal | normal | Main headline (h1) |
| Body | system-ui | 16px | 400 | normal | normal | Standard reading text |

### Full Font Size Scale

Sizes detected in the design (descending): `24px`, `16px`

## 4. Component Stylings


## 4b. Component Behaviors (State Matrix)

### Interaction State Narrative


*State transitions extracted via Playwright simulation — exact values in the YAML matrix below.*

```yaml
component-behaviors:
  link:
    default:
      bg: "rgba(0, 0, 0, 0)"
      fg: "rgb(51, 68, 136)"
```

**Agent usage**: Validate generated components against this matrix. If your output's `:hover` state changes properties not listed here, you are off-brand.

## 5. Layout Principles

### Layout Type
**top-nav + content**

### Grid
Single column, centered content

### Max Width
1200px

### Spacing System
Generous spacing — editorial breathing room

| Token | Value |
|-------|-------|
| xxs | 2px |
| xs | 16px |
| sm | 135px |
| md | 143px |
| base | 151px |
| lg | 159px |
| xl | 167px |
| 2xl | 175px |
| 3xl | 183px |

### Border Radius Scale
| Name | Value | Use |
|------|-------|-----|
| None | 0px | No rounding |
| Xs | 4px | Tiny corners (badges, micro elements) |
| Sm | 8px | Buttons, inputs, small elements |
| Md | 14px | Cards, containers |
| Lg | 20px | Large rounded elements, pill segments |
| Xl | 32px | Category strips, featured containers |
| Full | 9999px | Pills, avatars, circular elements |

### Shape Language

| Component | Border Radius |
|-----------|---------------|
| Page Body | `0px` |

**Shape Personality**: Sharp & Angular — No rounding. Precise, editorial, enterprise feel.


## 5b. Spacing Rhythm Names

*Named spacing tokens with explicit use cases. Use these names in YOUR code instead of raw pixels for consistency.*

| Name | Value | Use case |
|------|-------|----------|
| **hero** | `183px` | Top/bottom of full-bleed hero sections |
| **section** | `167px` | Between major bands (color change, content shift) |
| **subsection** | `159px` | Within a section, between content groups |
| **card** | `143px` | Card padding, list-item spacing |
| **compact** | `135px` | Form fields, tight clusters, badge padding |
| **micro** | `16px` | Icon-text gap, tag inner padding |

**Agent rule**: NEVER hardcode raw pixel values for spacing in generated UI. Always reference these named tokens (`spacing-rhythm.section`, etc.).

## 5c. Widget & Structure Library

Structural patterns extracted from the page DOM — these are the **blueprints** an agent should follow to reproduce the page architecture (not just CSS values).

**2/8 structural patterns detected.**

### Hero Pattern

- **Composition:** left-aligned — 
- **Viewport coverage:** 98px tall (not full-viewport)
- **Heading:** "Example Domain" — 24px left-aligned
- **Subheading:** "This domain is for use in documentation examples without needing permission. Avoid use in operations."
- **CTAs:** none detected in hero (unusual — agent should verify)
- **Clone instruction:** Reproduce the **left-aligned** layout. Use the heading font-size token at the documented size. No imagery needed for hero — text-driven.

### Footer Pattern

- **Columns:** 1
- **Links:** 1 total
- **Height:** 98px
- **Includes:** ✗ no newsletter | ✗ no social |  
- **Clone instruction:** Build a 1-column footer with ~1 links per column.

## 6. Depth & Elevation

| Level | Treatment | Use |
|-------|-----------|-----|
| Flat (Level 0) | No shadow | Page background, content blocks |

**Shadow Philosophy**: Flat design — no shadows used. Borders and spacing define structure.

## 8. Do's and Don'ts

### Do
- Use Off-White (`#eeeeee`) as the page background — it's intentionally not pure white
- Use #334488 (`#334488`) as the primary accent — it's the brand's signature interactive color
- Respect the 16px–167px spacing range — the design uses a wide scale for visual breathing room

### Don't
- Don't use pure white (`#ffffff`) as a page background — the warm tone is part of the brand identity
- Don't introduce additional saturated accent colors — the palette is intentionally controlled
- Don't over-build the footer — this design keeps it minimal (1 cols, 1 links)


## 7b. Enforceable Brand Rules

*Structured Do/Don't with reasoning and validation tests. Agents can programmatically verify generated UI.*

```yaml
rules:
  - id: brand-canvas-001
    type: do
    rule: "Always use the page background `rgb(238, 238, 238)` as the base canvas"
    why: "Every component is designed to composit against this exact tone"
    test: "document.body.style.backgroundColor === 'rgb(238, 238, 238)'"
  - id: brand-accent-001
    type: do
    rule: "Reserve `rgb(51, 68, 136)` for primary CTAs and brand-mark signals only"
    why: "Single chromatic assertion device — overuse dilutes meaning"
    test: "querySelectorAll('[style*=\"rgb(51, 68, 136)\"]').length <= 3 per fold"
  - id: brand-depth-001
    type: dont
    rule: "Do NOT introduce drop shadows on cards or sections"
    why: "Containment is achieved via borders, not elevation — adding shadows breaks the depth contract"
    test: "getComputedStyle(card).boxShadow === 'none'"
```

## 9. Responsive Behavior

### Breakpoints
| Name | Width | Key Changes |
|------|-------|-------------|
| Mobile | 640px | Single column layout |
| Tablet | 768px | 2-column grids |
| Desktop | 1024px | Full layout |
| Large Desktop | 1280px | Maximum width |

### Collapsing Strategy
- Navigation: horizontal links → hamburger menu on mobile
- Cards: multi-column → stacked vertical on mobile
- Footer: multi-column → stacked single column on mobile

### Touch Targets
- Navigation: adequate spacing between items
- Interactive elements: minimum 44px touch target recommended

### Collapsing Narrative

How the structural patterns adapt from desktop to mobile (extracted from both viewport extractions):

*No major structural differences detected between desktop and mobile widgets. The same blueprints scale rather than collapse — verify by inspecting actual mobile render.*

## 9b. Visual Tone & Photography

**Tone:** No imagery

No detectable photographic content. The site composes entirely with typography, color blocks, and minimal vector graphics. Clone strategy: lean on type hierarchy + layout rhythm rather than visual media.

**Media Format Mix:**
- *No detectable images.*

**Imagery Guidance for clones:**
- Don't add stock imagery just to "fill space" — this site's clarity comes from typographic restraint.
- Use generous whitespace, strong type hierarchy, and color blocks for visual rhythm.

## 10. Agent Prompt Guide

### Quick Reference
- Background: Off-White (`#eeeeee`)
- Primary text: Pure Black (`#000000`)
- Accent: #334488 (`#334488`)
- Border: Whitesmoke (`#e5e7eb`)
- Font: system-ui
- Body: 16px weight 400

### Example Component Prompts
- "Create a hero section on Off-White background (#eeeeee). Headline at 24px system-ui weight 700, line-height normal, color #000000."
- "Create the primary CTA button: `#334488` background, `#ffffff` text, 9999px border-radius, 11px 21px padding, 700 weight, system-ui font."
- "Build navigation: sticky on `#eeeeee`. system-ui 16px weight 400 for links."

### Iteration Guide
1. **Canvas**: Set the light canvas to Off-White (`#eeeeee`) — every component is composited against this exact base.
2. **Typography**: All type in system-ui, weight range 400–700. Never exceed 700 — heavier weights break the brand's tonal restraint.
3. **Accent**: #334488 (`#334488`) is the sole interactive color. On hover → #334488 (`#334488`). Use CSS transitions, not opacity/brightness filters.
4. **Spacing**: Use the `--ca-space-*` token scale (16px–167px). All padding, margin, and gap values are multiples from this scale — no magic numbers.
5. **Tokens**: Import from §11 CSS Export (`--ca-*` vars). Never hardcode hex values — always reference a token so theming remains consistent.

## 11. CSS Design Tokens Raw Export

*Copy-paste ready `:root {}` block — all values extracted directly from the live site.*

```css
/* Colors */
:root {
  --ca-surface-2: #eeeeee;
  --ca-primary-hover: #334488;
  --ca-on-primary: #ffffff;
  --ca-hairline: #e5e7eb;
}

/* Typography */
:root {
  --ca-font-primary: "system-ui", system-ui, sans-serif;
  --ca-text-display: 24px;
  --ca-text-body: 16px;
}

/* Spacing & Radius */
:root {
  --ca-space-xxs: 2px;
  --ca-space-xs: 16px;
  --ca-space-sm: 135px;
  --ca-space-md: 143px;
  --ca-space-base: 151px;
  --ca-space-lg: 159px;
  --ca-space-xl: 167px;
  --ca-space-2xl: 175px;
  --ca-space-3xl: 183px;
  --ca-radius-none: 0px;
  --ca-radius-xs: 4px;
  --ca-radius-sm: 8px;
  --ca-radius-md: 14px;
  --ca-radius-lg: 20px;
  --ca-radius-xl: 32px;
  --ca-radius-full: 9999px;
}
```


## 13. Page Structure Skeleton

*The actual layout the source site uses. Reproduce these sections in order to match the site structure.*

```yaml
page-skeleton:
  - section: feature-section
    tag: div
    height: 98px
    width: 864px
    layout: block
    children: 3
```

**Agent rule**: rebuild sections in this order (sorted by vertical position). Match the layout primitive (grid N-col / flex direction / block).


---
## Coverage: 13% of dimensions extracted

> Coverage measures how much of the design we could read, **not** how pixel-faithful a clone is. For fidelity, see the SSIM/structure score.

| Category | Score | Max | Detail |
|----------|-------|-----|--------|
| Colors & Palette | 4 | 25 | 3 named colors |
| Typography | 5 | 20 | 2 roles defined |
| Components | 0 | 20 | 0 specs extracted |
| Motion & Interaction | 0 | 15 | No keyframes |
| CSS Custom Properties | 0 | 10 | 0 vars |
| Responsive Breakpoints | 4 | 5 | 4 breakpoints |
| Variable Fonts | 0 | 5 | None detected |

## 12. Known Gaps & Confidence

Explicit list of what this extraction could NOT capture. Agents should not invent values for these — either skip the feature or use the documented baseline + heuristic fallback.

*Auto-detected extraction limitations — understand before building:*

- **Sparse component extraction** — fewer than 5 component types detected. Highly dynamic sections (modals, datepickers, carousels) require interaction to render and are not captured in a static pass.

| Category | What's missing | Fallback strategy |
|----------|----------------|-------------------|
| **Photography** | No photographic content detected on this page | Don't add stock imagery; clarity comes from type + color blocks |
| **Keyframe animations** | No @keyframes declarations found (transitions only) | Use CSS transitions for state changes; avoid complex scroll-based animations |
| **Dark mode** | No dark-mode CSS variables or media queries detected | Light mode is canonical; do not generate dark-mode variants unless explicitly requested |
| **Form inputs** | No text input fields detected on this page | Use the documented border-radius + accent border on focus; 12-16px padding inside |
| **Design tokens** | Only 0 CSS custom properties (low signal for semantic naming) | Color names are nearest-neighbor approximations; verify against brand guidelines if available |

### Per-section confidence

| Section | Confidence | Reason |
|---------|------------|--------|
| §1 Visual Theme | High | Body bg extracted via getComputedStyle() |
| §2 Colors | Low | 0 CSS vars (semantic naming requires ≥20 for high) |
| §3 Typography | Low | 2 typography roles inferred |
| §4 Components | Low | 0 component variants captured |
| §7 Motion | Medium | Transitions only |
| §8 Do's/Don'ts | Medium | 6 rules generated; design-decisions.json has evidence per rule |
| §9 Responsive | High | 4 breakpoints detected |
| §9b Photography | Low | 0 images, hero not detected |

## 11.2 Measured Reality (CDP Engine)

Captured directly from Chrome's engine across **all 11 rendered nodes** — not a sample. These are the values the page *actually paints*, weighted by how often they appear.

### Measured Design Scale
**Type scale by usage** (× = paint count): `16px`×8 · `24px`×2

**Weights** (× = paint count): `400`×8 · `700`×2

### Provenance — measured styles on key elements
Read from the live CSSOM (includes runtime-injected CSS). This is *what actually styles the page*, by element:

```css
body { background:#eee; font-family:system-ui,sans-serif; background-color:rgb(238, 238, 238) }
h1 { font-size:1.5em }
a { color:#348 }
```

> Selectors normalised to their semantic element — source class names are often build-hashed (`.bgDIHX`) and not reusable. The declarations + CSS vars are the transferable part.

---
*Generated by Prism — automated Playwright extraction + design analysis.*
*Source: https://example.com | 2026-06-14T04:37:47.625Z*
*Values extracted via getComputedStyle() (rendered) + CSS custom properties (tokens, marked `(token)`). Token-only values may not be painted — verify against the live site before shipping.*