AI summariser explainer — Remotion prompt (long doc in, summary out)

<direction> A 9-second AI tool explainer in Remotion (1280x720, 270 frames at 30fps). House style: near-black #0a0a0a background, panels #141414, borders #2a2a2a, text #ffffff/#c9c9c9, ONE accent #ff5c1a, Arial/Helvetica bold, no webfonts. The demo IS the explanation: a dense document on the left, one button, a three-bullet summary on the right. Fictional tool; the document, summary and timing are labelled samples/demo in the film. No gradients, no stock photos, no real brand logos, no lorem ipsum, no purple/blue tech gradient. </direction> <structure> Frames 0-96 — Kicker "AI TOOL EXPLAINER — NoteShrink". Headline: "Long doc in. Short answer out." Left: a document card ("Q3 FIELD REPORT.PDF", "2,400 words · 12-minute read") filled with grey text lines. Centre: a SUMMARISE pill. Frames 96-140 — The pill pulses once; the document dims and shrinks slightly — the machine is "reading". Frames 140-196 — The summary card lands right (accent border): three bullets, each a complete, specific sentence (a result, a problem, a decision) — never "the document discusses various topics". Frames 196-270 — The savings chip lands bottom-left: "12 MIN READ → 40 SEC (DEMO)", beside the fictional fine print. </structure> <build> One component; all motion from useCurrentFrame with clamped interpolate. The document's lines are a fixed array of widths mapped to divs — count them against the card height BEFORE writing the rest (see gotchas). Bullets are real sentences in the JSX, not lorem bars: the summary's specificity is the product demo. </build> <gotchas> - Iteration 1: fourteen text lines overflowed the document card's bottom border — the card is 430px; header + 14 lines + padding is ~514px. Count line height × lines + header + padding first; ten lines fit. Fixed in iteration 2. - Summary bullets must contain information, not meta-language — if a bullet could describe any document, rewrite it. - The (DEMO) tag on the timing chip is mandatory in adaptations until the timing is measured on the real tool. </gotchas> Before you finish: step through the timeline at five points and fix anything that overlaps, clips the frame, or drifts off the beat grid.