Skip to content

Production-ready animations, transitions, backgrounds, and scenes for Remotion

feat: added new good/bad rules

dev_wandry93713cd60a02
diff --git a/skills/remocn/SKILL.md b/skills/remocn/SKILL.md
index 6eefe5ba..697a10c1 100644
--- a/skills/remocn/SKILL.md
+++ b/skills/remocn/SKILL.md
@@ -164,7 +164,7 @@ Don't dump components — compose one story. When asked to build a full video ("
`references/anatomy.md` §1.
2. **Follow the beats** — a product demo is Hook → Positioning → Product reveal → Features → Proof →
CTA (last two optional). See `references/anatomy.md` §2.
-3. **Use the recipe** — `references/archetypes.md` has the per-archetype build: content contract
+3. **Use the recipe** — `references/archetypes/index.md` routes to per-archetype builds: content contract
(infer → ask → placeholder), duration variants, beat→component slots, and a worked
`<TransitionSeries>` skeleton.
4. **Pick each beat's component** from `references/components/index.md`; match the `vibe` tag to the
@@ -175,7 +175,7 @@ Don't dump components — compose one story. When asked to build a full video ("
## Reference
- `references/anatomy.md` — composing a full video: strategy (template/compose/new), the product-demo beats, and the good-vs-slop quality bar.
-- `references/archetypes.md` — per-archetype build recipes (currently product-demo): content contract, duration variants, beat→slot map, worked `<TransitionSeries>` skeleton.
+- `references/archetypes/index.md` — router to per-archetype build recipes (product-demo flagship + changelog, feature-announcement, oss-showcase, cli-tool-demo, testimonial-reel, year-in-review, pricing-reveal, logo-bumper): content contract, duration variants, beat→slot map.
- `references/components/index.md` — router table (all components, grouped by category, with `Use for` / `Avoid for`). Open `references/components/<name>.md` for one component's full props, example, and use / don't-use notes.
- `references/design.md` — anti-slop design defaults (do/avoid) + design tokens (palette, fonts, canvas).
- `references/motion-principles.md` — motion-design principles adapted to remocn + Remotion.
diff --git a/skills/remocn/references/anatomy.md b/skills/remocn/references/anatomy.md
index e8fc87e3..f3ed1d04 100644
--- a/skills/remocn/references/anatomy.md
+++ b/skills/remocn/references/anatomy.md
@@ -1,7 +1,7 @@
# Video Anatomy & Composition Strategy
How to turn "make a product demo with remocn" into a coherent video. Read this before composing.
-The component catalog is `components/index.md`; the per-archetype recipe is `archetypes.md`.
+The component catalog is `components/index.md`; the per-archetype recipes are in `archetypes/` (start at `archetypes/index.md`).
This file has three layers, kept separate:
1. **Strategy** — template vs compose vs build-new.
@@ -26,7 +26,7 @@ Don't use a template when the user's content or brand can't fit its fixed slots,
- The needed structure is a sequence of existing components (hook → product UI → proof → CTA) with no exotic choreography.
- Speed and fit matter more than a pixel-locked recreation.
-This is the primary path. Output is a raw `<TransitionSeries>` orchestrator stitching installed components — see `archetypes.md`.
+This is the primary path. Output is a raw `<TransitionSeries>` orchestrator stitching installed components — see `archetypes/index.md`.
### Build a new lightweight component when
- A beat needs a visual the catalog lacks (a specific product-UI frame, a chart type) **and** it will be reused across videos (e.g. a generic `ui-frame`, a `metric-card`, a `task-card`).
@@ -55,7 +55,7 @@ The hook usually carries the single hardest idea; features are where most of the
## 3. Good vs slop — the quality bar
-Derived from real reference demos. The good ones (CrowdReply, Flowith, HeyGen, monid, shadcn-sidebar) share a language; the bad ones (a component-catalog dump, two shadcn promos, an over-long slide tool) share failure modes.
+Derived from real reference demos. The good ones (CrowdReply, Flowith, HeyGen, monid, shadcn-sidebar, Claude Code Security, Notion Agents/Sites, React Bits) share a language; the bad ones (a component-catalog dump, shadcn promos, an over-long slide tool, fractal/openpaper/ChatJS/SlidesAI/itshover/dito) share failure modes. The line is often *restraint and legibility*, not the presence of any one effect.
### Good — do these
- **One accent color per video.** Everything else neutral (mono / cream / dark). Good demos pick exactly one (orange, yellow, teal, blue) and use it only on the emphasized word, the active number, and the CTA.
@@ -67,9 +67,11 @@ Derived from real reference demos. The good ones (CrowdReply, Flowith, HeyGen, m
- **A number/score payoff** with the accent, when there's a metric to land.
- **A calm logo lockup outro.** Optionally on a dark hold; keep it restrained.
- **Tight runtime with overlapping beats.** ~18s (short) to ~45s (standard). Length comes from story, not from listing.
+- **Show the product large and legible.** The UI sim fills the frame and reads clearly (Claude Code Security's scan→findings→fix→PR, Notion's populated dashboard) — the product is the hero, not a distant window.
+- **Long videos ride a narrative thread.** If it must run 60s+, carry it with a character / story (good Notion demo: the "Bug Wrangler" agent doing real tasks), never a feature list.
### Slop — never do these (each seen in a bad reference)
-- **No decorative glow / radial halos behind type.** Soft purple/lavender glow clouds behind headings (both shadcn promos do this) are the #1 tell. The hook gets life from motion and the accent, not a halo. See `design.md`, [no decorative glows].
+- **Keep gradients / glow restrained — small and subtle, never large or dominant.** This is about *dosage*, not presence. A small, sparing gradient accent is fine (good_04 React Bits — restrained, not big, not much of it). Slop is a *large, saturated, full-frame* gradient wash (bad_04's hot-pink background) or a soft radial **halo behind headings** (both shadcn promos — the #1 tell). The hook gets life from motion and the accent, not a glow blob. See `design.md`, [no decorative glows].
- **No feature-list / catalog enumeration.** Naming feature after feature ("Row Selection", "Pagination", "Sorting"…) over the same screenshot, or dumping every component in a gallery, is not a video — it has no narrative. Tell one problem → solution → proof story instead.
- **No placeholder / lorem content.** "Scene A", "Scene B", "First", "Your UI", "Selected element", `TASK-####` filler. If real content is missing, use honest English placeholders the user will obviously replace — never ship lorem as the final.
- **No ALL-CAPS heavy blocks, no decorative letter-spacing, no gradient text.** (A red ALL-CAPS "VISUAL EDITOR" block is slop.) See `design.md`.
@@ -77,6 +79,10 @@ Derived from real reference demos. The good ones (CrowdReply, Flowith, HeyGen, m
- **No monotony.** Don't repeat the same slide/screenshot under different labels. Each beat must advance the story.
- **Don't run long by enumerating.** 100s+ of feature-listing drags. If the content is genuinely long, give it a strong repeating rhythmic device (e.g. a question→answer cadence) or split into multiple videos.
- **No `mesh-gradient-bg`** as a hero background. Use `dynamic-grid`, `spotlight-card`, or a solid theme color via `backdrop`.
+- **Show the product big and legible.** Don't render the UI near-black / low-contrast (bad_01 fractal, bad_03 ChatJS), shrink it to a distant floating window, or float it over a photographic background (bad_02 openpaper). The viewer must be able to read the product — it's the hero.
+- **No raw screen-recording with browser / OS chrome.** Use a clean product sim cropped to the content, not an un-styled screencast of a real browser tab (bad_04 SlidesAI).
+- **No casual / throwaway copy.** "?????", ";)", "link in bio :)", lazy filler (bad_05 itshover) reads unfinished. Keep copy crisp and professional. All English.
+- **One accent, not per-brand colors.** Don't tint each word a different platform's brand color (bad_06: Instagram-pink + Twitter-blue + LinkedIn-blue in one line). One accent across the whole video.
### The one-line test
A good product demo could be described as *"X has problem Y; here's the product solving it, here's proof, here's how to get it."* If your composition is instead *"here are my components / here are my features,"* it's slop — restructure around a story.
diff --git a/skills/remocn/references/archetypes/changelog.md b/skills/remocn/references/archetypes/changelog.md
new file mode 100644
index 00000000..ec787548
--- /dev/null
+++ b/skills/remocn/references/archetypes/changelog.md
@@ -0,0 +1,52 @@
+# changelog
+
+**Family:** B. Release & Updates · **Default duration:** ~9s (270f @30fps, scales with item count N) · **Format:** 16:9 · **Vibe:** clean
+
+A regular-release recap: show the version number and a human-readable list of changes (Added / Fixed /
+Changed), close on a footer with a link and date. Calm and legible — the list must read, not dazzle.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+A short 3-beat specialization of the anatomy (Positioning → Features → CTA). Duration scales with N:
+`total ≈ 60 (badge) + clamp(N*24, 96, 200) (list) + 70 (footer) − 2*12 overlap`. N=4 → ~270f.
+
+| Frames (N=4) | Beat | What happens |
+|---|---|---|
+| 0–60 | **Version badge** | version chip slides into the top-left, date right; "What's new" builds via `tracking-in` |
+| 60–160 | **Change list** | N rows, each a category tag (Added/Fixed/Changed) + text; staggered in, ~9f apart |
+| 160–270 | **Footer / CTA** | small version chip, link/CTA fades in, optional release-progress indicator |
+
+Transitions: badge→list `shared-axis-y` (spring, 12f); list→footer `fade-through` (linear, 12f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Version badge | `tracking-in` (title), `dynamic-grid` (static low-opacity bg) | **`version-badge`** — version chip + date (build per `../anatomy.md` §1) |
+| Change list | `staggered-fade-up` (rows), `spring-scale-in` (tags) | **`change-list`** — renders `{tag,text}[]` with a tag→color map (Added=green, Fixed=amber, Changed=blue) and auto-stagger + "+M more" truncation; **`category-tag`** — fixed-width monospace category chip (reused in patch-notes) |
+| Footer / CTA | `soft-blur-in` (link), `micro-scale-fade` (chip), `progress-steps` (optional release indicator) | a small footer/CTA scene if none fits |
+
+The change-list / version-badge / category-tag don't exist in the catalog yet — they're reusable
+across release archetypes, so build them as lightweight components (anatomy §1, "build new"), not one-offs.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `version` | yes | infer from `package.json` / latest git tag |
+| `date` | yes | release date |
+| `changes[]` | yes | `{ tag: "Added"\|"Fixed"\|"Changed", text }` — infer from `CHANGELOG.md` / merged PR titles |
+| `link` | no | full-notes URL / CTA |
+| `brand` | no | `{ accent, background }` → one accent on a neutral canvas |
+
+`[N]` archetype: the list scene stretches linearly with the number of changes; cap visible rows and
+fold the rest into "+M more" rather than shrinking type.
+
+## Notes
+
+- **Background stays static.** A low-opacity `dynamic-grid` (≈0.06) with no motion, or a solid theme
+ fill — the list is the focus; don't animate the backdrop under reading text.
+- One accent only; the tag colors (green/amber/blue) are semantic, not decoration — keep them muted.
+- Real change text from the repo, never `Scene A` / lorem. All copy English.
+- This is a list archetype — guard against the slop trap of enumerating forever: cap rows, keep it ~9s.
diff --git a/skills/remocn/references/archetypes/cli-tool-demo.md b/skills/remocn/references/archetypes/cli-tool-demo.md
new file mode 100644
index 00000000..465c122d
--- /dev/null
+++ b/skills/remocn/references/archetypes/cli-tool-demo.md
@@ -0,0 +1,79 @@
+# cli-tool-demo
+
+**Family:** D. Developer/OSS · **Default duration:** ~45s (1350f @30fps, short ~18s/540f) · **Format:** 16:9 · **Vibe:** tech
+
+Demo a CLI or dev tool by running a real command to a visible result. The terminal is the product surface — show a
+believable command typed, output streaming line by line as instant steps, and the final artifact or success state.
+Two variants: short (social clip, grounded in monid ~18s) and standard (launch / conference ~43s).
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+### Short (~18s / 540f)
+
+`hook → terminal run → result → sign-off`
+
+| Frames | Beat | What happens |
+|---|---|---|
+| 0–90 | **Hook** | Value line builds word by word; one accent word lands; generous whitespace |
+| 90–360 | **Terminal run** | Terminal types the command char by char; output lines appear as instant step-function steps (~6f apart); final `✓ Done` line highlighted |
+| 360–480 | **Result** | Success callout — a metric, file count, or elapsed time — lands with the accent; plain dark hold if no visual artifact |
+| 480–540 | **Sign-off** | Logo cluster on calm dark hold |
+
+Transitions: hook→terminal `directional-wipe` down (20f); terminal→result `shared-axis-z` (spring, terminal recedes into depth); result→sign-off `fade-through` (16f).
+
+### Standard (~45s / 1350f)
+
+`hook → agent chat → terminal run → value line → result reveal → sign-off`
+
+| Frames | Beat | What happens |
+|---|---|---|
+| 0–150 | **Hook** | Problem statement or bold positioning line — kinetic word-by-word build, one accent |
+| 150–420 | **Agent chat** | Prompt typed in the matching agent surface; cursor blinks; response or task list begins streaming |
+| 420–900 | **Terminal run** | Command types in; progress output scrolls as instant step-function steps; numbers (file count, elapsed ms) tick up; final success line highlighted in green |
+| 900–1050 | **Value line** | Outcome statement — "All finished" / "Don't get blocked by your machine" style; per-word swap or kinetic build; accent on the key phrase |
+| 1050–1260 | **Result reveal** | Pipeline steps completing OR result artifact visible; plain dark hold if result needs no visual |
+| 1260–1350 | **Sign-off** | Logo cluster fades in on dark hold |
+
+Transitions: hook→chat `fade-through` (16f); chat→terminal `directional-wipe` down (20f); terminal→value-line `shared-axis-z` (spring, terminal recedes into depth); value-line→result `spatial-push` (24f); result→sign-off `fade-through` (16f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Hook | `kinetic-center-build` (headline), `inline-highlight` (accent word), `dynamic-grid` (0.06 opacity static bg) | — |
+| Agent chat | `claude-code` / `opencode` / `v0` / `chat-gpt` / `claude-chat` (match the tool's ecosystem), `cursor` (pointer to input field) | — |
+| Terminal run | `terminal-simulator` (hero — scroll is an instant step-function, never eased), `staggered-fade-up` (output rows, 6f apart), `rolling-number` (inline numbers — file count, elapsed time), `marker-highlight` (green sweep on the final `✓` line) | — |
+| Value line | `per-word-crossfade` (A→B two-phrase swap) or `kinetic-center-build` (single statement build), `inline-highlight` (accent phrase) | — |
+| Result — pipeline | `progress-steps` (CI/pipeline steps completing) | — |
+| Result — web artifact | `spring-scale-in` (window entrance), `typewriter` (address bar), `soft-blur-in` (content inside) | **`browser-frame`** — lightweight browser chrome (traffic-light buttons + address bar) wrapping a screenshot or child content; entrance `spring-scale-in` on the frame itself; address bar types with `typewriter`; child content enters with `soft-blur-in`; props: `url: string`, `screenshot?: string`, `children?: ReactNode`, `chrome?: 'mac' | 'minimal'` (default `'mac'`), `accent?: string`; the chrome strip is the only opaque element — content stays transparent |
+| Sign-off | `logo-enter` (logo cluster), `micro-scale-fade` (product name label) | — |
+
+`browser-frame` is reusable across D-family archetypes (cli-tool-demo, product-demo, changelog). Build it as a lightweight component per `../anatomy.md` §1, not a one-off.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `toolName` | yes | Product name, e.g. `vercel-snap`, `bun`, `remocn` |
+| `tagline` | yes | One phrase — what the tool does in plain language |
+| `command` | yes | Exact shell command to type, e.g. `npx vercel-snap build --prod` |
+| `outputLines[]` | yes | 3–6 log lines; last line is the success line (prefix `✓`); include 1–2 numbers (file count, time) for `rolling-number`; never real transcript walls |
+| `resultType` | yes | `"pipeline"` → `progress-steps`; `"web"` → **`browser-frame`** (build new); `"metric"` → `rolling-number` + label; `"none"` → skip result beat |
+| `agentSurface` | no (standard only) | `"claude-code"` \| `"opencode"` \| `"chat-gpt"` \| `"v0"` \| `"claude-chat"` — omit to skip the chat beat entirely |
+| `prompt` | no (standard only) | Prompt text typed in the agent surface when `agentSurface` is set |
+| `hookLine` | no | Override the hook headline; defaults to `tagline` |
+| `accent` | no | One hex; default `#22D3A6`; applied to success line highlight, accent word, logo — nowhere else |
+| `font` | no | Monospace font for the terminal; default `JetBrains Mono` |
+| `logo` | no | Path or URL for sign-off; omit for text-only wordmark via `micro-scale-fade` |
+
+## Notes
+
+- **Terminal scroll is a step-function, never eased.** Each output line appears at its exact frame — no interpolated opacity ramp on the terminal window or its scroll position. Easing belongs to the value line and scene transitions, not the log stream. This is a hard constraint of `terminal-simulator`.
+- **Show 3–6 output lines maximum.** Pick the most readable step names and the success line; cut everything else. A wall of log text reads as noise, not credibility.
+- **Numbers inside the output use `rolling-number` inline.** File count, elapsed time, bundle size — these small payoffs make the terminal feel live. One or two numbers per output section; not every line.
+- **One accent color throughout.** The `✓ Done` line highlight, the hook's emphasis word, and the logo share exactly one accent. All other text stays neutral mono on dark.
+- **Background stays static.** `dynamic-grid` at 0.06 opacity or a solid theme fill — never animated under the terminal. The terminal is the focal point; the background must not compete.
+- **Agent chat beat is optional.** Include it in the standard variant when the tool is AI-powered or agentic. Skip it (and use the short structure) when the tool is a pure CLI with no AI surface — adding a chat beat to a Rust CLI just to fill time is slop.
+- **Pick the agent surface to match the tool's ecosystem.** A Claude-powered tool → `claude-code`. An OpenCode workflow → `opencode`. A web-generation tool → `v0`. Mismatching brand surfaces undermines credibility.
+- **`browser-frame` must be built before any video using `resultType: "web"`.** It does not exist in the catalog; flag it at composition time and build per `../anatomy.md` §1. It is reusable — worth building, not a one-off.
diff --git a/skills/remocn/references/archetypes/feature-announcement.md b/skills/remocn/references/archetypes/feature-announcement.md
new file mode 100644
index 00000000..5639d538
--- /dev/null
+++ b/skills/remocn/references/archetypes/feature-announcement.md
@@ -0,0 +1,46 @@
+# feature-announcement
+
+**Family:** A. Product & Launch · **Default duration:** ~12s (360f @30fps) · **Format:** 16:9 · **Vibe:** premium
+
+A single-feature reveal: a quiet kicker sets expectation, the feature name arrives at full scale with a spotlight, then one benefit line lands with an accent highlight on the key word. Three beats, one idea — this is "Introducing X" for a tweet or changelog banner, not a feature list.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+Fixed three-beat structure; runtime is 360f.
+
+| Frames | Beat | What happens |
+|---|---|---|
+| 0–90 | **Kicker** | Small "Introducing" label slides down and holds; `tracking-in` keeps letterforms tight; no motion after entrance |
+| 90–240 | **Feature name** | The feature name bursts in per-character from below; the `spotlight-card` light shifts to sit behind the name over 24f; a scale pulse (1.0→1.04→1.0) lands as the last character settles |
+| 240–360 | **Payoff** | A single benefit line builds line by line; one key word receives a growing accent bar via `inline-highlight`; the whole scene exits via `scale-down-fade` |
+
+Transitions: kicker→name `fade-through` (linear, 12f); name→payoff `shared-axis-y` downward (spring, ~18f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Kicker | `short-slide-down` (label entrance, y −20→0 over 12f), `tracking-in` (letterforms focus in on hold), `spotlight-card` (static bg during kicker) | **`kicker-eyebrow`** — small superscript label above the feature name; sentence-case, no uppercase; props `text`, `align`, `delayInFrames` (build per `../anatomy.md` §1) |
+| Feature name | `per-character-rise` (letters from below, spring damping 12, stagger 4f/char), `spring-scale-in` (scale pulse 1.0→1.04→1.0 on landing), `spotlight-card` (light position interpolated over 24f to sit behind name) | **`feature-name`** — short-phrase spotlight frame; drives character entrance and synchronizes the `spotlight-card` light shift; props `name`, `spotlight: boolean`, `entrance`, `emphasis?` |
+| Payoff | `line-by-line-slide` (benefit line entrance), `inline-highlight` (accent bar grows over 10f on key word), `scale-down-fade` (full-scene exit) | — |
+
+`feature-name` and `kicker-eyebrow` are absent from the catalog — both recur across announcement archetypes, so build them as lightweight components (anatomy §1, "build new"), not one-offs.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `featureName` | yes | 1–3 words ("Smart Replies", "Instant Export", "Live Sync") — infer from PR title or release notes |
+| `benefitLine` | yes | One plain-language sentence of value, e.g. "Draft ready before you hit send" — ask if not supplied |
+| `highlightWord` | yes | The one word in `benefitLine` that carries the payoff; drives `inline-highlight` |
+| `kickerLabel` | no | Default `"Introducing"`; override for re-runs ("Now in beta", "Coming to all plans") |
+| `brand` | no | `{ accent, background }` — one accent on neutral; `spotlight-card` light tint inherits `accent` |
+
+## Notes
+
+- **One feature only.** This archetype spotlights a single capability. For multiple features use changelog or a repeating per-feature series; enumeration is the primary slop failure mode here.
+- **Background is `spotlight-card` throughout.** The light animates from center to behind the feature name over 24f — that motion is the visual payoff, replacing any decorative effect. No glow blobs, no radial halos behind type.
+- **Accent on one word.** The `inline-highlight` on `highlightWord` is the sole accent touch; kicker and feature name stay in the neutral theme color.
+- **Keep the feature name short.** `per-character-rise` at 4f stagger over more than ~12 characters runs long and loses energy. Names over three words should be shortened or split to two display lines.
+- **All copy in English.** `benefitLine` and `kickerLabel` must be real English content, never lorem; `highlightWord` must be a genuine content word that repays the accent.
diff --git a/skills/remocn/references/archetypes/index.md b/skills/remocn/references/archetypes/index.md
new file mode 100644
index 00000000..bc47d1d7
--- /dev/null
+++ b/skills/remocn/references/archetypes/index.md
@@ -0,0 +1,94 @@
+# Archetype index
+
+Router for video archetypes. **Pick the archetype that matches the user's ask, then open that
+`<name>.md`** for its full recipe (beats → slots → contract). Read `../anatomy.md` first for the
+strategy, the beat language, and the good-vs-slop bar; pick components from `../components/index.md`.
+
+Status: **ready** = has a recipe file here. **planned** = known archetype, not yet distilled — compose
+it from `../anatomy.md` (the 6-beat anatomy generalizes) until a recipe lands. `product-demo` is the
+fully-worked flagship; the others are compact recipes.
+
+## A. Product & Launch
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`product-demo`](product-demo.md) | Show a product solving a problem, end to end | ~18–45s | **ready** (flagship) |
+| [`feature-announcement`](feature-announcement.md) | Spotlight one new capability | ~12–20s | **ready** |
+| launch-coming-soon | Tease a launch / coming-soon date | ~10–15s | planned |
+| app-store-preview | Vertical app-store preview reel | ~15–30s `[9:16]` | planned |
+| waitlist-beta | Waitlist / beta-invite ask | ~10–15s | planned |
+| brand-sizzle | Fast brand intro / sizzle | ~10–20s | planned |
+
+## B. Release & Updates
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`changelog`](changelog.md) | Version + human-readable change list | ~9s `[N]` | **ready** |
+| version-bump | One headline version highlight | ~8–12s | planned |
+| patch-notes | Bugfix / patch list | ~8s `[N]` | planned |
+| roadmap-reveal | Upcoming roadmap items | ~12–20s `[N]` | planned |
+| migration-guide | Steps to migrate to a new version | ~15–25s `[N]` | planned |
+
+## C. Growth & Social Proof
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`testimonial-reel`](testimonial-reel.md) | Cycle real testimonials/quotes | ~15–25s `[N]` | **ready** |
+| tweet-wall | Wall of tweets/mentions | ~12–20s `[N]` | planned |
+| milestone | Celebrate a milestone number | ~8–12s | planned |
+| social-proof-stats | Aggregate proof stats | ~10–15s | planned |
+| review-spotlight | One standout review, vertical | ~10–15s `[9:16]` | planned |
+
+## D. Developer / OSS
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`oss-showcase`](oss-showcase.md) | Show an OSS repo (stars, contributors, code) | ~20–35s | **ready** |
+| [`cli-tool-demo`](cli-tool-demo.md) | Demo a CLI / dev tool running | ~20–45s | **ready** |
+| code-walkthrough | Step through code | ~20–40s `[steps]` | planned |
+| api-sdk-intro | Introduce an API / SDK | ~20–30s | planned |
+| integration-announcement | Announce an integration | ~12–20s | planned |
+| deploy-story | A deploy/build pipeline story | ~20–35s | planned |
+
+## E. Data & Metrics
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`year-in-review`](year-in-review.md) | Recap a year/period in numbers | ~20–35s `[N]` | **ready** |
+| dashboard-tour | Tour a dashboard | ~20–30s | planned |
+| metrics-report | Report key metrics | ~15–25s `[N]` | planned |
+| funnel-growth-story | A funnel / growth narrative | ~20–30s | planned |
+| comparison-before-after | Before → after comparison | ~12–20s | planned |
+
+## F. Onboarding & Education
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| app-walkthrough | Onboarding walkthrough | ~20–35s `[N]` | planned |
+| tutorial-how-to | A how-to / tutorial | ~20–40s `[N]` | planned |
+| empty-to-populated | Empty state → populated | ~12–20s | planned |
+| tooltip-tour | A tooltip-guided tour | ~15–25s | planned |
+
+## G. Marketing & Events
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| webinar-event-promo | Promote a webinar/event | ~12–20s | planned |
+| sale-discount-promo | A sale / discount promo | ~8–15s | planned |
+| newsletter-digest | A newsletter digest | ~15–25s `[N]` | planned |
+| hiring | We're-hiring reel | ~12–20s `[N]` | planned |
+| podcast-promo | Podcast/episode promo, vertical | ~15–25s `[9:16]` | planned |
+
+## H. Brand & Identity
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`logo-bumper`](logo-bumper.md) | Logo reveal / intro-outro bumper | ~4–6s | **ready** |
+| lower-third | A lower-third name/title strip | ~5–8s | planned |
+
+## I. Sales & Conversion
+| Archetype | Use for | Duration | Status |
+|---|---|---|---|
+| [`pricing-reveal`](pricing-reveal.md) | Reveal pricing tiers | ~12–20s | **ready** |
+| plan-comparison | Compare plans side by side | ~15–25s | planned |
+| case-study | A customer case study | ~20–35s | planned |
+| roi-savings | An ROI / savings result | ~10–18s | planned |
+
+---
+
+**Adding an archetype:** distill its `TEMPLATES.md` section into a compact recipe (`<name>.md`) using
+`changelog.md` as the format model — Beats → Beat→slots → Content contract → Notes — grounded in real
+catalog components, flagging any not-in-catalog visual as a "build new" component (anatomy §1). Then flip
+its row here to **ready** with the link.
diff --git a/skills/remocn/references/archetypes/logo-bumper.md b/skills/remocn/references/archetypes/logo-bumper.md
new file mode 100644
index 00000000..f7ba4688
--- /dev/null
+++ b/skills/remocn/references/archetypes/logo-bumper.md
@@ -0,0 +1,56 @@
+# logo-bumper
+
+**Family:** H. Brand & Identity · **Default duration:** ~4.5s (135f @30fps, ±15f with wordmark length) · **Format:** 16:9 · **Vibe:** premium
+
+A brand insert: the wordmark assembles, the mark draws or scales in, the lockup holds. Used as a standalone intro sting, a series opener (with corner brackets and a tagline), or a closing brand card. One mark, one accent, total restraint — this archetype is where over-decoration is most tempting and most wrong.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+Three-beat structure: wordmark builds progressively, mark enters while the wordmark tail is still settling (overlap keeps energy without rushing), then the full lockup holds static.
+Frame math: `60 (wordmark) + 45 (mark, −15 overlap with wordmark) + 45 (hold) = 135f`. Scale the hold window up if the bumper will be reused across many cuts.
+
+| Frames | Beat | What happens |
+|---|---|---|
+| 0–60f | **Wordmark build** | brand name assembles — word by word or character by character, reads as "O → Open → OpenAI" |
+| 45–105f | **Mark reveal** | the brand mark draws, scales, or assembles in, overlapping the wordmark tail; settles at full opacity |
+| 90–135f | **Hold** | complete lockup holds static — 30–45f of no motion for clean editor trim |
+
+Transitions: none internal — the bumper is atomic. Connect to surrounding content externally (`zoom-through-transition` or `image-expand-to-fullscreen` from the host composition).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Wordmark build | `kinetic-center-build` (word-by-word from center, premium feel), `per-character-rise` (crisp even stagger, clean), `tracking-in` (all letters as one focusing unit, premium) | — |
+| Mark reveal | — | **`logo-sting`** — single mark; `logo-enter` is a multi-chip partner cluster and cannot represent one mark |
+| Hold + optional exit | `blur-out-up` (graceful exit before the next scene), `dynamic-grid` or `spotlight-card` or solid `backdrop` (static bg) | — |
+| Bumper variant: bracket frame + tagline | — | **`bumper-frame`** — corner brackets (strokeDashoffset draw, 4f stagger per corner) + tagline/CTA rows + `mode: 'intro' \| 'outro'` that mirrors choreography |
+| Accent pop (launch bumper only) | `confetti` — one burst on a product-launch sting; skip entirely on a standard brand insert | — |
+
+`logo-enter` ([`../components/logo-enter.md`](../components/logo-enter.md)) renders a brand or partner **chip cluster** ("works with Stripe, GitHub, Vercel"). A single product mark always needs the new `logo-sting` component.
+
+The two new components are reusable across the entire H family: `logo-sting` is the atomic mark primitive that H1/H3/H4 all share; `bumper-frame` wraps it for series openers and closers.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `wordmark` | yes | brand name as displayed; infer from `package.json` name or project root |
+| `logoSrc` | yes | path to the SVG mark (e.g. `/brand/mark.svg`); `draw` preset requires a `<path>` outline for `strokeDashoffset` |
+| `accent` | yes | one color only; every other value stays neutral (white / near-black) |
+| `preset` | yes | `'draw' \| 'assemble' \| 'impact'` — controls mark choreography inside `logo-sting` |
+| `tagline` | no | bumper variant (intro mode) only; short phrase under the wordmark |
+| `cta` | no | bumper variant (outro mode) only; e.g. `"Subscribe · Next episode"` |
+| `hold` | no | frames of static finale appended to the sting; default 30 |
+
+## Notes
+
+- **One accent, mono otherwise.** The accent touches the active character or the mark outline only — never the whole wordmark, never the background. Gradient text is slop.
+- **No glow halo.** No radial-gradient blobs, no blur clouds behind the mark, no drop-shadow rings. The mark earns attention through motion alone.
+- **`logo-enter` is wrong here.** The catalog `logo-enter` renders a multi-chip cluster of brand logos arriving together. A single product mark needs the new `logo-sting`.
+- **Background stays static.** Low-opacity `dynamic-grid` (≈0.05) or a solid `backdrop` color — no animated background competing with the mark reveal.
+- **Hold generously.** 30–45f of static lockup lets the editor cut cleanly. If the bumper will be dropped into many different videos, lean toward 45f.
+- **Brackets only for series bumpers.** Add `bumper-frame` for YouTube series, courses, or weekly update intros/outros. A one-off product sting uses `logo-sting` alone — no frame chrome.
+- **Outro mirrors intro.** In `bumper-frame` `mode='outro'`: wordmark enters with `mask-reveal-up` instead of `kinetic-center-build`; CTA line uses `short-slide-down`; brackets hold throughout as the brand signature rather than animating in fresh.
+- **`confetti` is a hard exception.** Use it only on an explicit product-launch or milestone bumper, never as default decoration. When in doubt, omit it.
diff --git a/skills/remocn/references/archetypes/oss-showcase.md b/skills/remocn/references/archetypes/oss-showcase.md
new file mode 100644
index 00000000..077e293d
--- /dev/null
+++ b/skills/remocn/references/archetypes/oss-showcase.md
@@ -0,0 +1,60 @@
+# oss-showcase
+
+**Family:** D. Developer/OSS · **Default duration:** ~13s (390f @30fps, scales with contributor count N) · **Format:** 16:9 · **Vibe:** tech
+
+An OSS repo announcement: establish the repo name, count up stars and forks, reveal the contributor community, show the install command, close on a GitHub CTA. The traction numbers are the story spine — they must land with satisfying momentum, not slide by as decoration.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+Five-beat structure: Positioning (repo name) → Proof (stars/forks) → Proof (contributors) → Product reveal (install) → CTA. The contributors scene scales with N: `clamp(90, 90 + N×4, 180)` frames; default N≈48 → 90f. Total default: ~390f minus transition overlaps (~72f combined) ≈ 390f net.
+
+**Long variant — Q&A cadence (avoid over-long slop):** For repos with a richer story, replace the RepoTitle beat with a question→answer rhythm: "Open source?" → "Yes." / "Battle-tested?" → "Yes." / "Free forever?" → "Yes." — three quick `kinetic-center-build` + `per-word-crossfade` swaps before the stars beat. Avoids the enumeration trap. Reference `good_06` (shadcn-sidebar, ~117s) demonstrates this cadence at scale.
+
+| Frames (default) | Beat | What happens |
+|---|---|---|
+| 0–90f | **RepoTitle** | `owner/repo` name large centered via `per-character-rise` (stagger 2f/char); one-line tagline `soft-blur-in` at 12f delay; scene exits via `micro-scale-fade` |
+| 90–195f | **StarsTraction** | `github-stars` entrance: star icon `spring-scale-in`, count rolls up to value; forks and issues `rolling-number` cascade 8f apart; `shimmer-sweep` sweeps the star count at peak |
+| 195–285f | **Contributors** | `contributors-grid` (build new) waves in avatar tiles staggered by index; "N contributors" heading via `rolling-number` |
+| 285–360f | **InstallLine** | `terminal-simulator` types install command char by char; output line enters via `staggered-fade-up`; green checkmark `spring-scale-in` |
+| 360–390f | **CTA** | "Star it on GitHub" text `tracking-in`; repo URL and button `micro-scale-fade`; `spotlight-card` behind button |
+
+Transitions: RepoTitle→Stars `fade-through` (spring, 20f); Stars→Contributors `spatial-push` left (linear, 18f); Contributors→Install `frosted-glass-wipe` (24f); Install→CTA `zoom-through-transition` (spring, ~15f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| RepoTitle | `per-character-rise` (repo name), `soft-blur-in` (tagline), `micro-scale-fade` (exit), `dynamic-grid` (bg) | — |
+| StarsTraction | `github-stars` (stargazer fly-through + odometer), `rolling-number` (forks, issues cascade), `shimmer-sweep` (count emphasis at peak) | — |
+| Contributors | `rolling-number` (contributor count heading) | **`contributors-grid`** — wave of avatar tiles; `avatars: {avatarUrl: string; login?: string}[]`, `columns?: number` (auto), `stagger?: number` (3f default), `shape?: 'circle' \| 'rounded'` (default circle), `maxVisible?: number` (overflow folded into "+N" chip); each tile spring scale+opacity, stagger by index; seek-safe, no side-effect clocks (anatomy §1) |
+| InstallLine | `terminal-simulator` (typed command + output lines), `staggered-fade-up` (output text), `spring-scale-in` (checkmark icon) | — |
+| CTA | `tracking-in` (headline), `micro-scale-fade` (URL + button), `spotlight-card` (editorial bg under button), `dynamic-grid` (base bg) | **`cta-scene`** — reusable CTA wrapper (label + URL chip + button slot); not in catalog, build as lightweight transparent component (anatomy §1) |
+
+For the long Q&A variant: `kinetic-center-build` (question line), `per-word-crossfade` (question→answer swap) — both catalog; no new component needed.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `repo` | yes | `owner/repo` — infer from `package.json` `"repository"` or current git remote |
+| `tagline` | yes | one-line description — infer from GitHub API `description` or `package.json` `"description"` |
+| `stars` | yes | infer from `GET /repos/{owner}/{repo}`; animate from 0 to value |
+| `forks` | no | infer from same API response; omit if zero |
+| `issues` | no | open issue count from API; omit if repo disables issues |
+| `contributors[]` | yes | `{avatarUrl: string; login?: string}[]` — infer from `GET /repos/{owner}/{repo}/contributors?per_page=24`; fold remainder into "+N" chip |
+| `installCmd` | yes | infer from `package.json` `"name"` → `npm install <name>`; use `npx shadcn add @<scope>/<name>` for shadcn-registry repos |
+| `ctaLabel` | no | default `"Star it on GitHub"` |
+| `ctaUrl` | yes | full GitHub repo URL |
+| `accent` | no | one color; default `#FFD23F`; applied to star count, terminal checkmark, CTA button — nowhere else |
+| `font` | no | default `Geist Mono`; monospace reinforces the dev context |
+
+## Notes
+
+- **One accent only.** The accent touches exactly three elements: the peak star count, the terminal checkmark, and the CTA button. Tagline, contributor heading, and output lines stay neutral.
+- **Background is `dynamic-grid` throughout.** Low opacity (~0.06), no motion competing with content. CTA beat adds `spotlight-card` behind the button — a structured editorial card, not a glow blob.
+- **Star count is the number payoff.** `github-stars` exists for exactly this beat — it provides the stargazer fly-through plus the odometer. A bare `rolling-number` on its own misses the moment.
+- **Contributors must feel like people arriving, not a grid being filled.** The diagonal wave entrance (stagger by index) creates a sense of community assembling. Cap visible tiles at 24; fold the rest into a "+N" chip rather than shrinking avatar size.
+- **Terminal output: 2–3 lines max.** Command line, one confirmation output (`✓ added 1 package in 2s`), and the checkmark. A wall of npm install output is slop — `terminal-simulator` can render more, but don't.
+- **`contributors-grid` must be seek-safe.** Compute each tile's animation purely from `frame` and index; no `useState`, `useEffect`, or real-time clocks. See anatomy §1.
+- **`cta-scene` is not in the catalog.** Build it as a lightweight transparent wrapper (label `string`, url `string`, buttonLabel `string`) consistent with anatomy §1. Reusable across all D-family archetypes.
diff --git a/skills/remocn/references/archetypes/pricing-reveal.md b/skills/remocn/references/archetypes/pricing-reveal.md
new file mode 100644
index 00000000..e2366a71
--- /dev/null
+++ b/skills/remocn/references/archetypes/pricing-reveal.md
@@ -0,0 +1,67 @@
+# pricing-reveal
+
+**Family:** I. Sales & Conversion · **Default duration:** ~12s (360f @30fps) · **Format:** 16:9 · **Vibe:** premium
+
+A sales scene that walks viewers through pricing tiers, elevates the recommended plan, and closes on a CTA. The recommended tier is the single focal point — every other element frames it. Restrained by design: one accent color, one highlighted column, one ask.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+A 5-beat specialization of the anatomy (Positioning → Features → CTA), compressed into a single unbroken scene followed by a CTA cut.
+
+| Frames | Beat | What happens |
+|---|---|---|
+| 0–55f | **Lead** | "Simple pricing" headline resolves; a kicker line fades up beneath it |
+| 55–150f | **ColumnsEnter** | Three tier cards rise from below with a left-to-right stagger |
+| 150–250f | **RecommendFocus** | Recommended column lifts and scales up; flanking columns dim; feature checks draw in; "Popular" badge springs in |
+| 250–320f | **PriceLand** | Recommended price rolls in with `$` prefix and lands; `/mo` gets a brief inline highlight |
+| 320–360f | **CTA** | CTA headline builds word by word; button springs in and takes a single shimmer sweep |
+
+Transitions: Lead→ColumnsEnter `shared-axis-y` (spring, 16f); grid→CTA `spatial-push` upward (linearTiming, 20f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Lead | `soft-blur-in` (title, blur 14→0 over 20f), `staggered-fade-up` (kicker), `spotlight-card` (bg, static light) | — |
+| ColumnsEnter | `staggered-fade-up` (column group, 8f stagger, spring `damping:18`) | **`pricing-column`** — tier card atom |
+| RecommendFocus | `micro-scale-fade` (recommended lift + scale 1→1.05), `spring-scale-in` ("Popular" badge), `progress-steps` (features drawing in, 6f stagger), `spotlight-card` (light angle shifts onto recommended) | orchestrated by **`plan-table`** |
+| PriceLand | `slot-machine-roll` (price with `$` prefix + suffix `/mo`), `inline-highlight` (/mo emphasis) | — |
+| CTA | `kinetic-center-build` (CTA headline, word-by-word), `spring-scale-in` (button entrance, `damping:8`), `shimmer-sweep` (single sweep on button) | — |
+
+`pricing-column` and `plan-table` are not in the catalog — build both:
+
+- **`pricing-column`** (build new) — atomic tier card: name, price slot (passed as a rendered node so `slot-machine-roll` lives inside), period, feature list, `recommended` flag. When `recommended` is true, renders an accent border and exposes a lifted position for the parent orchestrator. Transparent background. Props: `{ name: string; price: number; period?: string; features: string[]; recommended?: boolean }`.
+- **`plan-table`** (build new) — orchestrator: lays out a `pricing-column[]` row, sequences the ColumnsEnter → RecommendFocus → PriceLand phases by splitting total frames into thirds, synchronizes the `spotlight-card` light position with the recommended column's x-offset. Props: `{ columns: PricingColumn[]; durationInFrames: number }`. Transparent; caller supplies the `spotlight-card` backdrop.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `tiers[]` | yes | `{ name: string; price: number; period?: string; features: string[]; recommended?: boolean }` — exactly one tier should have `recommended: true` |
+| `headline` | yes | Short, 2–4 words — "Simple pricing", "Plans that scale" |
+| `kicker` | no | One line beneath the headline — "No hidden fees", "Cancel anytime" |
+| `cta.headline` | yes | 3–5 words — "Start your free trial" |
+| `cta.label` | yes | Button label — "Get started", "Start free trial" |
+| `brand` | no | `{ accent }` → one accent color applied to the recommended column border, badge, and shimmer; everything else neutral |
+
+Use real plan names and real feature copy. Never use "Plan A / Feature 1" filler. If the user's product has no pricing yet, use the sample data below unchanged — it is honest placeholder, not lorem.
+
+Sample data:
+
+```ts
+columns: [
+ { name: "Hobby", price: 0, period: "mo", features: ["3 projects", "720p export", "Community support"] },
+ { name: "Pro", price: 19, period: "mo", features: ["Unlimited projects", "4K export", "Priority render", "Custom domain"], recommended: true },
+ { name: "Team", price: 49, period: "mo", features: ["Everything in Pro", "5 seats", "SSO", "Audit log"] },
+]
+```
+
+## Notes
+
+- **One accent only.** Apply the accent color to: the recommended column border, the "Popular" badge, the shimmer sweep on the CTA button. Secondary tiers stay neutral — dimming opacity (1→0.55) is the only treatment they receive.
+- **`spotlight-card` is motivated light, not a glow.** The light shifts toward the recommended column during RecommendFocus to justify the visual emphasis. Do not add a radial gradient or blur halo behind the column.
+- **`slot-machine-roll` for prices.** It handles the `$` prefix and `/mo` suffix natively — pass `prefix="$"` and `suffix="/mo"` rather than formatting the string by hand. Use `rolling-number` only for pure large integers with no currency symbol.
+- **Three tiers is the canonical count.** If the user has two or four, adjust the stagger timing accordingly; do not force a third empty column.
+- **Background stays dark.** `spotlight-card` defaults are tuned for dark backgrounds — keep the canvas dark so the light reads. A solid `#09090b` or `backdrop` with theme `dark` works; avoid light or colorful fills.
+- **CTA is calm, not celebratory.** `shimmer-sweep` runs once — no loop, no bounce, no confetti. The energy peaks at PriceLand; the CTA is a composed close.
diff --git a/skills/remocn/references/archetypes.md b/skills/remocn/references/archetypes/product-demo.md
similarity index 85%
rename from skills/remocn/references/archetypes.md
rename to skills/remocn/references/archetypes/product-demo.md
index 62c47a4e..6f76f8cf 100644
--- a/skills/remocn/references/archetypes.md
+++ b/skills/remocn/references/archetypes/product-demo.md
@@ -1,18 +1,13 @@
-# Archetype recipes
+# product-demo
-Concrete build recipes per video archetype. Read `anatomy.md` first (strategy + beats + the good/slop
-bar), pick components from `components/index.md`. Currently covers **product-demo**; more archetypes
-are added here over time.
+**Family:** A. Product & Launch · **Default duration:** ~45s standard (1356f @30fps) · **Format:** 16:9
----
+The flagship archetype, fully worked. A product demo tells one story: *"X has problem Y; here's the
+product solving it; here's proof; here's how to get it."* Built as a raw `<TransitionSeries>` stitching
+catalog components, one beat per sequence. Grounded in real demos (CrowdReply, Flowith, HeyGen, monid).
+Read `../anatomy.md` first.
-## product-demo
-
-A product demo tells one story: *"X has problem Y; here's the product solving it; here's proof; here's
-how to get it."* Built as a raw `<TransitionSeries>` stitching catalog components, one beat per
-sequence. Grounded in real demos (CrowdReply, Flowith, HeyGen, monid).
-
-### Step 1 — gather content (infer → ask → placeholder)
+## Step 1 — gather content (infer → ask → placeholder)
Fill this contract. **Infer** from the repo first (`README`, landing copy, `package.json`), then **ask**
the user only for what's missing, then fall back to honest English placeholders. Never block on missing data.
@@ -28,34 +23,34 @@ the user only for what's missing, then fall back to honest English placeholders.
| `cta` | no | `{ line, domain }` or `{ line, command }` |
| `brand` | no | `{ accentColor, vibe }` → default neutral + one accent; pick `vibe` to match (`tech`/`premium`/`clean`/`data`/`social`) |
-### Step 2 — pick the duration variant
+## Step 2 — pick the duration variant
| Variant | Length | Frames @30fps | Beats | Reference |
|---|---|---|---|---|
| **Short** | ~18s | ~540 | Hook → Product reveal → Positioning/CTA | monid (good, 18s) |
| **Standard** | ~45s | ~1356 | all 6 | CrowdReply / Flowith / HeyGen (good, 42–45s) |
| **Long** | 90s+ | — | many features | only with a strong repeating rhythm (Q&A cadence); else split into several videos. A flat 100s feature-list drags — that is the slop trap. |
-| **Bumper** | ~4–5s | ~135 | Positioning → lockup only | a logo sting; use `logo-enter`. Not a full demo — a brand insert. |
+| **Bumper** | ~4–5s | ~135 | Positioning → lockup only | a logo sting; see `logo-bumper.md`. Not a full demo — a brand insert. |
-### Step 3 — map beats to component slots
+## Step 3 — map beats to component slots
-Pick one slot per beat from these candidates (full props in each `components/<name>.md`):
+Pick one slot per beat from these candidates (full props in each `../components/<name>.md`):
| Beat | Slot candidates | Notes |
|---|---|---|
| **Hook** | `kinetic-center-build`, `blur-out-up`, `per-word-crossfade`, `tracking-in`, `staggered-fade-up` over `dynamic-grid` or solid | emphasize ONE word with the accent, sentence case |
| **Positioning** | `per-character-rise` / `focus-blur-resolve` / `kinetic-center-build` for the line and wordmark; `logo-enter` for a brand/partner logo cluster (not a single lockup) | resolve text into the brand mark; a single styled lockup may be a small new component |
-| **Product reveal** | `terminal-simulator`, `glass-code-block`, `code-accordion`, `device-mockup-zoom`; AI surfaces `chat-gpt`/`claude-chat`/`claude-code`/`v0`/`opencode`; add `cursor` / `simulated-cursor` | if the catalog lacks the exact surface, build a new lightweight `ui-frame` (see `anatomy.md` §1) |
+| **Product reveal** | `terminal-simulator`, `glass-code-block`, `code-accordion`, `device-mockup-zoom`; AI surfaces `chat-gpt`/`claude-chat`/`claude-code`/`v0`/`opencode`; add `cursor` / `simulated-cursor` | if the catalog lacks the exact surface, build a new lightweight `ui-frame` (see `../anatomy.md` §1) |
| **Features** | `progress-steps` (checklist), `animated-bar-chart` / `animated-line-chart`, `per-word-crossfade` for a "designed to ___" swap, `marker-highlight` / `inline-highlight` for emphasis, `tool-menu-slide-in`, `data-flow-pipes` | one concrete moment per feature, 2–4 total |
| **Proof** | `rolling-number` / `number-wheel` / `slot-machine-roll` for a score; `animated-bar-chart`; `github-stars` / `x-followers-overview` for social counts; a testimonial card (compose or build new) | land one number with the accent |
| **CTA** | `per-word-crossfade` / `kinetic-center-build` closer, `terminal-simulator` for a run-this command, `spring-scale-in` for a pill, `logo-enter`, `confetti` (one accent pop) | one ask + where to go |
| **Transitions** | `spatial-push` (going deeper), `fade-through` (neutral cut), `frosted-glass-wipe`, `directional-wipe`, `shared-axis-y`/`shared-axis-z` | wrap two scenes via `from`/`to` |
Budget each `<TransitionSeries.Sequence durationInFrames>` around the component's natural length
-(`Length` in `components/index.md`). Standard ~45s split: Hook 165 · Positioning 120 · Product reveal
+(`Length` in `../components/index.md`). Standard ~45s split: Hook 165 · Positioning 120 · Product reveal
150 · Features 450 (across 2–4) · Proof 300 · CTA 171.
-### Step 4 — assemble (raw `<TransitionSeries>`)
+## Step 4 — assemble (raw `<TransitionSeries>`)
Standard variant skeleton. Swap the slot components and content for the gathered contract. Install each
picked component first (`shadcn add @remocn/<name>`); deps auto-install.
@@ -114,13 +109,13 @@ transparent. Replace `DynamicGrid` import usage if you want a grid hook backgrou
fill. The product-reveal beat above is folded into the features checklist for brevity — for a richer
surface, add a `TerminalSimulator` / chat sim / new `ui-frame` sequence before the features beat.
-### Step 5 — check against the bar
+## Step 5 — check against the bar
-Before delivering, run the good/slop checklist in `anatomy.md` §3: one accent, sentence-case kinetic
+Before delivering, run the good/slop checklist in `../anatomy.md` §3: one accent, sentence-case kinetic
type, real content (no `Scene A` lorem), no glow halos, no feature-list enumeration, no `mesh-gradient-bg`,
legible text, story not catalog. Budget frames so nothing clips and there's no dead air.
-### Installable worked example
+## Installable worked example
`a1-product-demo` in this registry is a full standard-length (~45s, 1356f) product demo built on this
skeleton — install and read it as the long worked reference: `shadcn add @remocn/a1-product-demo`.
diff --git a/skills/remocn/references/archetypes/testimonial-reel.md b/skills/remocn/references/archetypes/testimonial-reel.md
new file mode 100644
index 00000000..020c5dde
--- /dev/null
+++ b/skills/remocn/references/archetypes/testimonial-reel.md
@@ -0,0 +1,51 @@
+# testimonial-reel
+
+**Family:** C. Growth & Social Proof · **Default duration:** ~14s (430f @30fps for N=3, scales with quote count) · **Format:** 16:9 · **Vibe:** clean
+
+Cycle real customer quotes one at a time — each card springs in, holds while the quote text plays word-by-word, then fades through to the next. Close on an aggregate proof number ("Join 12,000+ people who found their flow") so the social proof lands on data, not sentiment alone. One accent color throughout; background is a `spotlight-card` soft light on a solid dark canvas.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+Frame math: `total = 60 (intro) + N×90 (quote scenes, 15f fade-through overlap each) + 10 (last-quote hold) + 90 (aggregate close)`. N=3 → 430f (~14s). Cap at N=5 (~600f, ~20s) and fold any extra quotes into "+M more" on the aggregate tagline rather than extending runtime.
+
+| Frames (N=3) | Beat | What happens |
+|---|---|---|
+| 0–60 | **Intro** | Section title "What teams say" builds via `tracking-in`; thin horizontal divider enters via `mask-reveal-up` (left → right, 20f) |
+| 60–165 | **Quote 1** | `testimonial-card` springs up (translateY 40→0, `spring({damping:18,mass:0.9})`); quote text arrives via `per-word-crossfade` (4f/word stagger); avatar + author/role enter via `staggered-fade-up` (2 elements, 6f stagger); 2 peek cards behind at scale 0.94 / opacity 0.5 |
+| 150–255 | **Quote 2** | `fade-through` swap (15f overlap); author-line enters via `short-slide-right`; peek stack shifts depth |
+| 240–355 | **Quote N** | Last quote holds +10f longer; peek cards resolve to full opacity as the stack empties; `blur-out-up` exits the card stack on the way out |
+| 345–435 | **Aggregate close** | `spring-scale-in` enters the metric block; `rolling-number` counts to the aggregate figure; tagline "Join X+ [phrase]" arrives via `staggered-fade-up`; optional `x-followers-overview` or `github-stars` anchors the number in a recognizable social surface |
+
+Transitions: `fade-through` (`linearTiming(15)`) between each quote scene; intro → Quote 1 via `springTiming({damping:200})`; Quote N → aggregate via `fade-through` (15f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| Intro | `tracking-in` (title), `mask-reveal-up` (divider line), `spotlight-card` (bg) | — |
+| Quote cycling | `per-word-crossfade` (quote text), `staggered-fade-up` (avatar + author/role), `short-slide-right` (author-line on swap), `fade-through` (scene transition), `blur-out-up` (stack exit) | **`testimonial-card`** — avatar + quote text + name/role; transparent bg; props: `quote`, `name`, `role`, `avatarUrl`; build per `../anatomy.md` §1 |
+| Aggregate close | `spring-scale-in` (metric block entrance), `rolling-number` (count animation), `staggered-fade-up` (tagline), `x-followers-overview` or `github-stars` (optional social anchor) | — |
+
+`testimonial-card` is the only gap in the catalog. The stacking depth effect (peek cards at 0.94 scale / 0.5 opacity behind the active card) is orchestration logic in the parent composition — render 2–3 `testimonial-card` instances with interpolated transform/opacity values; no separate stack container component is needed.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `quotes[]` | yes | `{ quote: string; name: string; role: string; avatarUrl?: string }` — 3–5 entries; infer from testimonials page, G2, or press quotes |
+| `aggregate` | yes | `{ value: number; label: string }` — e.g. `{ value: 12000, label: "people who found their flow" }`; infer from marketing site or README; never fabricate a number |
+| `sectionTitle` | no | Default `"What teams say"`; swap to match brand voice |
+| `brand` | no | `{ accent, background }` — one accent on a neutral dark canvas |
+| `socialAnchor` | no | `"x-followers" \| "github-stars" \| null` — which catalog social surface to pair with the aggregate close |
+
+`[N]` archetype: quote scenes stretch linearly with quote count; cap at N=5 visible quotes and fold any excess into "+M more" on the aggregate tagline rather than extending runtime or compressing type.
+
+## Notes
+
+- **Background: `spotlight-card` on a solid dark base.** The moving soft light tracks the active card, giving depth without a glow blob or radial halo behind the quote text. Never use `mesh-gradient-bg`.
+- **One accent only.** Apply it to the `rolling-number` payoff and optionally to one emphasized word per quote via `inline-highlight`. Everything else is neutral mono.
+- **No glow halos behind quote text.** Depth is conveyed by the peek-card scale/opacity stack (0.94 / 0.5) — that is sufficient.
+- **Real quotes, specific attribution.** "Marcus L., Head of Growth at Loom" beats "User, Company". If avatars are unavailable, render initials in a neutral mono circle — never use stock headshots.
+- **N cap.** Beyond five quotes the runtime exceeds ~20s; split into a second reel or cut entries. Never extend by shrinking type or compressing hold time.
+- **`testimonial-card` stays transparent.** Set the background via `Backdrop` in the example composition, not inside the card itself.
diff --git a/skills/remocn/references/archetypes/year-in-review.md b/skills/remocn/references/archetypes/year-in-review.md
new file mode 100644
index 00000000..a7ecceca
--- /dev/null
+++ b/skills/remocn/references/archetypes/year-in-review.md
@@ -0,0 +1,57 @@
+# year-in-review
+
+**Family:** E. Data & Metrics · **Default duration:** ~20s (600f @30fps, N=4) · **Format:** 16:9 · **Vibe:** data / premium
+
+A mounting sequence of headline numbers — one stat fills the full frame per beat — building urgency as entry stagger compresses, culminating in a RecapWall that shows every figure at once. The rhythm accelerates; the numbers do the talking.
+Read `../anatomy.md` first; pick components from `../components/index.md`.
+
+## Beats
+
+Duration scales with N stats: `total = 90 (intro) + N×120 (stat-beats) − N×15 (overlap) + 90 (recap)`. N=4 → 600f (20s). N=6 → 810f (27s). Cap at N=8 (≈33s); above that, split into two videos.
+
+| Frames (N=4) | Beat | What happens |
+|---|---|---|
+| 0–90 | **IntroTitle** | year kicker builds glyph-by-glyph via `kinetic-center-build` (per-glyph spring, damping 14, stagger 2f); "Year in review" subtitle enters via `soft-blur-in` (blur 12→0px, 24f); full beat exits via `blur-out-up` |
+| 90–210 | **StatBeat #1** | `rolling-number` counts 0→target over 45f ease-out; label enters via `staggered-fade-up` (stagger 24f); number pulses `spring-scale-in` 1.0→1.06→1.0 (damping 8) at roll end; aligned left |
+| 210–330 | **StatBeat #2** | same structure, aligned right; label stagger tightens to 16f |
+| 330–450 | **StatBeat #3** | aligned left; label stagger 16f; optional `animated-line-chart` trend line below the number |
+| 450–570 | **StatBeat #4** | aligned right; label stagger 10f; one `confetti` burst fires at roll end (accent only, finale stat) |
+| 570–660 | **RecapWall** | all N stats enter via `staggered-fade-up` (stagger 8f) into a 2×⌈N/2⌉ grid; accent stat pulses `micro-scale-fade`; CTA line enters via `tracking-in` (letter-spacing 0.3em→0) |
+
+Transitions: Intro → Beat #1 `shared-axis-y` (linearTiming, 18f). Between stat beats `fade-through` (springTiming, config `{ damping: 200 }`, 15f). Beat #N → RecapWall `spatial-push` upward (linearTiming, 20f).
+
+## Beat → slots
+
+| Beat | Catalog components | New component needed |
+|---|---|---|
+| IntroTitle | `kinetic-center-build` (year glyph), `soft-blur-in` (subtitle), `blur-out-up` (exit), `dynamic-grid` (static bg, opacity 0.06) | — |
+| StatBeat #1–N | `rolling-number` (plain large integer), `number-wheel` (integer ≤6 digits or countdown), `slot-machine-roll` (prefix/suffix: `$4.2M`, `98.4%`), `staggered-fade-up` (label), `spring-scale-in` (roll-end pulse), `blur-out-up` (exit); optionally `animated-bar-chart` or `animated-line-chart` as a secondary trend lane below the number | **`stat-beat`** — full-frame single-metric scene: large number component + label + optional delta badge; owns `align` prop (`"left"\|"center"\|"right"`); wraps the correct number component based on value shape; transparent bg |
+| RecapWall | `staggered-fade-up` (grid entries), `micro-scale-fade` (accent stat pulse), `tracking-in` (CTA), `dynamic-grid` (same static bg, continuity) | **`stat-recap`** — 2×⌈N/2⌉ grid of stat cells with staggered entry and optional CTA row; transparent bg |
+
+`stat-beat` and `stat-recap` are not in the catalog — build both as lightweight reusable components (anatomy §1, "build new"). `stat-beat` is the per-beat scene wrapper; `stat-recap` is the closing wall. They pair naturally across release, milestone, and wrap-up archetypes.
+
+## Content contract (infer → ask → placeholder)
+
+| Field | Required | Notes |
+|---|---|---|
+| `kicker` | yes | year or period string, e.g. `"2025"` |
+| `title` | yes | e.g. `"Year in review"` |
+| `stats[]` | yes | `{ label: string; value: number; format?: "plain"\|"compact"\|"currency"; prefix?: string; suffix?: string; delta?: { value: number; direction: "up"\|"down" } }` — min 2, max 8 |
+| `accentStatIndex` | no | index of the stat that earns the `confetti` burst; defaults to last stat |
+| `cta` | no | closing line in RecapWall, e.g. `"See the full report →"` |
+| `brand` | no | `{ accent, background }` — one accent on a dark canvas |
+
+`[N]` archetype: each stat occupies exactly one beat and the total runtime grows linearly with N. When N>8, group related metrics into a single `slot-machine-roll` beat or split the video into two parts — never shrink the type to fit more numbers on screen.
+
+## Notes
+
+- **Background stays static throughout.** A single `dynamic-grid` at opacity 0.06 spans every beat including the RecapWall — the same "dashboard" canvas persists, giving continuity to the sequence.
+- **Alignment alternates left/right.** Left on odd beats, right on even. Compositional variety without introducing a new visual language per beat.
+- **Each beat must advance.** Never repeat the same metric. If two stats are closely related (revenue + MRR), pick one or combine into a single `slot-machine-roll` beat.
+- **Stagger compresses beat by beat.** 24f label stagger on Beat #1, tightening to 10f by the finale — the cadence accelerates, building urgency without changing any component.
+- **One confetti accent.** On the finale stat beat only. Using confetti on every beat drains the payoff; reserve it as a single punctuation mark.
+- **Number component selection.** `rolling-number` for plain large integers (1,284,000 requests); `number-wheel` for small integers or countdowns (42 customers, day 365); `slot-machine-roll` for values with a prefix or suffix ($4.2M ARR, 98.4% uptime).
+- **Delta badge is optional.** Only show `delta` when a prior-year number is real and meaningful (e.g. +31% YoY). Skip if unavailable — a made-up delta is slop.
+- **RecapWall grid sizing.** 2×⌈N/2⌉ grid. For N>6, reduce the per-cell font size proportionally so the wall reads at a glance. Never scroll or clip.
+- **Trend charts are supporting, not lead.** An `animated-bar-chart` or `animated-line-chart` can appear below the rolling number on one beat to add context; it should be smaller than the number and not compete with it. Omit if the number speaks for itself.
+- Real numbers, English labels. Never ship `Metric #1`, `Value`, or lorem as final copy.