launchframe 0.4.3 → 0.4.4

package/.gemini/commands/launchframe.toml

@@ -25,7 +25,9 @@ Before reconnaissance, write or update:
 
 ## SaaS copy overlay (Phase 4 assembly and final polish)
 
-After structure and styles match the reference, apply the **SaaS idea** to hero, headings, and primary CTAs where the reference uses interchangeable marketing copy, **without** changing layout grids, spacing, or motion from extracted specs. Respect third-party brands.
+After structure and styles match the reference, apply the **SaaS idea** to hero, headings, and primary CTAs where the reference uses interchangeable marketing copy, **without** changing layout grids, spacing, or motion from extracted specs. **Brand identity** (below) must be **original** for anything you ship as the user’s product — never pass off the reference company’s trademarks or distinctive marks.
+
+**Precedence:** For those surfaces (hero, main headings, primary CTAs), **final ship copy comes from the SaaS idea**, not the reference — still capture reference strings in research/specs if useful for QA diffs. Everywhere else, keep **verbatim** reference text unless the user overrides.
 
 ---
 
@@ -33,16 +35,17 @@ After structure and styles match the reference, apply the **SaaS idea** to hero,
 
 The target page(s) are the URL(s) you parsed in Pre-Flight. Clone exactly what's visible at each URL. Unless the user specifies otherwise, use these defaults:
 
-- **Fidelity level:** Pixel-perfect — exact match in colors, spacing, typography, animations
+- **Fidelity level:** Pixel-perfect **layout, spacing, typography scale, and motion** (durations, easings, keyframes, triggers) matched to the reference. **Colors** match where you are emulating neutral/UI chrome from the reference; where **Brand identity** applies, use the **new palette** and assets while keeping the same CSS structure (fills land on different tokens). **Animations** stay reference-faithful unless the user opts out.
 - **In scope:** Visual layout and styling, component structure and interactions, responsive design, mock data for demo purposes
 - **Out of scope:** Real backend / database, authentication, real-time features, SEO optimization, accessibility audit
 - **Customization:** Structure and visuals — pure emulation of the reference. **Marketing copy** — apply the parsed **SaaS idea** where hero/headlines/CTAs are interchangeable (see “SaaS copy overlay” above); do not invent a different product than the user’s idea.
+- **Brand identity:** The reference is a **pattern** for layout, motion, and UI craft — **not** permission to ship their brand. Unless the user **explicitly** asks for a faithful copy of the reference brand (e.g. licensed work, clearly labeled internal mock, private design audit), **invent an original brand** aligned with the SaaS idea: product name, wordmark or simple logomark (SVG or styled text) sized to the same logo slot, favicon / app icon, OG imagery, and a cohesive palette. Do **not** reuse their trademarked logo paths, mascot art, or distinctive illustrative brand assets; use originals or functional UI icons instead. Hero or lifestyle images that center the reference brand should be replaced with **original** imagery or neutral compositions that keep the **same layout rhythm**. **Keep** reference-faithful neutrals where they are clearly **non-brand** UI (borders, subtle grays, default body text color roles) unless they are unmistakably part of their distinctive palette. Note in `docs/research/LAUNCHFRAME.md` which marks and assets are **original brand** versus **layout-only** extraction.
 
 If the user provides additional instructions (specific fidelity level, customizations, extra context), honor those over the defaults.
 
 ## Pre-Flight
 
-1. **Browser automation is required.** Check for available browser MCP tools (Chrome MCP, Playwright MCP, Browserbase MCP, Puppeteer MCP, etc.). Use whichever is available — if multiple exist, prefer Chrome MCP. If none are detected, ask the user which browser tool they have and how to connect it. This skill cannot work without browser automation.
+1. **Browser automation is required.** Check for available browser MCP tools (Chrome MCP, Playwright MCP, Browserbase MCP, Puppeteer MCP, etc.). Use whichever is available — if multiple exist, **prefer Chrome DevTools MCP** for inspection: it maps to the same engine the user sees and preserves **computed `animation` / `transition` / scroll-driven** values accurately. If none are detected, ask the user which browser tool they have and how to connect it. This skill cannot work without browser automation. **Motion parity:** every pass (reconnaissance, per-section extract, QA) must treat **motion as first-class** — same **durations, delays, easings (`cubic-bezier` / steps), iteration counts, fill modes, directions, keyframe percentages, and scroll/view-timeline bindings** as the live site, not “similar” motion.
 2. **Parse arguments** — extract every `http://` / `https://` URL token (there may be several). **SaaS idea** = the remaining non-URL text (trim outer quotes). Normalize and validate each URL; if any are invalid, or the SaaS idea is missing, ask the user once. For each valid URL, verify it is accessible via your browser MCP tool.
 3. Verify the base project builds: `npm run build`. The Next.js + shadcn/ui + Tailwind v4 scaffold should already be in place. If not, tell the user to set it up first.
 4. Create the output directories if they don't exist: `docs/research/`, `docs/research/components/`, `docs/design-references/`, `scripts/`. For multiple clones, also prepare per-site folders like `docs/research/<hostname>/` and `docs/design-references/<hostname>/`.
@@ -58,7 +61,7 @@ When you traverse the DOM and the Network panel, do **not** treat all nodes equa
 
 1. **Images (raster + video stills)** — Enumerate `<img>`, `<picture>`, responsive `srcset`, `data-*` lazy URLs, **computed `background-image`** on the element and parents (including pseudo-elements), mask images, `<video poster>`, hero media. **Scrape:** download binary assets to `public/images/` (or `public/videos/`) with stable paths referenced in specs. **Create** a replacement PNG/WebP/SVG only when the asset is blocked (CORS, auth cookie, 403), ephemeral, or impossible to URL-fetch — use a high-DPI screenshot crop, traced artwork, or CSS gradient approximation, and mark `ASSET_SOURCE: generated` in the component spec with a short reason.
 2. **SVGs & iconography** — Inline `<svg>`, sprite `symbol` defs, **SVG used as masks/filters**, icon fonts (prefer path extraction). Convert to `@/components/icons.tsx` (or section-local components) with meaningful names. Prioritize crisp edges and correct `viewBox` over shrinking bundle size during emulation.
-3. **Motion & animation** — CSS `@keyframes`, `animation`, `animation-timeline`, `transition`, `transform`, will-change hints; JS-driven motion (carousel timing, IntersectionObserver reveals); libraries (GSAP, Framer, Lottie JSON, Lenis). Capture **numbers** (ms, easing curves, stagger, scroll thresholds), not adjectives. Include **reduced-motion** behavior if present.
+3. **Motion & animation** — CSS `@keyframes`, `animation`, `animation-timeline` / `view-timeline` / `animation-range`, `transition`, `transform`, `transform-origin`, will-change; JS-driven motion (carousel timing, IntersectionObserver reveals); libraries (GSAP, Framer, Lottie JSON, Lenis). Capture **numbers** (ms, `cubic-bezier()`, `steps()`, stagger, scroll thresholds, **named keyframe blocks**), not adjectives — paste **verbatim** `cssText` for relevant `@keyframes` into specs when obtainable. Include **reduced-motion** (`matchMedia('(prefers-reduced-motion: reduce)'))` behavior if present.
 
 Only after the above are accounted for should you spend cycle time on minor text or non-visual refactors. A perfect grid with missing hero art and dead animation still fails the clone.
 
@@ -78,6 +81,8 @@ Look at each section and judge its complexity. A simple banner with a heading an
 
 Extract the actual text, images, videos, and SVGs from the live site. This is a clone, not a mockup. Use `element.textContent`, download every `<img>` and `<video>`, extract inline `<svg>` elements as React components. The only time you generate content is when something is clearly server-generated and unique per session.
 
+**Marketing surfaces** (hero, primary headings, main CTAs) follow the **SaaS copy overlay** and **Brand identity** rules — capture reference copy for audit, but **ship** the user’s idea there.
+
 **Prioritize** (see §0): downloadable imagery and backgrounds first, then SVG/icon layers, then motion. If you must **fabricate** an asset, prefer screenshot-based exports or traced vectors tied to measured box sizes — avoid unrelated stock art.
 
 **Layered assets matter.** A section that looks like one image is often multiple layers — a background watercolor/gradient, a foreground UI mockup PNG, an overlay icon. Inspect each container's full DOM tree and enumerate ALL `<img>` elements and background images within it, including absolutely-positioned overlays. Missing an overlay image makes the clone look empty even if the background is correct.
@@ -193,8 +198,113 @@ This is a dedicated pass AFTER screenshots and BEFORE anything else. Its purpose
 - Mobile: 390px
 - At each width, note which sections change layout (column → stack, sidebar disappears, etc.) and at approximately which breakpoint the change occurs.
 
+Re-check **all three widths** again in **Phase 5: Visual QA Diff** so tablet regressions are not skipped.
+
 Save all findings to `docs/research/BEHAVIORS.md`. This is your behavior bible — reference it when writing every component spec.
 
+### Chrome MCP: precise motion & animation extraction
+
+Use **evaluate script** (or equivalent) in Chrome MCP **during** the scroll/click/hover sweeps so you capture **live computed values**, not guesses from DevTools screenshots alone.
+
+**Rules:**
+
+- **No hand-waving** — if the reference uses `0.45s cubic-bezier(0.4, 0, 0.2, 1)`, the spec and implementation use that exact string (or Tailwind utilities **only** when the **resolved computed** animation/transition longhands match — class names alone are not proof).
+- **`@keyframes` source of truth** — for each animated element, record `getComputedStyle(el).animationName` and resolve the **full `@keyframes` rule** from stylesheets when allowed. Many sites inline CSS or use same-origin sheets: iterate `document.styleSheets` / `cssRules` inside `try/catch`; for **cross-origin** sheets that throw on `cssRules`, copy the rule from the **Network** response or **Sources** panel in Chrome and paste into `docs/research/MOTION.md` / the component spec. Never substitute a different easing or keyframe shape “because it looks close.”
+- **Scroll-driven animations** — for `animation-timeline: view()` / named timelines, capture **`view-timeline` / `scroll-timeline` on ancestors**, `animation-range`, `scroll-padding` / snap containers, and **which scroll container** is the timeline root (often `html`, sometimes a nested `overflow-y: auto` div). **`getComputedStyle` support varies** for scroll-animation longhands; also read **`cs.getPropertyValue('view-timeline-name')`**, **`scroll-timeline-name`**, **`animation-timeline`**, etc., when camelCase mirrors are missing in the engine you’re using.
+- **Before/after pairs** — for scroll- or hover-driven motion, capture computed `transform`, `opacity`, and longhand `animation-*` / `transition-*` **in both states** (see §7) and the **exact trigger** (px, ratio, or event).
+- **Libraries** — if Lenis/GSAP/Framer is present, document **version/hooks** from **script `src` URLs** (path often includes version), `//# sourceMappingURL` / comment banners in the bundle if visible, global identifiers on `window` when safe to read, **npm lockfile** only if this repo vendors that script, and **class/DOM hooks** (e.g. `.lenis`). Sample **computed style** at rest vs. mid-animation after interactions.
+- **Deliverable** — maintain `docs/research/MOTION.md`: page-level keyframes inventory, global scroll/smooth-scroll setup, and per-section pointers into component specs. Large pages may scope the audit script to a **section root selector** to avoid noise.
+
+**Motion audit script** (run via Chrome MCP; optional `rootSelector` limits to a subtree):
+
+```javascript
+(function motionAudit(rootSelector) {
+  const root = rootSelector ? document.querySelector(rootSelector) : document.body;
+  if (!root) return JSON.stringify({ error: 'root not found: ' + rootSelector });
+
+  function safeRules(sheet) {
+    try {
+      return [...sheet.cssRules];
+    } catch {
+      return [];
+    }
+  }
+
+  const walkKeyframes = (rules, out) => {
+    for (const rule of rules) {
+      if (rule.type === CSSRule.KEYFRAMES_RULE) {
+        out.push({ name: rule.name, cssText: rule.cssText });
+      } else if (rule.type === CSSRule.MEDIA_RULE && rule.cssRules) {
+        walkKeyframes(rule.cssRules, out);
+      }
+    }
+  };
+
+  const keyframes = [];
+  for (const sheet of document.styleSheets) {
+    walkKeyframes(safeRules(sheet), keyframes);
+  }
+
+  const animated = [];
+  // Include `root` — querySelectorAll('*') misses animations on the section container itself
+  const scope = [root, ...root.querySelectorAll('*')];
+  for (const el of scope) {
+    const cs = getComputedStyle(el);
+    const animName = cs.animationName;
+    const hasAnim = animName && animName !== 'none';
+    const transDurs = (cs.transitionDuration || '')
+      .split(',')
+      .map((s) => s.trim())
+      .filter(Boolean);
+    const hasTrans =
+      cs.transitionProperty &&
+      cs.transitionProperty !== 'none' &&
+      transDurs.some((d) => d !== '0s' && d !== '0ms');
+    if (!hasAnim && !hasTrans) continue;
+
+    animated.push({
+      hint: el.tagName.toLowerCase() + (el.className
+        ? '.' + String(el.className).trim().split(/\s+/).slice(0, 4).join('.')
+        : ''),
+      animation: cs.animation,
+      animationName: cs.animationName,
+      animationDuration: cs.animationDuration,
+      animationTimingFunction: cs.animationTimingFunction,
+      animationDelay: cs.animationDelay,
+      animationIterationCount: cs.animationIterationCount,
+      animationDirection: cs.animationDirection,
+      animationFillMode: cs.animationFillMode,
+      animationPlayState: cs.animationPlayState,
+      animationTimeline: cs.animationTimeline,
+      animationRange: cs.animationRange,
+      transition: cs.transition,
+      transitionProperty: cs.transitionProperty,
+      transitionDuration: cs.transitionDuration,
+      transitionTimingFunction: cs.transitionTimingFunction,
+      transitionDelay: cs.transitionDelay,
+      transform: cs.transform,
+      transformOrigin: cs.transformOrigin,
+      opacity: cs.opacity,
+      willChange: cs.willChange,
+      viewTimelineName: cs.viewTimelineName,
+      scrollTimelineName: cs.scrollTimelineName,
+      viewTimelineNameRaw: cs.getPropertyValue('view-timeline-name'),
+      scrollTimelineNameRaw: cs.getPropertyValue('scroll-timeline-name')
+    });
+  }
+
+  return JSON.stringify(
+    {
+      prefersReducedMotion: window.matchMedia('(prefers-reduced-motion: reduce)').matches,
+      keyframes,
+      animatedElements: animated
+    },
+    null,
+    2
+  );
+})(''); // Pass section selector string, e.g. 'section.hero', instead of ''
+```
+
 ### Page Topology
 Map out every distinct section of the page from top to bottom. Give each a working name. Document:
 - Their visual order
@@ -266,7 +376,7 @@ For each section, use browser MCP to extract everything:
 
 1. **Screenshot** the section in isolation (scroll to it, screenshot the viewport). Save to `docs/design-references/`.
 
-2. **Extract CSS** for every element in the section. Use the extraction script below — don't hand-measure individual properties. Run it once per component container and capture the full output:
+2. **Extract CSS** for every element in the section. Use the extraction script below — don't hand-measure individual properties. Run it **once per spec scope**: usually the **section wrapper** selector (one subtree). For very large sections, run again on **inner selectors** (e.g. each card type) — the `depth` / `children.slice(0, 20)` limits are **deliberately capped** for MCP payload size; raise them or narrow `SELECTOR` when the spec is incomplete.
 
 ```javascript
 // Per-component extraction — run via browser MCP
@@ -285,13 +395,15 @@ For each section, use browser MCP to extract everything:
     'borderRadius','border','borderTop','borderBottom','borderLeft','borderRight',
     'boxShadow','overflow','overflowX','overflowY',
     'position','top','right','bottom','left','zIndex',
-    'opacity','transform','transition','cursor',
+    'opacity','transform','transformOrigin','transition','transitionProperty','transitionDuration','transitionTimingFunction','transitionDelay',
+    'animation','animationName','animationDuration','animationTimingFunction','animationDelay','animationIterationCount','animationDirection','animationFillMode','animationPlayState','animationTimeline','animationRange','viewTimelineName','scrollTimelineName','cursor',
     'objectFit','objectPosition','mixBlendMode','filter','backdropFilter',
     'whiteSpace','textOverflow','WebkitLineClamp'
   ];
   function extractStyles(element) {
     const cs = getComputedStyle(element);
     const styles = {};
+    // Heuristic filter — for layout-audits, re-add any dropped `auto` / `normal` / transparent values the spec calls out as significant
     props.forEach(p => { const v = cs[p]; if (v && v !== 'none' && v !== 'normal' && v !== 'auto' && v !== '0px' && v !== 'rgba(0, 0, 0, 0)') styles[p] = v; });
     return styles;
   }
@@ -364,6 +476,15 @@ For each section (or sub-component, if you're breaking it up), create a spec fil
 ### <Child element N>
 ...
 
+## Motion & animation (exact — from Chrome MCP `getComputedStyle` + stylesheet rules)
+
+- **Keyframe names in use:** ...
+- **Full `@keyframes` blocks** (paste `cssText` or equivalent); note **cross-origin** gaps and how you filled them
+- **Per-element:** shorthand/longhand `animation` and `transition` values **verbatim** for resting state
+- **Scroll/view timelines:** timeline name, range, scroll container, snap/observer thresholds
+- **Libraries:** Lenis / GSAP / Framer / Lottie — hooks, init pattern, timing copied from reference
+- **`prefers-reduced-motion`:** matched behavior on the reference
+
 ## States & Behaviors
 
 ### <Behavior name, e.g., "Scroll-triggered floating mode">
@@ -448,15 +569,17 @@ After assembly, do NOT declare the clone complete. Take side-by-side comparison
 
 1. Open the original site and your clone side-by-side (or take screenshots at the same viewport widths)
 2. Compare section by section, top to bottom, at desktop (1440px)
-3. Compare again at mobile (390px)
-4. For each discrepancy found:
+3. Compare again at tablet (768px) — same widths as **Responsive sweep**
+4. Compare again at mobile (390px)
+5. For each discrepancy found:
    - Check the component spec file — was the value extracted correctly?
    - If the spec was wrong: re-extract from browser MCP, update the spec, fix the component
    - If the spec was right but the builder got it wrong: fix the component to match the spec
-5. Test all interactive behaviors: scroll through the page, click every button/tab, hover over interactive elements
-6. Verify smooth scroll feels right, header transitions work, tab switching works, animations play
+6. Test all interactive behaviors: scroll through the page, click every button/tab, hover over interactive elements
+7. **Motion QA (Chrome MCP again if needed):** For every animated or transitioned element, re-run `getComputedStyle` on the reference vs. the clone at the **same scroll position / interaction state** and compare **`animation-*`, `transition-*`, `transform`, `opacity`** longhands — **resolved** durations/easings must match where the cascade specifies them (Tailwind classes are fine when they compile to the same longhands; verify in **Computed**, not by class name alone). Re-record any `@keyframes` the reference still exposes so the clone can be patched until timings align.
+8. Verify smooth scroll feels right, header transitions work, tab switching works, stagger and scroll-driven reveals match the reference
 
-Only after this visual QA pass is the clone complete.
+Only after this visual + motion QA pass is the clone complete.
 
 ## Pre-Dispatch Checklist
 
@@ -468,9 +591,10 @@ Before dispatching ANY builder agent, verify you can check every box. If you can
 - [ ] For stateful components: every state's content and styles are captured
 - [ ] For scroll-driven components: trigger threshold, before/after styles, and transition are recorded
 - [ ] For hover states: before/after values and transition timing are recorded
+- [ ] Motion: relevant `@keyframes` captured (or cross-origin gap documented with manual paste), `docs/research/MOTION.md` updated, component specs include **exact** `animation*` / `transition*` / timeline fields from Chrome MCP
 - [ ] All images in the section are identified (including overlays and layered compositions)
-- [ ] Responsive behavior is documented for at least desktop and mobile
-- [ ] Text content is verbatim from the site, not paraphrased
+- [ ] Responsive behavior is documented for desktop, tablet, and mobile (1440 / 768 / 390)
+- [ ] Text: **verbatim** from the reference **except** hero, main headings, and primary CTAs — those match the **SaaS idea** (reference copy still captured for audit if useful)
 - [ ] The builder prompt is under ~150 lines of spec; if over, the section needs to be split
 
 ## What NOT to Do

package/.github/skills/launchframe/SKILL.md

@@ -24,7 +24,9 @@ Before reconnaissance, write or update:
 
 ## SaaS copy overlay (Phase 4 assembly and final polish)
 
-After structure and styles match the reference, apply the **SaaS idea** to hero, headings, and primary CTAs where the reference uses interchangeable marketing copy, **without** changing layout grids, spacing, or motion from extracted specs. Respect third-party brands.
+After structure and styles match the reference, apply the **SaaS idea** to hero, headings, and primary CTAs where the reference uses interchangeable marketing copy, **without** changing layout grids, spacing, or motion from extracted specs. **Brand identity** (below) must be **original** for anything you ship as the user’s product — never pass off the reference company’s trademarks or distinctive marks.
+
+**Precedence:** For those surfaces (hero, main headings, primary CTAs), **final ship copy comes from the SaaS idea**, not the reference — still capture reference strings in research/specs if useful for QA diffs. Everywhere else, keep **verbatim** reference text unless the user overrides.
 
 ---
 
@@ -32,16 +34,17 @@ After structure and styles match the reference, apply the **SaaS idea** to hero,
 
 The target page(s) are the URL(s) you parsed in Pre-Flight. Clone exactly what's visible at each URL. Unless the user specifies otherwise, use these defaults:
 
-- **Fidelity level:** Pixel-perfect — exact match in colors, spacing, typography, animations
+- **Fidelity level:** Pixel-perfect **layout, spacing, typography scale, and motion** (durations, easings, keyframes, triggers) matched to the reference. **Colors** match where you are emulating neutral/UI chrome from the reference; where **Brand identity** applies, use the **new palette** and assets while keeping the same CSS structure (fills land on different tokens). **Animations** stay reference-faithful unless the user opts out.
 - **In scope:** Visual layout and styling, component structure and interactions, responsive design, mock data for demo purposes
 - **Out of scope:** Real backend / database, authentication, real-time features, SEO optimization, accessibility audit
 - **Customization:** Structure and visuals — pure emulation of the reference. **Marketing copy** — apply the parsed **SaaS idea** where hero/headlines/CTAs are interchangeable (see “SaaS copy overlay” above); do not invent a different product than the user’s idea.
+- **Brand identity:** The reference is a **pattern** for layout, motion, and UI craft — **not** permission to ship their brand. Unless the user **explicitly** asks for a faithful copy of the reference brand (e.g. licensed work, clearly labeled internal mock, private design audit), **invent an original brand** aligned with the SaaS idea: product name, wordmark or simple logomark (SVG or styled text) sized to the same logo slot, favicon / app icon, OG imagery, and a cohesive palette. Do **not** reuse their trademarked logo paths, mascot art, or distinctive illustrative brand assets; use originals or functional UI icons instead. Hero or lifestyle images that center the reference brand should be replaced with **original** imagery or neutral compositions that keep the **same layout rhythm**. **Keep** reference-faithful neutrals where they are clearly **non-brand** UI (borders, subtle grays, default body text color roles) unless they are unmistakably part of their distinctive palette. Note in `docs/research/LAUNCHFRAME.md` which marks and assets are **original brand** versus **layout-only** extraction.
 
 If the user provides additional instructions (specific fidelity level, customizations, extra context), honor those over the defaults.
 
 ## Pre-Flight
 
-1. **Browser automation is required.** Check for available browser MCP tools (Chrome MCP, Playwright MCP, Browserbase MCP, Puppeteer MCP, etc.). Use whichever is available — if multiple exist, prefer Chrome MCP. If none are detected, ask the user which browser tool they have and how to connect it. This skill cannot work without browser automation.
+1. **Browser automation is required.** Check for available browser MCP tools (Chrome MCP, Playwright MCP, Browserbase MCP, Puppeteer MCP, etc.). Use whichever is available — if multiple exist, **prefer Chrome DevTools MCP** for inspection: it maps to the same engine the user sees and preserves **computed `animation` / `transition` / scroll-driven** values accurately. If none are detected, ask the user which browser tool they have and how to connect it. This skill cannot work without browser automation. **Motion parity:** every pass (reconnaissance, per-section extract, QA) must treat **motion as first-class** — same **durations, delays, easings (`cubic-bezier` / steps), iteration counts, fill modes, directions, keyframe percentages, and scroll/view-timeline bindings** as the live site, not “similar” motion.
 2. **Parse arguments** — extract every `http://` / `https://` URL token (there may be several). **SaaS idea** = the remaining non-URL text (trim outer quotes). Normalize and validate each URL; if any are invalid, or the SaaS idea is missing, ask the user once. For each valid URL, verify it is accessible via your browser MCP tool.
 3. Verify the base project builds: `npm run build`. The Next.js + shadcn/ui + Tailwind v4 scaffold should already be in place. If not, tell the user to set it up first.
 4. Create the output directories if they don't exist: `docs/research/`, `docs/research/components/`, `docs/design-references/`, `scripts/`. For multiple clones, also prepare per-site folders like `docs/research/<hostname>/` and `docs/design-references/<hostname>/`.
@@ -57,7 +60,7 @@ When you traverse the DOM and the Network panel, do **not** treat all nodes equa
 
 1. **Images (raster + video stills)** — Enumerate `<img>`, `<picture>`, responsive `srcset`, `data-*` lazy URLs, **computed `background-image`** on the element and parents (including pseudo-elements), mask images, `<video poster>`, hero media. **Scrape:** download binary assets to `public/images/` (or `public/videos/`) with stable paths referenced in specs. **Create** a replacement PNG/WebP/SVG only when the asset is blocked (CORS, auth cookie, 403), ephemeral, or impossible to URL-fetch — use a high-DPI screenshot crop, traced artwork, or CSS gradient approximation, and mark `ASSET_SOURCE: generated` in the component spec with a short reason.
 2. **SVGs & iconography** — Inline `<svg>`, sprite `symbol` defs, **SVG used as masks/filters**, icon fonts (prefer path extraction). Convert to `@/components/icons.tsx` (or section-local components) with meaningful names. Prioritize crisp edges and correct `viewBox` over shrinking bundle size during emulation.
-3. **Motion & animation** — CSS `@keyframes`, `animation`, `animation-timeline`, `transition`, `transform`, will-change hints; JS-driven motion (carousel timing, IntersectionObserver reveals); libraries (GSAP, Framer, Lottie JSON, Lenis). Capture **numbers** (ms, easing curves, stagger, scroll thresholds), not adjectives. Include **reduced-motion** behavior if present.
+3. **Motion & animation** — CSS `@keyframes`, `animation`, `animation-timeline` / `view-timeline` / `animation-range`, `transition`, `transform`, `transform-origin`, will-change; JS-driven motion (carousel timing, IntersectionObserver reveals); libraries (GSAP, Framer, Lottie JSON, Lenis). Capture **numbers** (ms, `cubic-bezier()`, `steps()`, stagger, scroll thresholds, **named keyframe blocks**), not adjectives — paste **verbatim** `cssText` for relevant `@keyframes` into specs when obtainable. Include **reduced-motion** (`matchMedia('(prefers-reduced-motion: reduce)'))` behavior if present.
 
 Only after the above are accounted for should you spend cycle time on minor text or non-visual refactors. A perfect grid with missing hero art and dead animation still fails the clone.
 
@@ -77,6 +80,8 @@ Look at each section and judge its complexity. A simple banner with a heading an
 
 Extract the actual text, images, videos, and SVGs from the live site. This is a clone, not a mockup. Use `element.textContent`, download every `<img>` and `<video>`, extract inline `<svg>` elements as React components. The only time you generate content is when something is clearly server-generated and unique per session.
 
+**Marketing surfaces** (hero, primary headings, main CTAs) follow the **SaaS copy overlay** and **Brand identity** rules — capture reference copy for audit, but **ship** the user’s idea there.
+
 **Prioritize** (see §0): downloadable imagery and backgrounds first, then SVG/icon layers, then motion. If you must **fabricate** an asset, prefer screenshot-based exports or traced vectors tied to measured box sizes — avoid unrelated stock art.
 
 **Layered assets matter.** A section that looks like one image is often multiple layers — a background watercolor/gradient, a foreground UI mockup PNG, an overlay icon. Inspect each container's full DOM tree and enumerate ALL `<img>` elements and background images within it, including absolutely-positioned overlays. Missing an overlay image makes the clone look empty even if the background is correct.
@@ -192,8 +197,113 @@ This is a dedicated pass AFTER screenshots and BEFORE anything else. Its purpose
 - Mobile: 390px
 - At each width, note which sections change layout (column → stack, sidebar disappears, etc.) and at approximately which breakpoint the change occurs.
 
+Re-check **all three widths** again in **Phase 5: Visual QA Diff** so tablet regressions are not skipped.
+
 Save all findings to `docs/research/BEHAVIORS.md`. This is your behavior bible — reference it when writing every component spec.
 
+### Chrome MCP: precise motion & animation extraction
+
+Use **evaluate script** (or equivalent) in Chrome MCP **during** the scroll/click/hover sweeps so you capture **live computed values**, not guesses from DevTools screenshots alone.
+
+**Rules:**
+
+- **No hand-waving** — if the reference uses `0.45s cubic-bezier(0.4, 0, 0.2, 1)`, the spec and implementation use that exact string (or Tailwind utilities **only** when the **resolved computed** animation/transition longhands match — class names alone are not proof).
+- **`@keyframes` source of truth** — for each animated element, record `getComputedStyle(el).animationName` and resolve the **full `@keyframes` rule** from stylesheets when allowed. Many sites inline CSS or use same-origin sheets: iterate `document.styleSheets` / `cssRules` inside `try/catch`; for **cross-origin** sheets that throw on `cssRules`, copy the rule from the **Network** response or **Sources** panel in Chrome and paste into `docs/research/MOTION.md` / the component spec. Never substitute a different easing or keyframe shape “because it looks close.”
+- **Scroll-driven animations** — for `animation-timeline: view()` / named timelines, capture **`view-timeline` / `scroll-timeline` on ancestors**, `animation-range`, `scroll-padding` / snap containers, and **which scroll container** is the timeline root (often `html`, sometimes a nested `overflow-y: auto` div). **`getComputedStyle` support varies** for scroll-animation longhands; also read **`cs.getPropertyValue('view-timeline-name')`**, **`scroll-timeline-name`**, **`animation-timeline`**, etc., when camelCase mirrors are missing in the engine you’re using.
+- **Before/after pairs** — for scroll- or hover-driven motion, capture computed `transform`, `opacity`, and longhand `animation-*` / `transition-*` **in both states** (see §7) and the **exact trigger** (px, ratio, or event).
+- **Libraries** — if Lenis/GSAP/Framer is present, document **version/hooks** from **script `src` URLs** (path often includes version), `//# sourceMappingURL` / comment banners in the bundle if visible, global identifiers on `window` when safe to read, **npm lockfile** only if this repo vendors that script, and **class/DOM hooks** (e.g. `.lenis`). Sample **computed style** at rest vs. mid-animation after interactions.
+- **Deliverable** — maintain `docs/research/MOTION.md`: page-level keyframes inventory, global scroll/smooth-scroll setup, and per-section pointers into component specs. Large pages may scope the audit script to a **section root selector** to avoid noise.
+
+**Motion audit script** (run via Chrome MCP; optional `rootSelector` limits to a subtree):
+
+```javascript
+(function motionAudit(rootSelector) {
+  const root = rootSelector ? document.querySelector(rootSelector) : document.body;
+  if (!root) return JSON.stringify({ error: 'root not found: ' + rootSelector });
+
+  function safeRules(sheet) {
+    try {
+      return [...sheet.cssRules];
+    } catch {
+      return [];
+    }
+  }
+
+  const walkKeyframes = (rules, out) => {
+    for (const rule of rules) {
+      if (rule.type === CSSRule.KEYFRAMES_RULE) {
+        out.push({ name: rule.name, cssText: rule.cssText });
+      } else if (rule.type === CSSRule.MEDIA_RULE && rule.cssRules) {
+        walkKeyframes(rule.cssRules, out);
+      }
+    }
+  };
+
+  const keyframes = [];
+  for (const sheet of document.styleSheets) {
+    walkKeyframes(safeRules(sheet), keyframes);
+  }
+
+  const animated = [];
+  // Include `root` — querySelectorAll('*') misses animations on the section container itself
+  const scope = [root, ...root.querySelectorAll('*')];
+  for (const el of scope) {
+    const cs = getComputedStyle(el);
+    const animName = cs.animationName;
+    const hasAnim = animName && animName !== 'none';
+    const transDurs = (cs.transitionDuration || '')
+      .split(',')
+      .map((s) => s.trim())
+      .filter(Boolean);
+    const hasTrans =
+      cs.transitionProperty &&
+      cs.transitionProperty !== 'none' &&
+      transDurs.some((d) => d !== '0s' && d !== '0ms');
+    if (!hasAnim && !hasTrans) continue;
+
+    animated.push({
+      hint: el.tagName.toLowerCase() + (el.className
+        ? '.' + String(el.className).trim().split(/\s+/).slice(0, 4).join('.')
+        : ''),
+      animation: cs.animation,
+      animationName: cs.animationName,
+      animationDuration: cs.animationDuration,
+      animationTimingFunction: cs.animationTimingFunction,
+      animationDelay: cs.animationDelay,
+      animationIterationCount: cs.animationIterationCount,
+      animationDirection: cs.animationDirection,
+      animationFillMode: cs.animationFillMode,
+      animationPlayState: cs.animationPlayState,
+      animationTimeline: cs.animationTimeline,
+      animationRange: cs.animationRange,
+      transition: cs.transition,
+      transitionProperty: cs.transitionProperty,
+      transitionDuration: cs.transitionDuration,
+      transitionTimingFunction: cs.transitionTimingFunction,
+      transitionDelay: cs.transitionDelay,
+      transform: cs.transform,
+      transformOrigin: cs.transformOrigin,
+      opacity: cs.opacity,
+      willChange: cs.willChange,
+      viewTimelineName: cs.viewTimelineName,
+      scrollTimelineName: cs.scrollTimelineName,
+      viewTimelineNameRaw: cs.getPropertyValue('view-timeline-name'),
+      scrollTimelineNameRaw: cs.getPropertyValue('scroll-timeline-name')
+    });
+  }
+
+  return JSON.stringify(
+    {
+      prefersReducedMotion: window.matchMedia('(prefers-reduced-motion: reduce)').matches,
+      keyframes,
+      animatedElements: animated
+    },
+    null,
+    2
+  );
+})(''); // Pass section selector string, e.g. 'section.hero', instead of ''
+```
+
 ### Page Topology
 Map out every distinct section of the page from top to bottom. Give each a working name. Document:
 - Their visual order
@@ -265,7 +375,7 @@ For each section, use browser MCP to extract everything:
 
 1. **Screenshot** the section in isolation (scroll to it, screenshot the viewport). Save to `docs/design-references/`.
 
-2. **Extract CSS** for every element in the section. Use the extraction script below — don't hand-measure individual properties. Run it once per component container and capture the full output:
+2. **Extract CSS** for every element in the section. Use the extraction script below — don't hand-measure individual properties. Run it **once per spec scope**: usually the **section wrapper** selector (one subtree). For very large sections, run again on **inner selectors** (e.g. each card type) — the `depth` / `children.slice(0, 20)` limits are **deliberately capped** for MCP payload size; raise them or narrow `SELECTOR` when the spec is incomplete.
 
 ```javascript
 // Per-component extraction — run via browser MCP
@@ -284,13 +394,15 @@ For each section, use browser MCP to extract everything:
     'borderRadius','border','borderTop','borderBottom','borderLeft','borderRight',
     'boxShadow','overflow','overflowX','overflowY',
     'position','top','right','bottom','left','zIndex',
-    'opacity','transform','transition','cursor',
+    'opacity','transform','transformOrigin','transition','transitionProperty','transitionDuration','transitionTimingFunction','transitionDelay',
+    'animation','animationName','animationDuration','animationTimingFunction','animationDelay','animationIterationCount','animationDirection','animationFillMode','animationPlayState','animationTimeline','animationRange','viewTimelineName','scrollTimelineName','cursor',
     'objectFit','objectPosition','mixBlendMode','filter','backdropFilter',
     'whiteSpace','textOverflow','WebkitLineClamp'
   ];
   function extractStyles(element) {
     const cs = getComputedStyle(element);
     const styles = {};
+    // Heuristic filter — for layout-audits, re-add any dropped `auto` / `normal` / transparent values the spec calls out as significant
     props.forEach(p => { const v = cs[p]; if (v && v !== 'none' && v !== 'normal' && v !== 'auto' && v !== '0px' && v !== 'rgba(0, 0, 0, 0)') styles[p] = v; });
     return styles;
   }
@@ -363,6 +475,15 @@ For each section (or sub-component, if you're breaking it up), create a spec fil
 ### <Child element N>
 ...
 
+## Motion & animation (exact — from Chrome MCP `getComputedStyle` + stylesheet rules)
+
+- **Keyframe names in use:** ...
+- **Full `@keyframes` blocks** (paste `cssText` or equivalent); note **cross-origin** gaps and how you filled them
+- **Per-element:** shorthand/longhand `animation` and `transition` values **verbatim** for resting state
+- **Scroll/view timelines:** timeline name, range, scroll container, snap/observer thresholds
+- **Libraries:** Lenis / GSAP / Framer / Lottie — hooks, init pattern, timing copied from reference
+- **`prefers-reduced-motion`:** matched behavior on the reference
+
 ## States & Behaviors
 
 ### <Behavior name, e.g., "Scroll-triggered floating mode">
@@ -447,15 +568,17 @@ After assembly, do NOT declare the clone complete. Take side-by-side comparison
 
 1. Open the original site and your clone side-by-side (or take screenshots at the same viewport widths)
 2. Compare section by section, top to bottom, at desktop (1440px)
-3. Compare again at mobile (390px)
-4. For each discrepancy found:
+3. Compare again at tablet (768px) — same widths as **Responsive sweep**
+4. Compare again at mobile (390px)
+5. For each discrepancy found:
    - Check the component spec file — was the value extracted correctly?
    - If the spec was wrong: re-extract from browser MCP, update the spec, fix the component
    - If the spec was right but the builder got it wrong: fix the component to match the spec
-5. Test all interactive behaviors: scroll through the page, click every button/tab, hover over interactive elements
-6. Verify smooth scroll feels right, header transitions work, tab switching works, animations play
+6. Test all interactive behaviors: scroll through the page, click every button/tab, hover over interactive elements
+7. **Motion QA (Chrome MCP again if needed):** For every animated or transitioned element, re-run `getComputedStyle` on the reference vs. the clone at the **same scroll position / interaction state** and compare **`animation-*`, `transition-*`, `transform`, `opacity`** longhands — **resolved** durations/easings must match where the cascade specifies them (Tailwind classes are fine when they compile to the same longhands; verify in **Computed**, not by class name alone). Re-record any `@keyframes` the reference still exposes so the clone can be patched until timings align.
+8. Verify smooth scroll feels right, header transitions work, tab switching works, stagger and scroll-driven reveals match the reference
 
-Only after this visual QA pass is the clone complete.
+Only after this visual + motion QA pass is the clone complete.
 
 ## Pre-Dispatch Checklist
 
@@ -467,9 +590,10 @@ Before dispatching ANY builder agent, verify you can check every box. If you can
 - [ ] For stateful components: every state's content and styles are captured
 - [ ] For scroll-driven components: trigger threshold, before/after styles, and transition are recorded
 - [ ] For hover states: before/after values and transition timing are recorded
+- [ ] Motion: relevant `@keyframes` captured (or cross-origin gap documented with manual paste), `docs/research/MOTION.md` updated, component specs include **exact** `animation*` / `transition*` / timeline fields from Chrome MCP
 - [ ] All images in the section are identified (including overlays and layered compositions)
-- [ ] Responsive behavior is documented for at least desktop and mobile
-- [ ] Text content is verbatim from the site, not paraphrased
+- [ ] Responsive behavior is documented for desktop, tablet, and mobile (1440 / 768 / 390)
+- [ ] Text: **verbatim** from the reference **except** hero, main headings, and primary CTAs — those match the **SaaS idea** (reference copy still captured for audit if useful)
 - [ ] The builder prompt is under ~150 lines of spec; if over, the section needs to be split
 
 ## What NOT to Do