---
version: alpha
name: ollama.com
description: "Light product system built on #ffffff with #262626 as the primary CTA accent. Type anchored in SF Pro Rounded at 36px / weight 500. Extracted automatically from https://ollama.com/ — rendered styles via getComputedStyle() + CSS custom properties (token-only values may not be painted)."
narrative: |
  ollama.com is built on a pure-white canvas (rgb(255, 255, 255)).
  The system uses rgb(38, 38, 38) as the singular interactive color.
  Fully-rounded CTAs (9999px) signal a friendly, tactile interaction model alongside SF Pro Rounded 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: "#ffffff"
  surface-1: "#ffffff"
  surface-2: "#f5f5f5"
  ink-muted: "#262626"
  ink-subtle: "#262626"
  primary: "#262626"
  on-primary: "#ffffff"
  primary-hover: "#f87171"

typography:
  display-xl:
    fontFamily: "SF Pro Rounded, 'SF Pro Display', system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif"
    fontSize: 36px
    fontWeight: 500
    lineHeight: 1.11
    letterSpacing: 0
  body:
    fontFamily: "ui-sans-serif, Georgia, 'Times New Roman', serif"
    fontSize: 16px
    fontWeight: 400
    lineHeight: 1.5
    letterSpacing: 0
  button:
    fontFamily: "ui-sans-serif, Georgia, 'Times New Roman', serif"
    fontSize: 18px
    fontWeight: 400
    lineHeight: 1.56
    letterSpacing: 0
  mono:
    fontFamily: "ui-sans-serif, Georgia, 'Times New Roman', serif"
    fontSize: 14px
    fontWeight: 400
    lineHeight: 1.43
    letterSpacing: 0

rounded:
  none: 0px
  xs: 12px
  sm: 16px
  md: 9999px
  lg: 10007px
  xl: 10015px
  pill: 9999px

spacing:
  xxs: 2px
  xs: 4px
  sm: 9px
  md: 10px
  lg: 32px
  xl: 48px
  xxl: 136px

components:
  button-ghost:
    backgroundColor: "transparent"
    textColor: "#737373"
    typography: "{typography.mono}"
    rounded: "{rounded.none}"
    padding: 4px 10px
  button-pill:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.button}"
    rounded: "{rounded.md}"
    padding: 6px 16px
  button-pill-2:
    backgroundColor: "{colors.primary}"
    textColor: "{colors.on-primary}"
    typography: "{typography.button}"
    rounded: "{rounded.md}"
    padding: 12px 32px
  code-block-inline-code--pre:
    backgroundColor: "#000000"
    textColor: "#000000"
    typography: "{typography.mono}"
    rounded: "{rounded.xs}"

extracted_at: "2026-06-11T05:01:54.939Z"
completeness: 62
scoreVersion: "v2"

---

# Design System — ollama.com
> Extracted automatically by Prism from https://ollama.com
> Date: 2026-06-11
> 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**: light  |  **Aesthetic**: soft-rounded

| Dimension | Value | Signal |
|---|---|---|
| Canvas | neutral | `#ffffff` |
| Type posture | sans-led (SF Pro Rounded) | "Automate your work" |
| Color assertion | dual-accent | #262626 |
| Whitespace | sparse | section rhythm 112px |
| Interaction | still | 1 keyframes, 2 transitions |
| Radius language | soft-pill | from token scale |

**Prism fingerprint**: `neutral-canvas · sans-display · dual-accent · soft-pill · still-motion`

> **🤖 TL;DR for AI agents** (read this first — saves you scanning the full doc):
>
> - **Canvas**: `rgb(255, 255, 255)` is the page background. Every component composits against this.
> - **Accent**: `rgb(38, 38, 38)` for primary CTAs ONLY. Never decorative.
> - **Body type**: 16px (token: `typography.body`). Default for ALL text not in a heading role.
> - **Section rhythm**: 112px between major bands. Card padding: 32px.
> - **Default radius**: 16px 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

ollama.com uses a pure-white canvas (`#ffffff`), letting typography, color and imagery carry the visual weight. 

Typography is anchored in **SF Pro Rounded**. 

Body text reads in Pure Black (`#000000`) (contrast ratio 21.0:1, well above WCAG AA). **Near-Black** (`#262626`) provides interactive distinction without visual aggression. Shadow is absent by design — depth is conveyed through borders, spacing, and color differentiation rather than light simulation. 
Border radius varies from pill-shaped (fully rounded) to moderately rounded elements, creating visual rhythm. Motion design uses smooth easing curves for polished state transitions. 

**Key Characteristics:**
- Background: Pure White (`#ffffff`)
- Primary typeface: ui-sans-serif
- Accent: Near-Black (`#262626`)
- Display: 36px weight 500

## 2. Color Palette & Roles

### Background & Surface
- **Pure White** (`#ffffff`): Page background (primary)
- **Whitesmoke** (`#e5e7eb`): Surface / elevated background
- **Off-White** (`#f5f5f5`): Surface / elevated background
- **Whitesmoke** (`#e5e5e5`): Surface / elevated background

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

### Accent & Interactive
- **Slate Gray** (`#6b7280`): Interactive / accent
- **Coral** (`#f87171`): Interactive / accent
- **Gold** (`#facc15`): Interactive / accent
- **#4ade80** (`#4ade80`): Interactive / accent
- **M Tricolor Blue** (`#2563eb`): Interactive / accent

### Border & Divider
- **Light Grey** (`#d4d4d4`): Borders / dividers

### Full Extracted Palette
**15 colors rendered on the page**. (12 categorized above + 3 additional below.)
Rendered values are read via `getComputedStyle()`; token values come from CSS variable declarations. Third-party logo colors are filtered out.

- `#737373` — Slate Grey
- `#a3a3a3` — Grey
- `#525252` — Charcoal

### CSS Custom Properties (Design Tokens)

**Shadow Token**
- `--tw-ring-offset-shadow`: `0 0 #0000`
- `--tw-ring-shadow`: `0 0 #0000`
- `--tw-shadow`: `0 0 #0000`
- `--tw-shadow-colored`: `0 0 #0000`

**Spacing Token**
- `--tw-numeric-spacing`: ``
- `--tw-border-spacing-x`: `0`
- `--tw-border-spacing-y`: `0`

**Other tokens**
- `--tw-ring-color`: `#3b82f680`
- `--tw-ring-offset-color`: `#fff`
- `--tw-bg-opacity`: `1`

## 3. Typography Rules

### Font Families
- **Primary**: `ui-sans-serif`
- **Secondary**: `SF Pro Rounded`
- **Font 3**: `ui-monospace`

### Typography Hierarchy

| Role | Font | Size | Weight | Line Height | Letter Spacing | Notes |
|------|------|------|--------|-------------|----------------|-------|
| Display Hero | SF Pro Rounded | 36px | 500 | 1.11 | normal | Main headline (h1) |
| Button Large | ui-sans-serif | 18px | 400 | 1.56 | normal | Button label (18px) |
| Button Large | ui-sans-serif | 18px | 500 | 1.56 | normal | Button label (18px) |
| Body | ui-sans-serif | 16px | 400 | 1.5 | normal | Standard reading text |
| Button Large | ui-monospace | 16px | 400 | 1.5 | normal | Button label (16px) |
| Button | ui-monospace | 14px | 400 | 0px | normal | Button label (14px) |
| Input | ui-sans-serif | 14px | 400 | 1.43 | normal | Form input (14px) |

### Full Font Size Scale

Sizes detected in the design (descending): `36px`, `30px`, `24px`, `20px`, `18px`, `16px`, `14px`, `12px`

> 4 size(s) detected outside the sampled hierarchy (30px, 24px, 20px, 12px). These appear on elements not in the sampled set — likely additional display sizes, marketing-section overrides, or third-party-widget styles.

## 4. Component Stylings

### Buttons

**Ghost**
- Background: `transparent`
- Text: `#737373`
- Padding: 4px 10px
- Radius: 0px
- Font: 14px weight 400
- Use: Subtle action, toolbar, nav button
- Focus: color: `rgb(111, 111, 111)`, outline: `rgba(0, 0, 0, 0) solid 2px`

**Pill**
- Background: `#262626` `{colors.primary}`
- Text: `#ffffff` `{colors.on-primary}`
- Padding: 6px 16px
- Radius: 9999px
- Font: 18px weight 400
- Use: Status pills, tags, chips
- Focus: color: `rgb(111, 111, 111)`, outline: `rgba(0, 0, 0, 0) solid 2px`

**Pill**
- Background: `#262626` `{colors.primary}`
- Text: `#ffffff` `{colors.on-primary}`
- Padding: 12px 32px
- Radius: 9999px
- Font: 18px weight 500
- Use: Status pills, tags, chips
- Focus: color: `rgb(111, 111, 111)`, outline: `rgba(0, 0, 0, 0) solid 2px`

### Code Blocks

**Inline Code / Pre**
- Background: `rgba(0, 0, 0, 0.05)`
- Text: `#000000`
- Padding: 0px
- Radius: 12px
- Border: 1px solid rgb(245, 245, 245)
- Font: 14px weight 400 — ui-monospace
- Use: Code samples, CLI commands, syntax highlighting blocks


## 4b. Component Behaviors (State Matrix)

### Interaction State Narrative

- **Button**:
  - **focus:** text #737373 → #6f6f6f

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

```yaml
component-behaviors:
  button:
    default:
      bg: "rgba(0, 0, 0, 0)"
      fg: "rgb(115, 115, 115)"
    focus:
      bg: "transparent"
      fg: "rgb(111, 111, 111)"
  link:
    default:
      bg: "rgba(0, 0, 0, 0)"
      fg: "rgb(0, 0, 0)"
  navLink:
    default:
      bg: "rgba(0, 0, 0, 0)"
      fg: "rgb(0, 0, 0)"
  footerLink:
    default:
      bg: "rgba(0, 0, 0, 0)"
      fg: "rgb(115, 115, 115)"
    hover:
      bg: "transparent"
      fg: "inherit"
```

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


## 4c. Component Vocabulary (Closed System)

*This brand uses ONLY the following component vocabulary. Introducing new variants without justification breaks the system's tonal coherence.*

### Buttons
- **2 shape(s)** in this system: `Ghost`, `Pill`
- **DO NOT introduce new buttons variants** without justification

### Code Blocks
- **1 shape(s)** in this system: `Inline Code / Pre`
- **DO NOT introduce new code blocks variants** without justification

## 5. Layout Principles

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

### Grid
Flexbox column

### Max Width
768px

### Spacing System
Generous spacing — editorial breathing room

| Token | Value |
|-------|-------|
| xxs | 2px |
| xs | 4px |
| sm | 9px |
| md | 10px |
| base | 24px |
| lg | 32px |
| xl | 48px |
| 2xl | 112px |
| 3xl | 136px |

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

### Shape Language

| Component | Border Radius |
|-----------|---------------|
| Buttons | `0px` |
| Code Blocks | `12px` |
| Page Body | `0px` |
| Navigation | `0px` |

**Shape Personality**: Moderate Rounding — Medium corners (4–12px). Modern SaaS standard, neither sharp nor pill.

**Full Radius Spectrum**: 12px, 16px, full/pill (from `allBorderRadii` scan)


## 5b. Spacing Rhythm Names

**Measured section padding**: bands use ~136px internal vertical padding (up to 136px) — **very airy / premium**. (Distinct from the gap *between* sections above.) Reproduce this generous vertical breathing room; cramped spacing is the #1 tell of a cheap clone.

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

| Name | Value | Use case |
|------|-------|----------|
| **hero** | `136px` | Top/bottom of full-bleed hero sections |
| **section** | `48px` | Between major bands (color change, content shift) |
| **subsection** | `32px` | Within a section, between content groups |
| **card** | `10px` | Card padding, list-item spacing |
| **compact** | `9px` | Form fields, tight clusters, badge padding |
| **micro** | `4px` | 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).

**4/8 structural patterns detected.**

### Hero Pattern

- **Composition:** centered — Centered composition — heading + subheading + CTAs stacked vertically, content centered horizontally. Common for SaaS marketing pages.
- **Viewport coverage:** 502px tall (not full-viewport)
- **Heading:** "The easiest way to build with open models" — 36px center-aligned
- **Subheading:** "paste this in PowerShell, or download Ollama"
- **Media:** present, positioned top
- **CTAs:** none detected in hero (unusual — agent should verify)
- **Clone instruction:** Reproduce the **centered** layout. Use the heading font-size token at the documented size. Place media top of text.

### Navigation Pattern

- **Position:** static (scrolls with page)
- **Layout:** logo-left-links-left — Logo and links both on the left (CTAs typically right)
- **Height:** 63px
- **Logo:** ✓ present
- **Nav links:** 3 primary items
- **CTAs in nav:** 2
- **Clone instruction:** Build a static logo left links left navigation. Reserve 2 slots for primary CTAs.

### Pricing Table Pattern

- **Tier count:** 2 pricing tiers
- **Layout:** side-by-side (horizontal comparison)
- **Columns (desktop):** 2-up
- **Feature list:** ✓ (median ~2 feature points per tier)
- **Clone instruction:** Build a 2-column side-by-side pricing comparison.

### Footer Pattern

- **Columns:** 1
- **Links:** 9 total
- **Height:** 44px
- **Includes:** ✗ no newsletter | ✓ social icons |  ✓ copyright
- **Clone instruction:** Build a 1-column footer with ~9 links per column, social media links, and a copyright line.

## 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.

## 7. Motion & Interaction

### Dominant Easing Curves

| Curve | Semantic Name |
|-------|---------------|
| `cubic-bezier(0.4,0,0.2,1)` | Material Standard — Balanced |

### Duration Scale

| Value | Tier | Typical Use |
|-------|------|-------------|
| `150ms` | Fast | Hover states, micro-interactions |

### Copy-Paste Transition Snippets

**Color / Background**
```css
transition: color 0.15s cubic-bezier(0.4, 0, 0.2, 1), background-color 0.15s cubic-bezier(0.4, 0, 0.2, 1), border-color 0.15s cub...;
```

### Keyframe Animation Catalog

| Animation Name | Type | Animated Props | Use Hint |
|----------------|------|----------------|----------|
| `spin` | Rotate / Spin | transform | Loading indicator |

### Motion Fingerprint

- **Speed Character**: Balanced Pacing (median duration: `150ms`)
- **Dominant Easing**: custom cubic-bezier curves
- **Animation Library**: 1 unique animation (1 total including variants)

> This design moves with balanced pacing timing using custom cubic-bezier curves, creating a UI that feels natural and fluid.

## 8. Do's and Don'ts

### Do
- Use ui-sans-serif as the primary typeface — it defines the brand personality
- Keep font weights between 400-500 — the system uses a narrow weight range for subtle hierarchy
- Use full-pill radius (9999px) only for specific elements (avatars, pills, toggles)
- Use Near-Black (`#262626`) as the primary accent — it's the brand's signature interactive color
- Use pill-shaped radius (9999px) for primary CTA buttons — the brand uses fully-rounded, pill CTAs
- Maintain nav height at 63.25px — consistent vertical space for the navigation bar
- Respect the 4px–48px spacing range — the design uses a wide scale for visual breathing room
- Place 2 pricing tiers side-by-side on desktop — direct comparison is the value prop

### Don't
- Don't substitute with generic sans-serif or serif — the custom font carries the brand
- Don't use weight 700 (bold) or above — 500 is the maximum weight in this system
- Don't apply pill radius on rectangular buttons or cards — it's reserved for specific interactive elements
- Don't introduce additional saturated accent colors — the palette is intentionally controlled
- Don't use rectangular buttons for primary actions — the rounded pill shape is the brand standard
- Don't collapse or hide the nav on scroll without an explicit scroll-triggered animation — the design uses fixed nav presence
- Don't make the nav sticky — this design lets it scroll away to maximize content focus
- Don't over-build the footer — this design keeps it minimal (1 cols, 9 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(255, 255, 255)` as the base canvas"
    why: "Every component is designed to composit against this exact tone"
    test: "document.body.style.backgroundColor === 'rgb(255, 255, 255)'"
  - id: brand-accent-001
    type: do
    rule: "Reserve `rgb(38, 38, 38)` for primary CTAs and brand-mark signals only"
    why: "Single chromatic assertion device — overuse dilutes meaning"
    test: "querySelectorAll('[style*=\"rgb(38, 38, 38)\"]').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 Large | 640px | Expanded mobile layout |
| Tablet | 768px | Multi-column grids begin |
| Tablet | 850px | Multi-column grids begin |
| Tablet | 1024px | Multi-column grids begin |
| Desktop | 1280px | Full feature layout |

### Token Diff — Desktop vs Mobile

| Element | Property | Desktop | Mobile |
|---------|----------|---------|--------|
| heading | font-size | `36px` | `30px` |
| heading | line-height | `40px` | `36px` |
| button | width | `36px` | `auto` |

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

### Touch Targets
- Buttons: 4px 10px padding
- 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):

- **Hero CTAs:** 0 on desktop → 1 on mobile.
- **Navigation collapses to hamburger** — 3 links visible on desktop, 0 on mobile (the rest hide behind a menu toggle).
- **Nav CTAs reduced** on mobile (2 → 0) — the design prioritizes content over conversion buttons at small sizes.
- **Pricing collapses to vertical stack** — desktop comparison becomes scrollable tier-by-tier on mobile.

## 9b. Visual Tone & Photography

**Tone:** Mixed photography + illustration

A balanced mix of photographic content and vector graphics. Photos likely carry product/lifestyle context while SVG handles icons, logos, and decorative accents.

**Canonical Brand Image (OG):**
- https://ollama.com/public/og.png (1200×628px)
  *This is the image shown when the site is shared on social media — represents the brand visual essence.*

**Hero Image (above-fold dominant visual):**
- Aspect: 1.33:1 (landscape)
- Rendered size: 288×216px
- Alt text: "OpenClaw"
- *Use this aspect ratio + composition for your clone's hero — mimicking the proportion preserves the visual hierarchy.*

**Aspect Ratio Distribution:**
- Landscape (1.15–2.3): 1 (100%)
- Portrait (<0.87): 0 (0%)
- Square (0.87–1.15): 0 (0%)

**Media Format Mix:**
- PNG: 1 (logos, transparent UI elements, mockups)
- SVG: 1 (icons, illustrations, decorative geometry)

**Average rendered image size:** 288×216px
**Above-fold image count:** 1 / 1

**Decorative Patterns Detected:**
- 1 large decorative SVG shape (≥200×200px, non-icon) — likely blob/illustration accents

**Clone instruction for decorative work:** Decorative details are subtle — don't over-style; the design relies on restraint.

**Imagery Guidance for clones:**
- Mix photography and illustration intentionally: photos for product/context, vectors for icons + decorative accents.
- Respect the format split — replacing JPGs with illustrations (or vice versa) will shift the brand tone.

## 10. Agent Prompt Guide

### Quick Reference
- Background: Pure White (`#ffffff`)
- Primary text: Pure Black (`#000000`)
- Accent: Near-Black (`#262626`)
- Border: Translucent Pure Black (5%) (`rgba(0, 0, 0, 0.05)`)
- Font: ui-sans-serif
- Body: 16px weight 400

### Example Component Prompts
- "Create a hero section on Pure White background (#ffffff). Headline at 36px ui-sans-serif weight 500, line-height 1.11, color #000000."
- "Create the primary CTA button: `#262626` background, `#737373` text, 9999px border-radius, 4px 10px padding, 500 weight, ui-sans-serif font."
- "Build navigation: static on `#ffffff`. ui-sans-serif 16px weight 400 for links."

### Iteration Guide
1. **Canvas**: Set the light canvas to Pure White (`#ffffff`) — every component is composited against this exact base.
2. **Typography**: All type in ui-sans-serif, weight range 400–500. Never exceed 500 — heavier weights break the brand's tonal restraint.
3. **Accent**: Near-Black (`#262626`) is the sole interactive color. On hover → Coral (`#f87171`). Use CSS transitions, not opacity/brightness filters.
4. **Motion**: All transitions use `cubic-bezier(0.4,0,0.2,1)`. Never use linear for UI transitions — preserve the brand's easing personality.
5. **Shape**: CTAs at `9999px`. Apply border-radius from the extracted scale only — don't invent intermediate values.
6. **Spacing**: Use the `--ca-space-*` token scale (4px–48px). All padding, margin, and gap values are multiples from this scale — no magic numbers.
7. **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-on-primary: #ffffff;
  --ca-surface-2: #f5f5f5;
  --ca-primary: #262626;
  --ca-primary-hover: #f87171;
}

/* Typography */
:root {
  --ca-font-primary: "SF Pro Rounded", system-ui, sans-serif;
  --ca-text-display: 36px;
  --ca-text-body: 16px;
  --ca-text-button: 18px;
  --ca-text-mono: 14px;
}

/* Spacing & Radius */
:root {
  --ca-space-xxs: 2px;
  --ca-space-xs: 4px;
  --ca-space-sm: 9px;
  --ca-space-md: 10px;
  --ca-space-base: 24px;
  --ca-space-lg: 32px;
  --ca-space-xl: 48px;
  --ca-space-2xl: 112px;
  --ca-space-3xl: 136px;
  --ca-radius-none: 0px;
  --ca-radius-xs: 12px;
  --ca-radius-sm: 16px;
  --ca-radius-md: 9999px;
  --ca-radius-lg: 10007px;
  --ca-radius-xl: 10015px;
  --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: main
    classes: ["mx-auto", "flex", "w-full", "max-w-3xl"]
    height: 806px
    width: 768px
    layout: flex-column justify=normal
    children: 1
    vertical-padding: ~136px (airy)
    padding: "112px 24px 160px"
  - section: feature-section
    tag: section
    classes: ["flex", "flex-col", "items-center", "text-center"]
    height: 502px
    width: 720px
    layout: flex-column justify=normal
    children: 5
  - section: feature-section
    tag: section
    classes: ["mx-auto", "w-full", "max-w-6xl", "px-6"]
    height: 280px
    width: 1152px
    layout: block
    children: 1
    padding: "0px 24px"
  - section: feature-section
    tag: section
    classes: ["mx-auto", "w-full", "max-w-6xl", "px-6"]
    height: 392px
    width: 1152px
    layout: block
    children: 1
    padding: "0px 24px"
  - section: feature-section
    tag: section
    classes: ["mx-auto", "w-full", "max-w-6xl", "px-6"]
    height: 192px
    width: 1152px
    layout: block
    children: 1
    padding: "0px 24px"
  - section: section
    tag: section
    classes: ["max-w-6xl", "w-full", "mx-auto", "px-6"]
    height: 208px
    width: 1152px
    layout: block
    children: 1
    vertical-padding: ~48px
    padding: "0px 24px"
```

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


## 14. Copy Library (Real Content from Source)

*Actual text content extracted from the live page. Use these strings verbatim when reproducing the site — they carry the brand voice.*

```yaml
copy:
  section-headings:
    - "Start local. Scale with cloud."
    - "Get started with Ollama"
  sub-headings:
    - "Automate your work"
    - "Solve harder tasks, faster"
    - "For your most demanding work"
  ctas:
    - "Sign in"
    - "Download"
    - "Create account"
    - "Get Pro"
    - "Get Max"
  navigation:
    - "Models"
    - "Docs"
    - "Pricing"
    - "Sign in"
    - "Download"
  footer-links:
    - "Download"
```

**Agent rule**: reuse these exact strings when generating UI. Do NOT translate or rephrase — brand voice is preserved through the original wording.


## 15. Asset Inventory (Image Roles & Ratios)

*Image inventory classified by role and aspect ratio. When reproducing the site, allocate this number of assets per role.*

```yaml
assets:
```

**Agent rule**: when generating placeholder images, match these counts and aspect ratios. Use neutral placeholder backgrounds for `product` (e.g. `#f5f5f5`), full-color photography hints for `hero` and `editorial`.


## 16. Component HTML Templates

*Suggested HTML markup for reproducing the key components — based on what was detected in the source DOM.*

### Button (primary action)
```html
<button class="btn btn-primary">
  Sign in
</button>
```
_Source pattern detected: padding `6px 16px` · radius `9999px` · weight `400`_

**Agent rule**: use these markup skeletons as the structural baseline. Apply tokens from §2-3 for visual styling.


## 17. Content Architecture & Resources (Links by Purpose)

*The page's links classified by purpose — the information architecture to reproduce. Categories, featured images, devices and projects are extracted from the rendered DOM, not guessed.*

**By purpose:** **nav** 3 · **cta** 1 · **auth** 1 · **pricing** 1 · **docs** 4 · **blog** 1 · **social** 3 · **legal** 2 · **footer** 1 · **other** 4

**Primary actions (conversion path):**
- Account access — "Sign in" (login/signup) → `https://ollama.com/signin`
- Primary call-to-action — "Create account" (the conversion path) → `https://ollama.com/signup`

**Signals:** 1/21 links carry a featured image · device mockups detected: tablet ×1 · dominant link roles: inline-link (10), footer-link (8), navigation (3).


---
## Extraction Completeness: 62/100 (C)

| Category | Score | Max | Detail |
|----------|-------|-----|--------|
| Colors & Palette | 17 | 25 | 12 named colors |
| Typography | 18 | 20 | 7 roles defined |
| Components | 8 | 20 | 2 specs extracted |
| Motion & Interaction | 12 | 15 | Keyframes |
| CSS Custom Properties | 3 | 10 | 52 vars |
| Responsive Breakpoints | 5 | 5 | 5 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 |
|----------|----------------|-------------------|
| **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 |

### Per-section confidence

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

## 11.1 CSS Implementation Guide (CSS Interception Engine v2.15+)

*Ready-to-use CSS from Prism's CSS Interception Engine — intercepted directly from the site's CSS files (bypasses CORS). Copy-paste into your `<style>` block.*

### Keyframe Animations (Intercepted from CSS)

**1 @keyframes found** — these are the real animation definitions:

```
@keyframes spin { ... }
```

<details><summary>Full keyframes CSS (1 animations)</summary>

```css
@keyframes spin{to{transform:rotate(1turn)}}
```
</details>

### Hover State CSS (Intercepted)

**1 hover rule lines** captured from CSS files. Key interactive transitions from real CSS (not inferred):

```css
[type=checkbox]:checked:focus,[type=checkbox]:checked:hover,[type=checkbox]:indeterminate,[type=radio]:checked:focus,[type=radio]:checked:hover{background-color:currentColor;border-color:#0000}

[type=checkbox]:indeterminate:focus,[type=checkbox]:indeterminate:hover{background-color:currentColor;border-color:#0000}
```

> **Note**: All values above are extracted from the live site's CSS files. The font files are saved locally by Prism and embedded in the output HTML. Use them as-is for maximum fidelity.

## 11.2 Measured Reality (CDP Engine)

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

### Real Responsive Breakpoints
**5 breakpoints** read from the live `@media` rules (not guessed):
`640px` · `768px` · `850px` · `1024px` · `1280px`

### Measured Design Scale
**Type scale by usage** (× = paint count): `16px`×100 · `14px`×36 · `12px`×25 · `18px`×19 · `36px`×10 · `24px`×7 · `20px`×4 · `30px`×2

**Radius scale** (× = paint count): `9999px`×17 · `16px`×3 · `12px`×2

**Weights** (× = paint count): `400`×177 · `500`×22 · `600`×4

**Layout gaps** (× = paint count): `12px`×7 · `80px`×3 · `16px`×2 · `8px`×1 · `24px`×1

### 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
header { background-color:rgb(255 255 255/var(--tw-bg-opacity)) }
h1 { font-family:SF Pro Rounded,system-ui,-apple-system,BlinkMacSystemFont,sans-serif }
h1 { font-size:1.875rem }
h1 { font-weight:500 }
@media (min-width: 768px) h1 { font-size:2.25rem }
h2 { font-family:SF Pro Rounded,system-ui,-apple-system,BlinkMacSystemFont,sans-serif }
h2 { font-size:2.25rem }
h2 { font-weight:500 }
button { color:inherit; font-family:inherit; font-size:100%; font-weight:inherit }
button { color:rgb(115 115 115/var(--tw-text-opacity)) }
input { color:inherit; font-family:inherit; font-size:100%; font-weight:inherit }
input { border-radius:9999px }
```

> 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://ollama.com | 2026-06-11T05:01:54.950Z*
*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.*