figma-B5YYjdXH3ETCtoQrI6aZ3z

DESIGN.md

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

---
version: alpha
name: figma-B5YYjdXH3ETCtoQrI6aZ3z
description: "Light product system built on #ffffff with #881ffe as the primary CTA accent. Type anchored in Open Sans at 100px / weight 600. Extracted from the Figma file via the Figma REST API — exact fills, type styles, effects, and auto-layout spacing read straight from the design source of truth (not a rendered approximation)."
narrative: |
  figma-B5YYjdXH3ETCtoQrI6aZ3z is built on a pure-white canvas (rgb(255, 255, 255)).
  The system uses rgb(136, 31, 254) as the high-saturation accent for primary actions.
  Open Sans as the primary typeface.
  Open Sans is paired with Lato for secondary roles.
  A restrained elevation system (2 distinct shadows) — shadows reserved for the few elements that must lift off the page.

colors:
  background: "#ffffff"
  surface-1: "#ffffff"
  surface-2: "#ffffff"
  primary: "#881ffe"
  on-primary: "#ffffff"
  primary-hover: "#673ab7"
  hairline: "#d1c4e9"

typography:
  display-xl:
    fontFamily: "Open Sans, 'SF Pro Display', system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif"
    fontSize: 100px
    fontWeight: 600
    lineHeight: 0.5
    letterSpacing: 0
  display-lg:
    fontFamily: "Open Sans, 'SF Pro Display', system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif"
    fontSize: 96px
    fontWeight: 400
    lineHeight: 1.36
    letterSpacing: 0
  body-sm:
    fontFamily: "Open Sans, 'SF Pro Display', system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif"
    fontSize: 36px
    fontWeight: 600
    lineHeight: 1.36
    letterSpacing: 0

rounded:
  none: 0px
  xs: 15px
  sm: 17px
  md: 27px
  lg: 29px
  xl: 32px
  pill: 9999px

spacing:
  xxs: 2px
  xs: 4px
  sm: 8px
  md: 12px
  lg: 24px
  xl: 32px
  xxl: 64px

components:


extracted_at: "2026-06-11T05:00:42.492Z"
completeness: 29
scoreVersion: "v2"

---

# Design System — figma-B5YYjdXH3ETCtoQrI6aZ3z
> Extracted automatically by Prism from https://www.figma.com/design/B5YYjdXH3ETCtoQrI6aZ3z/MobileApp-Landing-Page-Template-for-Mobile-Apps-Showcase-(Community)
> Date: 2026-06-11
> Viewport: Desktop 2560x15786 + Mobile 390x844
> Values are extracted from the Figma REST API, not hand-written: exact fills, text styles, effects, and auto-layout spacing read straight from the design file (the source of truth, not a rendered approximation).


## 0. Design DNA

**Density**: moderate  |  **Motion**: still  |  **Weight**: light  |  **Aesthetic**: product-neutral

| Dimension | Value | Signal |
|---|---|---|
| Canvas | neutral | `#ffffff` |
| Type posture | sans-led (Open Sans) | "Testimonials" |
| Color assertion | dual-accent | #881ffe |
| Whitespace | moderate | section rhythm 48px |
| Interaction | still | 0 keyframes, 0 transitions |
| Radius language | 17px-rounded | from token scale |

**Prism fingerprint**: `neutral-canvas · sans-display · dual-accent · 17px-rounded · 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(136, 31, 254)` for primary CTAs ONLY. Never decorative.
> - **Body type**: 16px (token: `typography.body`). Default for ALL text not in a heading role.
> - **Section rhythm**: 48px between major bands. Card padding: 24px.
> - **Default radius**: 17px on buttons/inputs. Pills (`9999px`) only for icon-buttons or status chips.
>
> **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

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

Typography is anchored in **Open Sans**. Headlines use weight 600 for confident, assertive presence — the brand wants to be heard. 

Body text reads in Pure Black (`#000000`) (contrast ratio 21.0:1, well above WCAG AA). **#881ffe** (`#881ffe`) is the single high-saturation color in the system — it earns its presence only on interactive elements, making CTAs and links the unmistakable focal points against the otherwise neutral palette. Elevation comes from a small, deliberate set of shadows (2 distinct), each a multi-layer stack — several blurred layers at varying offsets — used sparingly rather than across the whole UI. 


**Key Characteristics:**
- Background: Pure White (`#ffffff`)
- Primary typeface: Open Sans
- Accent: #881ffe (`#881ffe`)
- Display: 100px weight 600
- Shadow system: 2 distinct elevation levels
- Custom fonts loaded: Open Sans, Lato

## 2. Color Palette & Roles

### Background & Surface
- **Pure White** (`#ffffff`): Page background (primary)
- **Light Blue** (`#b2ebf2`): Surface / elevated background

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

### Accent & Interactive
- **Lavender** (`#d1c4e9`): Interactive / accent
- **#881ffe** (`#881ffe`): Interactive / accent
- **#673ab7** (`#673ab7`): Interactive / accent
- **#00bcd4** (`#00bcd4`): Interactive / accent
- **#ff3000** (`#ff3000`): Interactive / accent
- **#9c27b0** (`#9c27b0`): Interactive / accent
- **#ffce33** (`#ffce33`): Interactive / accent

### Full Extracted Palette
**16 colors rendered on the page**. (10 categorized above + 6 additional below.)
Colors are read straight from the Figma file via the REST API (exact fills, text styles, effects, auto-layout spacing); design-token variables are preserved alongside them. Third-party logo colors are filtered out.

- `#979797` — Grey
- `#ff3231` — Vermillion
- `#3157ff` — #3157ff
- `#00a8ee` — Sky Bright
- `#ff31d3` — #ff31d3
- `#e1bee7` — #e1bee7

## 3. Typography Rules

### Font Families
- **Primary**: `Open Sans`
- **Secondary**: `Lato`

### Custom Fonts Loaded
- **Open Sans** weight undefined (undefined)
- **Lato** weight undefined (undefined)

### Typography Hierarchy

| Role | Font | Size | Weight | Line Height | Letter Spacing | Notes |
|------|------|------|--------|-------------|----------------|-------|
| Display Hero | Open Sans | 100px | 600 | 0.5 | normal | Main headline (heading) |
| Section Heading | Open Sans | 96px | 400 | 1.36 | normal | Section titles (subheading) |
| Link Large | Open Sans | 36px | 600 | 1.36 | normal | Link (36px) — Decoration: none |

### Full Font Size Scale

Sizes detected in the design (descending): `100px`, `96px`, `72px`, `66px`, `64px`, `60px`, `46px`, `42px`, `36px`, `28px`, `24px`

> 8 size(s) detected outside the sampled hierarchy (72px, 66px, 64px, 60px, 46px, 42px, 28px, 24px). These appear on elements not in the sampled set — likely additional display sizes, marketing-section overrides, or third-party-widget styles.

## 4. Component Stylings

## 5. Layout Principles

### Layout Type
**hero + sections**

### Grid
Single column, centered content

### Max Width
1200px

### Spacing System
Compact spacing — information density prioritized

| Token | Value |
|-------|-------|
| xxs | 2px |
| xs | 4px |
| sm | 8px |
| md | 12px |
| base | 16px |
| lg | 24px |
| xl | 32px |
| 2xl | 48px |
| 3xl | 64px |

### Border Radius Scale
| Name | Value | Use |
|------|-------|-----|
| None | 0px | No rounding |
| Xs | 15px | Tiny corners (badges, micro elements) |
| Sm | 17px | Buttons, inputs, small elements |
| Md | 27px | Cards, containers |
| Lg | 29px | 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` |
| Navigation | `0px` |

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

**Full Radius Spectrum**: 0px, 15px, 17px, 27px, 29px (from `allBorderRadii` scan)


## 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** | `64px` | Top/bottom of full-bleed hero sections |
| **section** | `32px` | Between major bands (color change, content shift) |
| **subsection** | `24px` | Within a section, between content groups |
| **card** | `12px` | Card padding, list-item spacing |
| **compact** | `8px` | 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).

**2/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:** 1613px tall (not full-viewport)
- **Heading:** "Testimonials" — 100px center-aligned
- **Subheading:** "Sed Imperdiet Enim li Vitae Viverra Justo"
- **Media:** present, positioned right
- **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 right of text.

### Navigation Pattern

- **Position:** sticky (stays visible during scroll)
- **Layout:** logo-left — 
- **Height:** 231px
- **Logo:** ✓ present
- **Nav links:** 1 primary items
- **CTAs in nav:** 0 (no buttons — links only)
- **Clone instruction:** Build a sticky logo left navigation. Link-only — no button styling needed.

## 6. Depth & Elevation

| Level | Treatment | Use |
|-------|-----------|-----|
| Flat (Level 0) | No shadow | Page background, content blocks |
| Layered (Level 1) | <br>`rgba(0, 0, 0, 0.06) 0px 3px 49px 5px` | Cards, elevated surfaces |
| Layered (Level 2) | <br>`rgba(0, 0, 0, 0.06) 0px 3px 49px 9px` | Cards, elevated surfaces |

**Shadow Philosophy**: Multi-layered shadow system creating natural, atmospheric depth. Each shadow level combines multiple layers for realistic elevation.

## 8. Do's and Don'ts

### Do
- Use Open Sans as the primary typeface — it defines the brand personality
- Keep font weights between 400-600 — the system uses a narrow weight range for subtle hierarchy
- Use the extracted shadow patterns for elevation — they are tuned to match the brand palette
- Use #881ffe (`#881ffe`) as the primary accent — it's the brand's signature interactive color
- Respect the 4px–32px spacing range — the design uses a wide scale for visual breathing room
- Make the navigation sticky — it stays visible during scroll, signaling content depth

### 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 — 600 is the maximum weight in this system
- Don't invent new shadow values — use only the extracted shadow levels
- Don't introduce additional saturated accent colors — the palette is intentionally controlled
- Don't put a CTA button in the nav — this design uses links only at the top


## 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(136, 31, 254)` for primary CTAs and brand-mark signals only"
    why: "Single chromatic assertion device — overuse dilutes meaning"
    test: "querySelectorAll('[style*=\"rgb(136, 31, 254)\"]').length <= 3 per fold"
```

## 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:** Illustration-driven

The site relies primarily on illustrations, vector art, and decorative SVG elements rather than photography. Use commissioned illustrations, icon sets, or generated graphics for clones — stock photos will feel off-brand.

**Media Format Mix:**
- WebP: 32 (optimized photo/illustration hybrid)
- SVG: 96 (icons, illustrations, decorative geometry)

**Imagery Guidance for clones:**
- Use vector illustration as the primary visual language — photos will read as off-brand.
- Maintain consistent illustration style (line weight, color palette) across the site.

## 10. Agent Prompt Guide

### Quick Reference
- Background: Pure White (`#ffffff`)
- Primary text: Pure Black (`#000000`)
- Accent: #881ffe (`#881ffe`)
- Border: Lavender (`#d1c4e9`)
- Font: Open Sans
- Body: 16px weight 400

### Example Component Prompts
- "Create a hero section on Pure White background (#ffffff). Headline at 100px Open Sans weight 600, line-height 0.5, color #000000."
- "Create the primary CTA button: `#881ffe` background, `#ffffff` text, 9999px border-radius, 11px 21px padding, 600 weight, Open Sans font."
- "Build navigation: relative on `#ffffff`. Open Sans 36px weight 600 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 Open Sans, weight range 400–600. Never exceed 600 — heavier weights break the brand's tonal restraint.
3. **Accent**: #881ffe (`#881ffe`) is the sole interactive color. On hover → #673ab7 (`#673ab7`). Use CSS transitions, not opacity/brightness filters.
4. **Spacing**: Use the `--ca-space-*` token scale (4px–32px). 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-on-primary: #ffffff;
  --ca-primary: #881ffe;
  --ca-primary-hover: #673ab7;
  --ca-hairline: #d1c4e9;
}

/* Typography */
:root {
  --ca-font-primary: "Open Sans", system-ui, sans-serif;
  --ca-text-display: 100px;
  --ca-text-heading: 96px;
  --ca-text-small: 36px;
}

/* Spacing & Radius */
:root {
  --ca-space-xxs: 2px;
  --ca-space-xs: 4px;
  --ca-space-sm: 8px;
  --ca-space-md: 12px;
  --ca-space-base: 16px;
  --ca-space-lg: 24px;
  --ca-space-xl: 32px;
  --ca-space-2xl: 48px;
  --ca-space-3xl: 64px;
  --ca-radius-none: 0px;
  --ca-radius-xs: 15px;
  --ca-radius-sm: 17px;
  --ca-radius-md: 27px;
  --ca-radius-lg: 29px;
  --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: section
    tag: div
    classes: ["Background Page"]
    height: 6623px
    width: full-bleed
    layout: block
    children: 3
  - section: footer
    tag: div
    classes: ["Footer"]
    height: 2744px
    width: full-bleed
    layout: block
    children: 13
  - section: section
    tag: div
    classes: ["Latest News"]
    height: 1466px
    width: 2345px
    layout: block
    children: 1
  - section: faq
    tag: div
    classes: ["FAQ"]
    height: 1305px
    width: 2248px
    layout: block
    children: 8
  - section: section
    tag: div
    classes: ["Logo"]
    height: 376px
    width: 1811px
    layout: block
    children: 2
  - section: social-proof
    tag: div
    classes: ["Testimonial"]
    height: 845px
    width: 1462px
    layout: block
    children: 4
  - section: features
    tag: div
    classes: ["Feature"]
    height: 2912px
    width: full-bleed
    layout: block
    children: 1
  - section: section
    tag: div
    classes: ["How It Works"]
    height: 4507px
    width: 2149px
    layout: block
    children: 4
  - section: section
    tag: div
    classes: ["Counter"]
    height: 268px
    width: 1913px
    layout: block
    children: 5
  - section: hero
    tag: div
    classes: ["Banner"]
    height: 1613px
    width: full-bleed
    layout: block
    children: 8
  - section: navigation
    tag: div
    classes: ["Header"]
    height: 231px
    width: 2205px
    layout: block
    children: 5
```

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


---
## Extraction Completeness: 29/100 (D)

| Category | Score | Max | Detail |
|----------|-------|-----|--------|
| Colors & Palette | 14 | 25 | 10 named colors |
| Typography | 8 | 20 | 3 roles defined |
| Components | 0 | 20 | 0 specs extracted |
| Motion & Interaction | — | N/A | Not applicable — a static Figma file has no animation |
| CSS Custom Properties | 0 | 10 | 0 vars (enable token scope file_variables:read to capture Figma Variables) |
| Responsive Breakpoints | — | N/A | Not applicable — single design frame, no media queries |
| Variable Fonts | — | N/A | Figma does not expose variable-font axes |

## 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 |
|----------|----------------|-------------------|
| **Hero imagery** | No dominant hero image detected above the fold | Use the canonical brand visual from §9b (OG image) for hero composition |
| **Motion / Animation** | No @keyframes or transitions detected | Either keep clones strictly static, or apply a single 150ms ease-out on hover/focus universally |
| **Component states** | Hover / focus / active states not captured | Darken background ~10% on hover, add 2px focus ring matching accent token, +50% opacity for disabled |
| **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 read from Figma frame fill |
| §2 Colors | Low | 0 CSS vars (semantic naming requires ≥20 for high) |
| §3 Typography | Medium | 3 typography roles inferred |
| §4 Components | Low | 0 component variants captured |
| §7 Motion | Low | No motion data |
| §8 Do's/Don'ts | High | 11 rules generated; design-decisions.json has evidence per rule |
| §9 Responsive | High | 4 breakpoints detected |
| §9b Photography | Medium | 128 images, hero not detected |

---
*Generated by Prism — automated Playwright extraction + design analysis.*
*Source: https://www.figma.com/design/B5YYjdXH3ETCtoQrI6aZ3z/MobileApp-Landing-Page-Template-for-Mobile-Apps-Showcase-(Community) | 2026-06-11T05:00:42.497Z*
*Values read straight from the Figma file via the REST API (exact fills, text styles, effects, auto-layout spacing). Cross-check against the live build before shipping.*