# Parser feature grid

Schema: Design Details SECTION.md v3.2
Website: Captain
Source: https://www.captain.dev/
Source section IDs: aa82da3d-5de9-4aaa-8c7e-bdbc92ccac1b
Status: AI analysed; vocabulary promotion is automated

## Builder's note

What makes it work:
- Each column opens with a short uppercase mono tag (DOCX, PDF, VIDEO+AUDIO) above one focused paragraph, so the three file types can be scanned in seconds.
- Thin 1px dividers and a dotted rule give structure without boxes, and the sparse white canvas with dark navy text keeps the focus on the copy.
- The asymmetric top row, with the headline on the left and a label plus intro on the right, leads into an even three-column grid below.

What a screenshot can't show:
- The recording shows only a scroll reveal of the parser content between about 47s and 57s; stagger, easing and duration are not visible.
- No font sizes, line heights or gaps were measured, so the type scale and spacing rhythm can't be confirmed.

Borrow: Pair a tiny mono label with one tight paragraph in each column, and separate the columns with hairline dividers instead of cards.
Leave alone: Don't copy the exact navy and blue palette, the Poppins, Instrument Sans and Geist Mono combination, or the dotted-rule and bracket-tag devices; use your own type pairing and divider motif.

## Classification

- Type: feature-grid
- Layout: Three-column horizontal grid.
- Styles: minimal, typographic
- Confidence: 95%

## Purpose and structure

A light-themed, minimalist grid of three text-heavy feature blocks explaining parser capabilities.

Visual signature: Very clean, sparse white section with three distinct blocks of text.

## Components

- grid layout
- headings
- text blocks
- small tags

## Typography

- Display: Poppins — 80px 400
- Heading: Poppins — 48px 400
- Body: instrumentSans — 20px 400
- Mono: geistMono — 12px 500

## Functional palette

- Canvas: canvas #FFFFFF
- Text: text #000F2E
- Primary-Action: primary action #0043CA
- Muted-Text: muted text #797E88
- Surface: surface #F1F5FF

## Motion evidence

- 47.0–57.0s — Scroll reveals information about the parser handling DOCX, PDF, Video/Audio files. (90% confidence)

## Section quality

Overall: 61.82/100 (Good)
Scored coverage: 85%

- Typography: 66 — Clear hierarchy between the heading, intro copy, and three-column feature text, using the documented Poppins/Instrument Sans/Geist Mono pairing with tight negative letter-spacing on the headline and uppercase mono tags for labels. The contrast between headline weight and body copy is restrained and consistent, but the type system itself is simple and the section leans entirely on type with little typographic invention beyond scale and case changes. Next tier: Needs a more distinctive typographic move (e.g. unusual scale jumps, numerals, or treatment unique to this grid) beyond standard heading/body/label hierarchy to earn a higher score.
- Composition: 64 — A disciplined three-column grid with a dotted-line rule separating the headline block from the supporting text, and thin 1px dividers separating the three feature columns, producing a clean, legible structure. The asymmetric top row (headline left, label+paragraph right) adds some compositional interest, but the three-column bottom grid is a very conventional, evenly-spaced layout with no unusual spatial tension or depth cues. Next tier: Requires a less default grid resolution (asymmetric column widths, varied vertical rhythm, or an added visual anchor) to move past a conventional three-column text layout.
- Motion: inconclusive — Gemini only describes a generic scroll reveal of the three columns without timestamped per-element detail (stagger timing, easing, or distinct motion behavior), so motion quality cannot be verified. Next tier: Needs specific timestamped evidence of distinct per-element motion behavior (stagger, entrance easing, parallax) to assess beyond presence of a scroll reveal.
- Content: 60 — Copy is tightly integrated with layout: each column pairs a short mono tag (DOCX, PDF, VIDEO+AUDIO) with a focused paragraph that directly expands the headline's claim, giving the grid a clear narrative purpose rather than generic feature filler. Next tier: Content is purely textual; no supporting visual, diagram, or data treatment ties the claims to concrete evidence, capping how memorable the integration can be.
- Originality: 55 — The dotted-rule divider and mono bracket tag are a mild distinguishing touch, but the overall pattern—headline, intro line, three-column text grid with dividers—is a common minimalist SaaS layout seen across many similar product sites. Next tier: Needs a structural or visual device genuinely specific to this grid (not just a tag/divider treatment) to separate it from generic minimalist feature grids.
- Adaptability: 62 — The skin (color palette, sharp 0px radius, thin borders, mono labels) is clearly separable from the structural skeleton (headline + 3-column grid with dividers), and the deterministic tokens (colors, fonts, border style) are well documented, making restyling straightforward. Next tier: Lack of animation parameters and limited structural variation (only one grid configuration shown) limits confidence in how the layout would adapt to different content lengths or breakpoints.

Strengths:
- Clean hierarchy separating headline, supporting copy, and feature columns using consistent type roles
- Thin dividers and dotted rule provide subtle structural separation without heavy visual weight
- Mono uppercase tags give each column a quick-scan label consistent with the technical tone

Weaknesses:
- Three-column grid is a very conventional, evenly spaced layout with no distinguishing spatial idea
- No visual, icon, or diagram accompanies the text columns to reinforce the parsing claims
- Motion detail insufficient to confirm any crafted entrance behavior beyond a basic scroll reveal

Why it does not reach the next tier: The section is legible and well-organized but relies entirely on a standard minimalist text-grid pattern without a structural or visual idea that would be hard to substitute with a generic template.

## Adaptation guidance

- Effort: Low
- Guidance: Swap palette and fonts while keeping the grid skeleton, divider lines, and tag+paragraph column pattern; structure adapts easily to other feature counts by adjusting column widths.

What transfers:
- Three-column feature grid skeleton with divider lines
- Headline + intro-copy + column-label pattern
- Mono-tag labeling convention for feature categories

Dependencies:
- Specific font family tokens (Poppins, Instrument Sans, Geist Mono)
- Exact color palette (canvas white, dark navy text, blue accent)
- Sharp 0px corner/border system for visual consistency

## Living vocabulary

- No reusable vocabulary candidates were supported by this section.

Only terms with status `active` enter the public taxonomy. Deferred and proposed terms remain available to later AI passes; rejected terms remain as provenance so they are not repeatedly reinvented.

## Provenance and limitations

- Section boundaries and naming: Gemini Pro visual observation
- Motion observations: Gemini Pro direct-video analysis
- Quality judgment: Claude
- Exact design facts: browser/CSS extraction at website scope
- Rubric: Design Details section rubric 3.2 (Typography 20%, Composition 20%, Motion 15%, Content 15%, Originality 15%, Adaptability 15%)
- Motion scored as inconclusive due to lack of timestamped per-element detail
- No color/animation parameter evidence beyond static screenshot and DOM facts
- Assessment limited to single desktop viewport capture

## Usage guidance

Use this section as design evidence. Create an original implementation; do not reproduce the source copy, assets, or proprietary composition exactly.

## Build blueprint v3.2

### Purpose and classification

- Canonical type: features
- Source type: feature-grid
- Structure: grid
- Layout: Three-column horizontal grid.
- Styles: minimal, typographic
- Components: grid layout, headings, text blocks, small tags
- Purpose: A light-themed, minimalist grid of three text-heavy feature blocks explaining parser capabilities.
- Visual signature: Very clean, sparse white section with three distinct blocks of text.
- Place on the page: 9 of 11, after Feature collection (`captain:C07`), before Logo strip (`captain:C09`)

### Crop and composition

- Crop: 1200×536px; aspect ratio 2.239:1
- Page bounds: 15398–16041px of 17712px
- Guidance: Keep a clear anchor card and consistent internal card rules so the grid reads as one system.

### Exact typography evidence

The sectionScale values were measured inside this crop. The siteRoles values explain how those faces function across the source website; they must not replace section measurements.

```json
{
  "sectionScale": [],
  "siteRoles": [
    {
      "role": "display",
      "size": "80px",
      "family": "Poppins",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-5: computed CSS at 1440×1000; AI role: Poppins at 80px used for the main hero headline.",
      "sampleId": "font-5",
      "confidence": 1,
      "lineHeight": "80px",
      "letterSpacing": "-1.6px"
    },
    {
      "role": "heading",
      "size": "48px",
      "family": "Poppins",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-1: computed CSS at 1440×1000; AI role: Poppins at 48px used for major section headings.",
      "sampleId": "font-1",
      "confidence": 1,
      "lineHeight": "52.8px",
      "letterSpacing": "-1px"
    },
    {
      "role": "body",
      "size": "20px",
      "family": "instrumentSans",
      "source": "computed",
      "traits": "Regular",
      "weight": "400",
      "evidence": "font-6: computed CSS at 1440×1000; AI role: Instrument Sans at 20px used for primary descriptive paragraphs.",
      "sampleId": "font-6",
      "confidence": 1,
      "lineHeight": "26px",
      "letterSpacing": "-0.4px"
    },
    {
      "role": "mono",
      "size": "12px",
      "family": "geistMono",
      "source": "computed",
      "traits": "uppercase",
      "weight": "500",
      "evidence": "font-13: computed CSS at 1440×1000; AI role: Geist Mono at 12px uppercase used for technical labels, tags, and small metadata.",
      "sampleId": "font-13",
      "confidence": 1,
      "lineHeight": "14.4px",
      "letterSpacing": "0.5px"
    }
  ]
}
```

### Contextual design review

```json
{
  "status": "client-review-required",
  "checks": {
    "hierarchy": "Does each eyebrow, label and text level add useful information or clarify a necessary decision?",
    "decoration": "Do borders, effects, motion and spacing explain grouping or express a specific idea?",
    "repetition": "Can repeated claims, descriptions or actions be removed without losing needed information?",
    "identity": "What visible relationship between this offer, actual copy, imagery, typography and space gives the composition a convincing identity? Name its contribution and losses; matching ingredients or sparse styling are insufficient.",
    "reference": "Does it retain the source's dominant explanatory effect, media role, type balance and quiet space, not just columns?"
  },
  "heroMedia": {
    "appliesWhen": "A hero relies on focal media. A reasoned no-image hero remains valid and is judged by its visible composition.",
    "plan": "Record the image/headline first impression, actual available asset and crop, source image contribution, replacement contribution and losses before studies.",
    "review": "Does the actual hero suggest an offer, audience and experience appropriate to the whole brief? Quiet copy space or a recognizable subject is insufficient. One activity may lead without depicting all offers; justify its emphasis and resolve misleading implications. Missing assets or uncertain essential effects remain unverified."
  },
  "optionMedia": {
    "appliesWhen": "A section uses imagery to help visitors distinguish choices.",
    "planPerChoice": [
      "visitor distinction",
      "observable image evidence",
      "available asset or unresolved dependency",
      "crop retaining the distinguishing detail"
    ],
    "review": "Inspect the actual images. Shared atmosphere, changed crops or matching cards do not establish choice-specific meaning. If that role fails, resolve assets, choose an executable alternative or record lost/unverified and reject. Text comparison can be valid; it preserves a different contribution."
  },
  "noteCheck": "Check editorial interpretations against the received image; retain conflicts and unknown states instead of inventing selection or image meaning.",
  "decision": "Judge brief fit and positive character separately from layout preservation. Compare actual renders/references; essential lost or unverified effects prevent proceed. Reject either or both weak directions after inspection.",
  "qualityCertified": false
}
```

### Typography preservation review

```json
{
  "beforeStudy": "Use the actual reference image and captured section values to describe what its typography contributes: letter proportions and width, weight and contrast, case, line breaks and text-block shape, scale, spacing and relationship to the image. Label visual observations separately from captured facts and unknowns.",
  "substitution": "Choose an available, permitted face for the brief. Explain any substitute by the source relationships it preserves and any deliberate change; a familiar family, a serif/sans category or a mood label alone is not a justification. Do not copy an unavailable proprietary font or ban a common family merely because it is common.",
  "finalCheck": "Compare the actual rendered headline and supporting type beside this reference at the intended viewport. Check the loaded face/fallback and visible proportions, weight, line breaks, scale, spacing, contrast and image balance. Revise or reject when an essential typographic contribution is lost or unverified; a layout match or a font name is not a typography pass.",
  "unknowns": [
    "Section-specific computed typography was not recorded; website context cannot fill this gap.",
    "Glyph proportions, optical weight, actual line breaks, text-block shape and type-to-image balance require inspection of the reference image.",
    "Actual rendered face, font availability/licensing and responsive typography are not verified by this response."
  ]
}
```

### Exact color evidence

The section samples record where each computed value was used. Functional roles come from the website-level classifier and remain separate.

```json
{
  "sectionUsage": [
    {
      "value": "#FFFFFF",
      "cssValue": "rgba(255, 255, 255, 0.1)",
      "alpha": 0.10196078431372549,
      "appliedAs": [
        "background"
      ],
      "occurrences": 15,
      "sourceId": "color-11"
    },
    {
      "value": "#F1F5FF",
      "cssValue": "rgb(241, 245, 255)",
      "alpha": 1,
      "appliedAs": [
        "control-background",
        "background"
      ],
      "occurrences": 5,
      "sourceId": "color-12"
    },
    {
      "value": "#DCDCDC",
      "cssValue": "rgb(220, 220, 220)",
      "alpha": 1,
      "appliedAs": [
        "background",
        "border"
      ],
      "occurrences": 4,
      "sourceId": "color-15"
    }
  ],
  "functionalPalette": [
    {
      "hex": "#FFFFFF",
      "name": "canvas",
      "role": "canvas",
      "source": "computed",
      "evidence": "color-1: computed rgb(255, 255, 255); AI role: Pure white (#FFFFFF) used as the primary background color for most content sections.",
      "sampleId": "color-1",
      "confidence": 1
    },
    {
      "hex": "#000F2E",
      "name": "text",
      "role": "text",
      "source": "computed",
      "evidence": "color-2: computed rgb(0, 15, 46); AI role: Very dark blue/black (#000F2E) used for primary text on light backgrounds.",
      "sampleId": "color-2",
      "confidence": 1
    },
    {
      "hex": "#0043CA",
      "name": "primary action",
      "role": "primary-action",
      "source": "computed",
      "evidence": "color-3: computed rgb(0, 67, 202); AI role: Vibrant blue (#0043CA) used for primary buttons, prominent text accents, and illustrations.",
      "sampleId": "color-3",
      "confidence": 1
    },
    {
      "hex": "#797E88",
      "name": "muted text",
      "role": "muted-text",
      "source": "computed",
      "evidence": "color-5: computed rgb(121, 126, 136); AI role: Gray (#797E88) used for secondary text, labels, and brackets.",
      "sampleId": "color-5",
      "confidence": 0.9
    },
    {
      "hex": "#F1F5FF",
      "name": "surface",
      "role": "surface",
      "source": "computed",
      "evidence": "color-12: computed rgb(241, 245, 255); AI role: Very light blue (#F1F5FF) used for subtle interactive backgrounds like the 'Claude Code' tab.",
      "sampleId": "color-12",
      "confidence": 0.8
    }
  ]
}
```

### Design tokens

```json
{
  "radius": "Buttons and containers appear to have 0px radius based on visual inspection.",
  "density": "Low overall density with high-density micro-typography (monospaced labels and brackets) clustered in specific areas.",
  "evidence": "DOM/CSS facts show no mention of border-radius in component examples; screenshots show sharp corners, 1px borders for structure, and significant whitespace.",
  "borderStyle": "Thin 1px solid borders used heavily for structural dividing lines, tabs, and code block containers.",
  "buttonStyle": "Solid, sharp-edged rectangles for primary CTAs (blue background, white text) with a distinct trailing arrow icon block.",
  "cornerStyle": "Sharp 0px border radii on buttons, inputs, and layout containers, reinforcing a precise, technical feel.",
  "contentWidth": "Restricted central content column with wide, full-bleed background bands for section separation.",
  "spacingRhythm": "Generous vertical spacing between major sections, with tight groupings inside technical feature blocks."
}
```

### Reconstruction specification

This is the implementation contract for the captured desktop viewport. Prefer section-specific facts here over general website descriptions.

- Root: 1440×643px; block; padding {"top":"0px","left":"0px","right":"0px","bottom":"0px"}; gap normal; background rgb(255, 255, 255); radius 0px.
- Representative content widths: 821, 419, 362px.
- Layout containers: 0; cards/surfaces: 0; media elements: 0; browser animations: 0.

#### Container, grid, and spacing

```json
{
  "viewport": {
    "width": 1440,
    "captureBounds": {
      "top": 15398,
      "bottom": 16041,
      "pageHeight": 17712
    }
  },
  "container": {
    "size": "1440×643px",
    "position": "x 0px, y 15362px",
    "display": "block",
    "positionMode": "static",
    "padding": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "margin": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "gap": "normal",
    "columns": "not captured",
    "background": "rgb(255, 255, 255)",
    "radius": "0px",
    "border": "0px solid rgb(228, 228, 231)",
    "shadow": "none",
    "overflow": "visible"
  },
  "spacing": {
    "observedGapsPx": [],
    "representativeContentWidthsPx": [
      821,
      419,
      362
    ]
  },
  "columns": []
}
```

#### Cards and surfaces

```json
{
  "cards": [],
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  }
}
```

#### Media treatment

```json
[]
```

#### Browser-exposed animation parameters

```json
[]
```

### Measured geometry, surfaces, media, and animation

These raw values come from the saved element map and computed styles. Empty arrays mean the fact was not captured; they are not permission to invent source values.

```json
{
  "root": {
    "id": "ld-732",
    "gap": "normal",
    "tag": "section",
    "rect": {
      "x": 0,
      "y": 15362,
      "width": 1440,
      "height": 643
    },
    "role": null,
    "label": "[Parsing]Search fails at the parser,not at the embedding.A DOCX or a scanned PDF is not text yet. Wh",
    "border": "0px solid rgb(228, 228, 231)",
    "margin": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "radius": "0px",
    "shadow": "none",
    "columns": null,
    "display": "block",
    "padding": {
      "top": "0px",
      "left": "0px",
      "right": "0px",
      "bottom": "0px"
    },
    "overflow": "visible",
    "position": "static",
    "background": "rgb(255, 255, 255)"
  },
  "cards": [],
  "media": [],
  "bounds": {
    "top": 15398,
    "bottom": 16041,
    "pageHeight": 17712
  },
  "schema": "little-details-section-measurements-v1",
  "source": "saved DOM/CSS element and animation maps",
  "columns": [],
  "spacing": {
    "gapsPx": [],
    "representativeContentWidthsPx": [
      821,
      419,
      362
    ]
  },
  "coverage": {
    "cards": 0,
    "media": 0,
    "animations": 0,
    "elementsInSection": 12
  },
  "surfaces": {
    "radii": [],
    "borders": [],
    "shadows": []
  },
  "animations": [],
  "capturedAt": "2026-09-21T04:30:03.294Z",
  "limitations": [
    "Values describe the captured desktop viewport and may change at other breakpoints.",
    "Transforms, sticky layers, and virtualized content can make the inferred section root approximate.",
    "Animations include browser-exposed Web Animations API state; CSS or script motion that was inactive at capture time may be absent."
  ],
  "viewportWidth": 1440
}
```

### Observed motion

1. **scroll** — Scroll reveals information about the parser handling DOCX, PDF, Video/Audio files. (47s–57s; 90% confidence). Recreate the interaction principle with project-appropriate timing and easing; the evidence does not guarantee source easing values.

The browser animation records above are deterministic parameters captured from active browser animations. The timestamped observations describe what Gemini saw in the video. Treat them as complementary evidence. When either source is empty or they conflict, state the uncertainty instead of inventing timing or easing.

### Responsive contract

- Measured viewport: 1440px wide.
- Mobile/tablet values: not measured by this section evidence unless a separate capture is explicitly listed.
- Preserve hierarchy and sequence; collapse simultaneous columns only where needed, maintain media aspect ratios, and verify touch targets and text wrapping at target breakpoints.

### Structure versus visual skin

These categories describe evidence, not independent layers that can be swapped without changing the design. Study the complete reference system before adapting it.

- Preserve: content hierarchy, layout relationships, section rhythm, interaction purpose.
- Adapt: brand colors, font family, copy, imagery, icons, decorative details.
- Rule: These compatibility categories are coupled: fonts, color and imagery can carry the layout's design logic. Preserve or purposefully replace their contribution while creating original branding, copy, assets, and implementation details.

### Adaptation and dependencies

- Effort: low
- What transfers: Three-column feature grid skeleton with divider lines; Headline + intro-copy + column-label pattern; Mono-tag labeling convention for feature categories
- Dependencies: Specific font family tokens (Poppins, Instrument Sans, Geist Mono); Exact color palette (canvas white, dark navy text, blue accent); Sharp 0px corner/border system for visual consistency
- Guidance: Swap palette and fonts while keeping the grid skeleton, divider lines, and tag+paragraph column pattern; structure adapts easily to other feature counts by adjusting column widths.

### Evidence readiness

- Coverage: 7/7
- Can build: Yes
- Missing facts: None


### Agent implementation prompt

Create an original features section inspired by the design evidence titled “Parser feature grid”.

Purpose: A light-themed, minimalist grid of three text-heavy feature blocks explaining parser capabilities.

Structure: grid. Source layout label: Three-column horizontal grid.. Keep a clear anchor card and consistent internal card rules so the grid reads as one system.

Visual signature to preserve at the pattern level: Very clean, sparse white section with three distinct blocks of text.

Components: grid layout, headings, text blocks, small tags.

Style direction: minimal, typographic.

Observed crop: 1200×536px (2.239:1). Treat this as evidence of composition, not a mandatory output size.

Typography evidence: {"role":"display","size":"80px","family":"Poppins","source":"computed","traits":"Regular","weight":"400","evidence":"font-5: computed CSS at 1440×1000; AI role: Poppins at 80px used for the main hero headline.","sampleId":"font-5","confidence":1,"lineHeight":"80px","letterSpacing":"-1.6px"} {"role":"heading","size":"48px","family":"Poppins","source":"computed","traits":"Regular","weight":"400","evidence":"font-1: computed CSS at 1440×1000; AI role: Poppins at 48px used for major section headings.","sampleId":"font-1","confidence":1,"lineHeight":"52.8px","letterSpacing":"-1px"} {"role":"body","size":"20px","family":"instrumentSans","source":"computed","traits":"Regular","weight":"400","evidence":"font-6: computed CSS at 1440×1000; AI role: Instrument Sans at 20px used for primary descriptive paragraphs.","sampleId":"font-6","confidence":1,"lineHeight":"26px","letterSpacing":"-0.4px"} {"role":"mono","size":"12px","family":"geistMono","source":"computed","traits":"uppercase","weight":"500","evidence":"font-13: computed CSS at 1440×1000; AI role: Geist Mono at 12px uppercase used for technical labels, tags, and small metadata.","sampleId":"font-13","confidence":1,"lineHeight":"14.4px","letterSpacing":"0.5px"}

Color evidence: {"hex":"#FFFFFF","name":"canvas","role":"canvas","source":"computed","evidence":"color-1: computed rgb(255, 255, 255); AI role: Pure white (#FFFFFF) used as the primary background color for most content sections.","sampleId":"color-1","confidence":1} {"hex":"#000F2E","name":"text","role":"text","source":"computed","evidence":"color-2: computed rgb(0, 15, 46); AI role: Very dark blue/black (#000F2E) used for primary text on light backgrounds.","sampleId":"color-2","confidence":1} {"hex":"#0043CA","name":"primary action","role":"primary-action","source":"computed","evidence":"color-3: computed rgb(0, 67, 202); AI role: Vibrant blue (#0043CA) used for primary buttons, prominent text accents, and illustrations.","sampleId":"color-3","confidence":1} {"hex":"#797E88","name":"muted text","role":"muted-text","source":"computed","evidence":"color-5: computed rgb(121, 126, 136); AI role: Gray (#797E88) used for secondary text, labels, and brackets.","sampleId":"color-5","confidence":0.9} {"hex":"#F1F5FF","name":"surface","role":"surface","source":"computed","evidence":"color-12: computed rgb(241, 245, 255); AI role: Very light blue (#F1F5FF) used for subtle interactive backgrounds like the 'Claude Code' tab.","sampleId":"color-12","confidence":0.8}

No section-bounded typography samples were measured.

Colors measured inside this section: {"id":"color-11","hex":"#FFFFFF","alpha":0.10196078431372549,"count":15,"contexts":[{"tag":"span","top":14280,"text":"OCR","property":"background"},{"tag":"div","top":16005,"text":"","property":"background"}],"cssValue":"rgba(255, 255, 255, 0.1)"} {"id":"color-12","hex":"#F1F5FF","alpha":1,"count":5,"contexts":[{"tag":"a","top":42,"text":"Sign in","property":"control-background"},{"tag":"button","top":8229,"text":"Claude Code","property":"control-background"},{"tag":"span","top":15800,"text":"DOCX","property":"background"}],"cssValue":"rgb(241, 245, 255)"} {"id":"color-15","hex":"#DCDCDC","alpha":1,"count":4,"contexts":[{"tag":"div","top":15739,"text":"","property":"background"},{"tag":"div","top":15740,"text":"PDFClean PDFs parse anywhere. Captain also reads the rotated scan and the handwritten margin note.","property":"border"}],"cssValue":"rgb(220, 220, 220)"}

Exact section measurements from the saved element map: root {"rect":{"x":0,"y":15362,"width":1440,"height":643},"padding":{"top":"0px","left":"0px","right":"0px","bottom":"0px"},"gap":"normal","columns":null,"overflow":"visible"}; spacing {"gapsPx":[],"representativeContentWidthsPx":[821,419,362]}; surfaces {"radii":[],"borders":[],"shadows":[]}

Motion evidence: scroll: Scroll reveals information about the parser handling DOCX, PDF, Video/Audio files. (90% confidence)

Transfer these principles: Three-column feature grid skeleton with divider lines; Headline + intro-copy + column-label pattern; Mono-tag labeling convention for feature categories.

Dependencies: Specific font family tokens (Poppins, Instrument Sans, Geist Mono); Exact color palette (canvas white, dark navy text, blue accent); Sharp 0px corner/border system for visual consistency.

Adaptation guidance: Swap palette and fonts while keeping the grid skeleton, divider lines, and tag+paragraph column pattern; structure adapts easily to other feature counts by adjusting column widths.

Study layout, typography, color, imagery and spacing as one coordinated source system. Record what creates its effect before producing a concept; preserve or purposefully replace each consequential relationship when adapting the business content and assets.

Use new copy, imagery, branding, and implementation details. Do not reproduce the source website or its proprietary assets.
