Add TikTok video skills (caption-animation, countdown-video, lower-thirds, short-form-video)

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011XhxckAYjGMLrLECWuKBzg
2026-10-18 21:47:45 +00:00
23 changed files with 1842 additions and 487 deletions
@@ -0,0 +1,24 @@
 # Caption Animation
 Turn a transcript or voiceover into word-timed, scroll-stopping captions: each word pops in on the syllable, the active word highlights, and the text stays glued to the narration. Build the kind of captions that drive watch-time on TikTok, Reels, and Shorts — readable, on-beat, and inside the safe area. For short-form creators burning open captions onto vertical video.
 ## When it activates
 - "Add animated captions," "make TikTok captions," or "karaoke captions."
 - "Word-by-word subtitles," "auto subtitles," or "highlight the active word."
 - "Burn in captions to a video" or "sync captions to a voiceover/narration."
 - "Turn an SRT/transcript into animated text."
 ## Example prompts
 - "Turn this Whisper transcript into karaoke captions with a per-word pop."
 - "Restyle these auto subtitles into a branded, Hormozi-style reveal."
 - "Burn word-level captions onto my voiceover and export a sidecar SRT."
 ## What's inside
 - `SKILL.md` — the transcribe → normalize → page → animate → place → export pipeline.
 - `references/word-timed-captions.md` — deeper guidance on word-level timing and animation.
 ---
 Part of **[Short-Form Video Skills](../../)** · Built by **[iart.ai](https://iart.ai/?utm_source=github&utm_medium=readme&utm_campaign=tiktok-video-skills&utm_content=skill_footer&utm_term=caption-animation)** — the AI motion agent for editable, on-brand motion graphics.
@@ -0,0 +1,177 @@
 ---
 name: caption-animation
 description: This skill should be used when the user asks to "add animated captions", "make TikTok captions", "karaoke captions", "word-by-word subtitles", "auto subtitles", "highlight the active word", "burn in captions to a video", "sync captions to a voiceover/narration", or "turn an SRT/transcript into animated text". Covers word-level timing from Whisper, per-word pop/scale-in, active-word highlight, 9:16 safe-area placement, readable type, and burn-in vs sidecar SRT/VTT.
 version: 0.1.0
 ---
 # Caption Animation
 Turn a transcript or voiceover into word-timed, scroll-stopping captions: each word pops in on the syllable, the active word highlights, and the text stays glued to the narration. Build the kind of captions that drive watch-time on TikTok, Reels, and Shorts — readable, on-beat, and inside the safe area.
 ## When to use
 - Word-by-word or karaoke captions on short-form vertical video (9:16).
 - Burning open captions onto a voiceover/narration track from a transcript.
 - Turning a Whisper/SRT transcript into animated text in Remotion or on the web.
 - Restyling auto-generated subtitles into a branded, "Hormozi-style" reveal.
 ## The pipeline
 | Stage | Job | Tool |
 |---|---|---|
 | Transcribe | Audio → word-level timestamps | Whisper (`@remotion/install-whisper-cpp`), AssemblyAI |
 | Normalize | → `{ text, startMs, endMs }[]` tokens | `@remotion/captions` `Caption` type |
 | Page | Group words into 1–4 word "pages" | `createTikTokStyleCaptions()` |
 | Animate | Per-word pop + active-word highlight | Remotion `spring()` / CSS |
 | Place | Safe-area, readable type | layout rules below |
 | Export | Burn-in (MP4) and/or sidecar SRT/VTT | Remotion render / file emit |
 ## Two non-negotiable rules
 1. **Word-level timing, not line-level.** Karaoke reads as magic only when each word lands on the syllable. Always transcribe to word timestamps; never fake them by splitting a line evenly over its duration — drift is instantly visible.
 2. **Readability beats style.** Captions are read on a phone, in sunlight, muted. Bold sans-serif, heavy stroke or shadow, high contrast first; decoration second. A caption nobody can read is decoration, not a caption.
 ## Word timing from a transcript
 Whisper emits word-level timestamps directly. Normalize every source into one flat token shape so the renderer never cares where the words came from:
 ```ts
 // Caption token — the one shape everything downstream consumes
 type Token = { text: string; startMs: number; endMs: number };
 // Parse an SRT cue block "00:00:01,200 --> 00:00:01,640" into ms
 const toMs = (t: string) => {
  const [h, m, rest] = t.split(":");
  const [s, ms] = rest.split(",");
  return ((+h * 60 + +m) * 60 + +s) * 1000 + +ms;
 };
 ```
 If only sentence-level cues exist, re-transcribe for word timing — do not interpolate. Whisper's `medium.en` is ~2x faster than `large` and accurate enough for clean voice audio.
 ## Per-word pop-in (Remotion)
 Drive each word's scale and opacity off a spring anchored to its own `startMs`. The micro-overshoot is what makes it feel "alive".
 ```tsx
 import { useCurrentFrame, useVideoConfig, spring, interpolate } from "remotion";
 const Word: React.FC<{ token: Token; active: boolean }> = ({ token, active }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const enter = (token.startMs / 1000) * fps;            // word's own entrance frame
  const p = spring({ frame: frame - enter, fps, config: { damping: 12, mass: 0.6 } });
  const scale = interpolate(p, [0, 1], [0.6, 1]);        // pop from 60% → 100% (overshoots)
  return (
    <span style={{
      display: "inline-block",
      transform: `scale(${scale})`,
      opacity: interpolate(p, [0, 1], [0, 1]),
      color: active ? "#FFE45E" : "#FFFFFF",             // active-word highlight
      transition: "color 80ms linear",
    }}>{token.text}&nbsp;</span>
  );
 };
 ```
 Compute `active` by testing `frame` against each token's `[startMs, endMs]`. Keep the highlight a single accent color or a filled "box" behind the live word — never animate every word's color at once.
 ## Pages, not walls of text
 Show 1–4 words at a time. Use Remotion's `createTikTokStyleCaptions()` (or group manually) and tune `combineTokensWithinMilliseconds`: ~200–500ms for true word-by-word, ~1000–1500ms for short readable phrases.
 ```ts
 import { createTikTokStyleCaptions } from "@remotion/captions";
 const { pages } = createTikTokStyleCaptions({
  captions, combineTokensWithinMilliseconds: 1200,       // ~2–3 words per page
 });
 ```
 ## Web/CSS pop (no Remotion)
 For a DOM/live player, give each word its own `animation-delay` equal to `startMs`:
 ```css
 .word { display:inline-block; opacity:0; animation: pop .26s cubic-bezier(.34,1.56,.64,1) forwards; }
@keyframes pop { from { opacity:0; transform:translateY(.18em) scale(.7) } to { opacity:1; transform:none } }
 .word.active { color:#FFE45E; }
 ```
 ```js
 words.forEach(w => { const el = mk(w.text); el.style.animationDelay = `${w.startMs}ms`; track.append(el); });
 ```
 ## Readable type and safe-area placement (9:16, 1080×1920)
 | Property | Value | Why |
 |---|---|---|
 | Font | Bold/ExtraBold sans (Montserrat, Inter, Helvetica) | Reads on small, busy screens |
 | Size | 56–80px (≈8% of frame height), min 45px | Legible muted on a phone |
 | Stroke | 2–6px solid black outline | Survives any background |
 | Shadow | Soft drop shadow as backup to stroke | Separation on bright frames |
 | Case | Uppercase or sentence; high contrast fill | Punch + scannability |
 | Vertical pos | Center band, ~62–70% down | Above the UI, below the action |
 | Bottom safe | Keep clear of bottom ~280px / 15% | Avoids caption/CTA/audio UI |
 | Side safe | Keep within center 80% width | Avoids right-rail icons |
 Place captions in the center band — not pinned to the very bottom, where the platform UI (username, audio, buttons) lives. Pad text to a max of ~2 lines.
 ## Sync to a voiceover / narration
 The transcript already carries the timing of the exact audio. Lay that same audio under the composition and keep timestamps in the audio's timebase — captions and voice stay locked with zero manual nudging. If the VO is re-recorded, re-transcribe; never hand-shift offsets.
 ## Burn-in vs sidecar SRT/VTT
 | | Burn-in (open) | Sidecar SRT/VTT (closed) |
 |---|---|---|
 | Where | Pixels in the MP4 | Separate `.srt`/`.vtt` file |
 | Social (TikTok/Reels) | Required — guaranteed, styleable | Often ignored by the platform |
 | Accessibility (ADA/WCAG) | Does not satisfy alone | Required (toggleable) |
 | Best practice | Burn animated captions for social | Also ship a sidecar for the web/SEO |
 Emit both: burn the animated captions for social, and write a plain SRT/VTT from the same tokens for accessible/SEO playback.
 ## Output checklist
 - Word-level timestamps (real, from transcription) — no even-split fakery.
 - Per-word pop with micro-overshoot; one accent color for the active word.
 - 1–4 words per page; never a wall of text.
 - Bold sans, 56–80px, 2–6px stroke + shadow, high contrast.
 - Center band, clear of bottom ~280px and side rails.
 - Audio laid under composition; timestamps in the audio timebase.
 - Ship burn-in for social and a sidecar SRT/VTT for accessibility.
 ## Deliver & verify (rendered stills → MP4)
 > **Packaged helper** (`scripts/`): tile your stills with `scripts/contact-sheet.sh sheet.png f-hook.png f-mid.png f-end.png`, then assert the encode with `scripts/probe-mp4.sh out.mp4 [WxH] [fps]`. See `scripts/README.md`.
 Captions ship as a Remotion composition (`<Composition>` + zod `schema` + `defaultProps`) — all word motion frame-driven off `useCurrentFrame()`, never `Date.now()` / `Math.random()` / timers. Deliverable = `out/*.mp4` (burned-in) + the project + the sidecar SRT/VTT. 9:16 vertical (1080×1920) is the default.
 **Verify loop — render stills → inspect → encode.** Word timing is the thing that breaks; check it at exact frames before you spend an encode.
 ```bash
 # Stills at start / a sampled active-word frame / end — WITH SHIPPED PROPS (real tokens + audio)
 npx remotion still Captions out/f-start.png --frame=0   --props='{"captionsSrc":"vo.json"}'
 npx remotion still Captions out/f-mid.png   --frame=90  --props='{"captionsSrc":"vo.json"}'
 npx remotion still Captions out/f-end.png   --frame=N   --props='{"captionsSrc":"vo.json"}'  # N = durationInFrames-1
 # Inspect each PNG:
 #  - the word highlighted at frame 90 is the word whose [startMs,endMs] contains 90/fps (no drift)
 #  - burn-in legible: bold sans, stroke+shadow holds, no clipping
 #  - 9:16 safe area: caption sits in the center band, clear of top ~12% and bottom ~20-35% (captions/CTA/audio UI) and the right action rail
 npx remotion render Captions out/captions.mp4 --props='{"captionsSrc":"vo.json"}'   # encode once stills are right
 npx remotion render Captions out/demo.gif --codec=gif                                # README proof clip
 ```
 Use `npx remotion compositions` to read `durationInFrames`/`fps` and pick the active-word + end frames.
 **Before you finish:**
 1. Stills render cleanly at frame 0, a mid active-word frame, and last — no missing font/audio.
 2. The correct word is highlighted at the sampled frame (frame/fps lands inside its token); no even-split fakery.
 3. Burn-in is legible (stroke+shadow) and the caption is fully inside the 9:16 safe area at every checked frame.
 4. Frame-driven only — no `Date.now()` / `Math.random()` / timers.
 5. Shipped props (real tokens, not just `defaultProps`) render correctly; MP4 + sidecar SRT/VTT emitted, GIF optional.
 ## Reference files
 - `references/word-timed-captions.md` — end-to-end build: Whisper transcription and the `Caption` type, a full SRT parser, Remotion word-timed component with active-highlight, manual paging, an SRT/VTT emitter, per-platform safe-area maps, and a readable-type spec sheet.
@@ -0,0 +1,254 @@
 # Word-Timed Captions — End-to-End Build
 A complete, runnable path from audio/transcript to animated burn-in captions plus a sidecar SRT/VTT. Code targets Remotion for burn-in and plain JS for the web; the data shapes are framework-agnostic.
 ## 1. The one data shape
 Everything normalizes to a flat array of word tokens. Get to this shape and the renderer never cares about the source.
 ```ts
 export type Token = { text: string; startMs: number; endMs: number };
 export type Page  = { startMs: number; endMs: number; tokens: Token[] };
 ```
 Remotion's `@remotion/captions` uses a compatible `Caption` type:
 ```ts
 type Caption = { text: string; startMs: number; endMs: number; timestampMs: number | null; confidence: number | null };
 ```
 ## 2. Transcribe to word-level timing (Whisper)
 Word timestamps are non-negotiable for karaoke. Whisper produces them natively.
 ```bash
 npx @remotion/install-whisper-cpp   # one-time: installs whisper.cpp + a model
 ```
 ```ts
 import { transcribe, toCaptions } from "@remotion/install-whisper-cpp";
 const { transcription } = await transcribe({
  inputPath: "voiceover.wav",      // 16kHz mono WAV is ideal for whisper.cpp
  model: "medium.en",              // medium.en ≈ 2x faster than large, accurate on clean voice
  tokenLevelTimestamps: true,      // <-- the key flag: per-word, not per-line
  whisperPath: "./whisper.cpp",
 });
 const { captions } = toCaptions({ transcription }); // → Caption[]
 ```
 Tips:
 - Feed clean voice audio (denoise/normalize first). Background music wrecks word boundaries.
 - `large` is most accurate but 2–3x real-time on a laptop. Use `medium.en` unless accuracy is critical.
 - Cloud alternatives (AssemblyAI, Deepgram, OpenAI Whisper API) also return word timing — map their `words[]` into `Token` the same way.
 Map any token shape into `Token`:
 ```ts
 const toTokens = (caps: Caption[]): Token[] =>
  caps.map(c => ({ text: c.text.trim(), startMs: c.startMs, endMs: c.endMs }));
 ```
 ## 3. Parse an existing SRT into tokens
 When handed an SRT, parse cues; if cues are sentence-level, re-transcribe for word timing rather than interpolating.
 ```ts
 const toMs = (t: string) => {
  const [h, m, rest] = t.trim().split(":");
  const [s, ms] = rest.split(",");
  return ((+h * 60 + +m) * 60 + +s) * 1000 + +ms;
 };
 export function parseSrt(src: string): Token[] {
  return src.trim().split(/\n\s*\n/).map(block => {
    const lines = block.split("\n");
    const time = lines.find(l => l.includes("-->"))!;
    const [a, b] = time.split("-->");
    const text = lines.slice(lines.indexOf(time) + 1).join(" ").trim();
    return { text, startMs: toMs(a), endMs: toMs(b) };
  });
 }
 ```
 ## 4. Page the tokens (1–4 words at a time)
 Either use Remotion's helper or group manually. Manual grouping by gap + max-words keeps full control:
 ```ts
 export function paginate(tokens: Token[], maxWords = 3, maxGapMs = 1200): Page[] {
  const pages: Page[] = [];
  let cur: Token[] = [];
  for (const t of tokens) {
    const span = cur.length ? t.endMs - cur[0].startMs : 0;
    if (cur.length >= maxWords || span > maxGapMs) {
      if (cur.length) pages.push(pageOf(cur)); cur = [];
    }
    cur.push(t);
  }
  if (cur.length) pages.push(pageOf(cur));
  return pages;
 }
 const pageOf = (ts: Token[]): Page => ({ startMs: ts[0].startMs, endMs: ts.at(-1)!.endMs, tokens: ts });
 ```
 Remotion equivalent:
 ```ts
 import { createTikTokStyleCaptions } from "@remotion/captions";
 const { pages } = createTikTokStyleCaptions({ captions, combineTokensWithinMilliseconds: 1200 });
 // 200–500ms → word-by-word; 1000–1500ms → short readable phrases
 ```
 ## 5. Remotion component: word-timed with active highlight
 ```tsx
 import { AbsoluteFill, Audio, Sequence, useCurrentFrame, useVideoConfig,
         spring, interpolate, staticFile } from "remotion";
 const CAPTION_STYLE: React.CSSProperties = {
  fontFamily: "Montserrat, Inter, sans-serif",
  fontWeight: 800,
  fontSize: 72,                         // ~8% of 1920px height
  color: "#fff",
  textAlign: "center",
  textTransform: "uppercase",
  WebkitTextStroke: "5px #000",         // heavy outline survives any background
  paintOrder: "stroke fill",            // stroke behind fill, not clipping glyphs
  textShadow: "0 4px 16px rgba(0,0,0,.55)",
  lineHeight: 1.1,
  padding: "0 80px",                    // keep inside center 80% width
 };
 const Word: React.FC<{ token: Token; active: boolean }> = ({ token, active }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const enter = (token.startMs / 1000) * fps;
  const p = spring({ frame: frame - enter, fps, config: { damping: 12, mass: 0.6 } });
  return (
    <span style={{
      display: "inline-block",
      transform: `scale(${interpolate(p, [0, 1], [0.6, 1])})`,
      opacity: interpolate(p, [0, 1], [0, 1]),
      color: active ? "#FFE45E" : undefined,
      transition: "color 80ms linear",
    }}>{token.text}&nbsp;</span>
  );
 };
 export const Captions: React.FC<{ pages: Page[]; audio: string }> = ({ pages, audio }) => {
  const { fps } = useVideoConfig();
  const f = (ms: number) => Math.round((ms / 1000) * fps);
  const frame = useCurrentFrame();
  return (
    <AbsoluteFill>
      <Audio src={staticFile(audio)} />        {/* same audio the transcript came from */}
      {pages.map((pg, i) => (
        <Sequence key={i} from={f(pg.startMs)} durationInFrames={Math.max(1, f(pg.endMs - pg.startMs))}>
          <AbsoluteFill style={{ justifyContent: "flex-start", alignItems: "center", paddingTop: "62%" }}>
            <div style={CAPTION_STYLE}>
              {pg.tokens.map((t, j) => {
                const now = (frame / fps) * 1000;
                return <Word key={j} token={t} active={now >= t.startMs && now < t.endMs} />;
              })}
            </div>
          </AbsoluteFill>
        </Sequence>
      ))}
    </AbsoluteFill>
  );
 };
 ```
 Because the `<Audio>` and the timestamps share one timebase, voice and captions stay locked with no manual nudging. Re-record the VO → re-transcribe → done.
 ## 6. Web/CSS path (live DOM player)
 ```js
 function renderTrack(tokens, mountEl) {
  tokens.forEach(t => {
    const el = document.createElement("span");
    el.className = "word";
    el.textContent = t.text + " ";
    el.style.animationDelay = `${t.startMs}ms`;   // each word pops on its own start
    mountEl.append(el);
  });
 }
 // drive .active off the media element's currentTime
 audio.addEventListener("timeupdate", () => {
  const ms = audio.currentTime * 1000;
  [...track.children].forEach((el, i) =>
    el.classList.toggle("active", ms >= tokens[i].startMs && ms < tokens[i].endMs));
 });
 ```
 ```css
 .cap   { font: 800 72px/1.1 Montserrat, sans-serif; text-transform: uppercase;
         color:#fff; -webkit-text-stroke:5px #000; paint-order:stroke fill;
         text-shadow:0 4px 16px rgba(0,0,0,.55); text-align:center; }
 .word  { display:inline-block; opacity:0; animation: pop .26s cubic-bezier(.34,1.56,.64,1) forwards; }
 .word.active { color:#FFE45E; }
@keyframes pop { from { opacity:0; transform:translateY(.18em) scale(.7) } to { opacity:1; transform:none } }
 ```
 ## 7. Emit a sidecar SRT / VTT from the same tokens
 Burn-in alone does not satisfy ADA/WCAG and many platforms ignore uploaded tracks — so ship both. Group tokens into readable cues and serialize:
 ```ts
 const pad = (n: number, w = 2) => String(n).padStart(w, "0");
 const stamp = (ms: number, sep: string) => {
  const h = Math.floor(ms / 3.6e6), m = Math.floor(ms % 3.6e6 / 6e4),
        s = Math.floor(ms % 6e4 / 1000), x = ms % 1000;
  return `${pad(h)}:${pad(m)}:${pad(s)}${sep}${pad(x, 3)}`;
 };
 export const toSrt = (pages: Page[]) => pages.map((p, i) =>
  `${i + 1}\n${stamp(p.startMs, ",")} --> ${stamp(p.endMs, ",")}\n${p.tokens.map(t => t.text).join(" ")}`
 ).join("\n\n") + "\n";
 export const toVtt = (pages: Page[]) => "WEBVTT\n\n" + pages.map(p =>
  `${stamp(p.startMs, ".")} --> ${stamp(p.endMs, ".")}\n${p.tokens.map(t => t.text).join(" ")}`
 ).join("\n\n") + "\n";
 ```
 Use SRT for the broadest platform support; VTT when styling/positioning cues or serving on the web.
 ## 8. Per-platform safe areas (1080×1920, 9:16)
 | Platform | Bottom keep-clear | Top keep-clear | Side keep-clear | Notes |
 |---|---|---|---|---|
 | TikTok | ~340px | ~120px | ~110px right rail | Captions, audio title, action buttons crowd the bottom-right |
 | Instagram Reels | ~280px | ~130px | ~60px | Username/CTA bar at bottom |
 | YouTube Shorts | ~240px | ~100px | ~120px right rail | Title + channel at bottom-left |
 | Facebook Reels | ~300px | ~130px | ~80px | Similar to Reels |
 Safe rule across all: place caption baseline at ~62–70% of frame height, keep text within the center 80% width, and never let it enter the bottom ~15%.
 ## 9. Readable-type spec sheet
 | Property | Recommended | Floor |
 |---|---|---|
 | Weight | 800 (ExtraBold) | 700 |
 | Size @1080p | 56–80px | 45px |
 | Stroke | 4–6px solid #000 | 2px |
 | Shadow | `0 4px 16px rgba(0,0,0,.55)` | soft 1px |
 | Active accent | one color (e.g. #FFE45E) or filled box | — |
 | Lines on screen | 1–2 | 2 max |
 | Words per page | 1–4 | 5 max |
 Set `paint-order: stroke fill` so a thick stroke sits behind the glyph instead of eating it. Test on a bright frame and a busy frame; if it survives both, it ships.
 ## 10. Render
 ```bash
 npx remotion render src/index.ts Captions out/captions.mp4 \
  --props='{"pages": ..., "audio": "voiceover.wav"}'
 ```
 A 10-minute video with animated captions can take 30–60 min to render locally; render long-form in segments, or render on Remotion Lambda for parallel speed.
 ---
 ## Built by the team behind iart.ai
 This skill is part of an open motion-graphics collection from iart.ai — the AI motion agent that turns data, scripts, and designs into editable motion graphics (Remotion → MP4). If you'd rather not hand-build this, iart.ai can auto-time captions to a narration track and one-click burn them in from a template — change the text/audio and re-export. → [iart.ai](https://iart.ai/?utm_source=github&utm_medium=reference&utm_campaign=tiktok-video-skills&utm_content=ref_footer&utm_term=caption-animation)
@@ -0,0 +1,25 @@
 # Countdown Video
 Make a countdown that ends exactly when it should. The whole craft is one idea: derive the remaining time from the frame (or a monotonic timestamp), then format and animate that number — never count down with a `setInterval`. Covers livestream "starting soon" screens, launch and flash-sale countdowns, and looping backgrounds. For creators who need a timer that lands on zero on the exact frame.
 ## When it activates
 - "Make a countdown timer video" or "create a countdown animation."
 - "Build a stream starting soon countdown" or "do an event/launch/sale countdown."
 - "Animate a mm:ss or dd:hh:mm:ss timer."
 - "Add digit roll/flip transitions to a counter" or "loop a countdown background."
 ## Example prompts
 - "Build a 10-minute 'be right back' livestream countdown."
 - "Make a dd:hh:mm:ss launch countdown to a fixed target date."
 - "Add flip transitions to an mm:ss timer that hits zero on the exact frame."
 ## What's inside
 - `SKILL.md` — frame-accurate (drift-free) timers, time formatting, and a configurable duration prop.
 - `references/countdown-cookbook.md` — recipes for common countdown scenarios.
 - `references/digit-flip.md` — digit flip/roll transition techniques.
 ---
 Part of **[Short-Form Video Skills](../../)** · Built by **[iart.ai](https://iart.ai/?utm_source=github&utm_medium=readme&utm_campaign=tiktok-video-skills&utm_content=skill_footer&utm_term=countdown-video)** — the AI motion agent for editable, on-brand motion graphics.
@@ -0,0 +1,152 @@
 ---
 name: countdown-video
 description: This skill should be used when the user asks to "make a countdown timer video", "create a countdown animation", "build a stream starting soon countdown", "do an event/launch/sale countdown", "animate a mm:ss or dd:hh:mm:ss timer", "add digit roll/flip transitions to a counter", or "loop a countdown background". Covers frame-accurate (drift-free) timers, digit flip/roll motion, time formatting, and a configurable duration prop.
 version: 0.1.0
 ---
 # Countdown Video
 Make a countdown that ends exactly when it should. The whole craft is one idea: derive the remaining time from the frame (or a monotonic timestamp), then format and animate that number — never count down with a `setInterval`. Covers livestream "starting soon" screens, launch/sale countdowns, and looping backgrounds.
 ## When to use
 - "Starting soon" / "be right back" livestream screens with a 5–10 min timer.
 - Launch and flash-sale countdowns (dd:hh:mm:ss down to a target date; mm:ss for urgency).
 - Any animated counter where the number must land on zero on the exact frame.
 ## The one rule: drive the number from the clock, never a tick
 A `setInterval(fn, 1000)` countdown **drifts** — the callback fires *at least* 1000 ms later, never exactly, and stacks up when the tab is throttled or a render frame is slow. Reports of ~1 second lost per minute are common. The fix is the same for rendered video and live web: compute remaining time as a pure function of an authoritative clock, so a late frame self-corrects on the next frame instead of accumulating error.
 | Context | Authoritative clock | Remaining time |
 |---|---|---|
 | Remotion render | `useCurrentFrame()` | `total − frame/fps` |
 | Web (live page) | `performance.now()` or `Date.now()` | `targetMs − now` |
 | To a fixed date | `Date.now()` | `targetTimestamp − Date.now()` |
 Never store remaining time in state and decrement it. Recompute it every frame.
 ## Frame-accurate countdown (Remotion → MP4)
 `useCurrentFrame()` is deterministic: frame N is always rendered at exactly `N/fps` seconds. Subtract from the total and the timer is drift-free by construction.
 ```tsx
 import { useCurrentFrame, useVideoConfig } from "remotion";
 export const Countdown: React.FC<{ durationInSeconds: number }> = ({
  durationInSeconds,
 }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  // remaining seconds, clamped at 0 — ceil so "1" shows for its full second
  const elapsed = frame / fps;
  const remaining = Math.max(0, Math.ceil(durationInSeconds - elapsed));
  return <div style={{ fontVariantNumeric: "tabular-nums" }}>{formatMMSS(remaining)}</div>;
 };
 ```
 `durationInSeconds` is a **prop**, not a constant — the same composition renders a 5-minute stream timer or a 30-second sale timer by changing one input. Set the composition's `durationInFrames` to `durationInSeconds * fps` so the video is exactly as long as the countdown.
 ## Web timer (live page, requestAnimationFrame)
 For a live page, drive an rAF loop from `performance.now()` and only repaint when the displayed second changes (no work 60×/sec for a 1 Hz number):
 ```js
 const start = performance.now();
 let lastShown = -1;
 function tick(now) {
  const remaining = Math.max(0, Math.ceil(duration - (now - start) / 1000));
  if (remaining !== lastShown) { render(remaining); lastShown = remaining; }
  if (remaining > 0) requestAnimationFrame(tick);
 }
 requestAnimationFrame(tick);
 ```
 Counting down to a fixed date is the same idea with `Date.now()`: `Math.max(0, target - Date.now())`. See `references/countdown-cookbook.md` for the full date-target version with timezone handling.
 ## Time formatting
 Break a remaining-seconds integer into fields with division + modulo, then zero-pad. Pick the format to fit the duration — never show `00d 00h 05m` when minutes is all that matters.
 ```js
 const pad = (n) => String(n).padStart(2, "0");
 const formatMMSS = (s) => `${pad(Math.floor(s / 60))}:${pad(s % 60)}`;
 const formatDHMS = (s) => {
  const d = Math.floor(s / 86400), h = Math.floor((s % 86400) / 3600);
  const m = Math.floor((s % 3600) / 60), sec = s % 60;
  return `${pad(d)}:${pad(h)}:${pad(m)}:${pad(sec)}`;
 };
 ```
 | Format | Use | Drop fields when |
 |---|---|---|
 | `mm:ss` | stream "starting soon", short timers (<1h) | — |
 | `hh:mm:ss` | flash sale, same-day event | hide `dd` while 0 |
 | `dd:hh:mm:ss` | launch / multi-day countdown | hide leading 0 units for cleaner read |
 Always set `font-variant-numeric: tabular-nums` (or a monospace digit font) so digits keep equal width and the layout does not jitter as numbers change.
 ## Digit roll / flip transitions
 A flat number swap reads as cheap; the rolling "odometer" look sells the countdown. Render each digit as a vertical strip 0–9 and translate it by `-digit × digitHeight`. Animate the *position*, not the text content, so the change is a glide, not a pop.
 ```css
 .reel { height: 1em; overflow: hidden; }
 .reel .col { transition: transform .45s cubic-bezier(.22,1,.36,1); }
 /* col holds stacked 0..9; shift by -value em */
 ```
 In Remotion, drive the strip offset off the frame instead of a CSS transition (so it is deterministic). The flip-card style (top half folds down over the bottom) and the per-digit reel are both detailed, with runnable components, in `references/digit-flip.md`.
 ## Looping background
 Stream screens hold for minutes, so the background must loop seamlessly. Build motion on a cycle that divides evenly into the timeline (e.g. a gradient or particle drift whose period is `loopFrames`), and read it as `frame % loopFrames` so there is no visible seam at the wrap. Keep it low-contrast and slow — the number is the subject; the background is ambience. Recipes in `references/countdown-cookbook.md`.
 ## Output checklist
 - Remaining time recomputed from `useCurrentFrame()` / `performance.now()` every frame — no `setInterval` decrement.
 - Timer hits `00:00` on the exact intended frame; `durationInFrames === durationInSeconds × fps`.
 - Duration is an input prop, not a hardcoded constant.
 - Digits use `tabular-nums`; layout does not shift as numbers change.
 - Format matches the span (mm:ss vs dd:hh:mm:ss); leading zero units dropped when distracting.
 - Background loop period divides the timeline evenly; no seam at the wrap.
 ## Deliver & verify (rendered stills → MP4)
 > **Packaged helper** (`scripts/`): tile your stills with `scripts/contact-sheet.sh sheet.png f-hook.png f-mid.png f-end.png`, then assert the encode with `scripts/probe-mp4.sh out.mp4 [WxH] [fps]`. See `scripts/README.md`.
 The countdown ships as a Remotion composition (`<Composition>` + zod `schema` + `defaultProps`, `durationInSeconds` a prop) — the timer is a pure function of `useCurrentFrame()`, never `setInterval` / `Date.now()` / `Math.random()`. Set `durationInFrames = durationInSeconds * fps`. Deliverable = `out/*.mp4` + the project. 9:16 vertical (1080×1920) is the default.
 **Verify loop — render stills → inspect → encode.** The whole point is frame-accuracy, so check the *digit value* at exact frames before encoding.
 ```bash
 # Stills at start / mid / end — WITH SHIPPED PROPS (the real duration you'll render)
 npx remotion still Countdown out/f-start.png --frame=0   --props='{"durationInSeconds":300}'
 npx remotion still Countdown out/f-mid.png   --frame=N   --props='{"durationInSeconds":300}'
 npx remotion still Countdown out/f-end.png   --frame=L   --props='{"durationInSeconds":300}'  # L = durationInFrames-1
 # Inspect each PNG — the digits must read EXACTLY the frame/fps math:
 #  - at frame N, displayed = ceil(durationInSeconds - N/fps)  (e.g. 300s @ 30fps, frame 4500 → 150s → "02:30")
 #  - last frame reads 00:00 (or the end-state hold); no drift, no off-by-one second
 #  - tabular-nums: layout does not jitter between frames
 #  - 9:16 safe area: the timer + brand block sit clear of top ~12% and bottom ~20-35% UI and the right action rail
 npx remotion render Countdown out/countdown.mp4 --props='{"durationInSeconds":300}'   # encode once digits verify
 npx remotion render Countdown out/demo.gif --codec=gif                                 # README proof clip
 ```
 Use `npx remotion compositions` to confirm `durationInFrames`/`fps`, then compute the frame for any second you want to check.
 **Before you finish:**
 1. Stills render cleanly at frame 0, mid, and last — no errors.
 2. The digit value at frame N equals `ceil(durationInSeconds - N/fps)` exactly; last frame hits 00:00 on the intended frame (no drift / off-by-one).
 3. Timer + brand stay inside the 9:16 safe area at every checked frame.
 4. Frame-driven only — no `setInterval` / `Date.now()` / timers; `tabular-nums` so layout holds.
 5. Shipped `durationInSeconds` (not just `defaultProps`) renders correctly; MP4 encoded, GIF optional.
 ## Reference files
 - `references/countdown-cookbook.md` — complete runnable Remotion `<Countdown>` (configurable duration, mm:ss / dd:hh:mm:ss, end-state hold), the count-down-to-a-fixed-date web component with timezone handling, a "starting soon" stream-screen layout (brand block + social handles + looping gradient background), and the seamless-loop background pattern.
 - `references/digit-flip.md` — two deterministic digit-animation components: the odometer reel (vertical 0–9 strip driven by frame) and the flip-card (top-half fold) effect, plus when each suits launch vs sale vs stream.
@@ -0,0 +1,205 @@
 # Countdown Cookbook
 Complete, runnable recipes. Every value is derived from an authoritative clock (frame or timestamp) so nothing drifts.
 ## 1. Configurable Remotion countdown (mm:ss + dd:hh:mm:ss)
 A single composition that handles any duration and either format. Drop into `src/Countdown.tsx`.
 ```tsx
 import React from "react";
 import { useCurrentFrame, useVideoConfig, AbsoluteFill } from "remotion";
 const pad = (n: number) => String(n).padStart(2, "0");
 const formatTime = (totalSeconds: number, mode: "mm:ss" | "dd:hh:mm:ss") => {
  const s = Math.max(0, totalSeconds);
  if (mode === "mm:ss") {
    return `${pad(Math.floor(s / 60))}:${pad(s % 60)}`;
  }
  const d = Math.floor(s / 86400);
  const h = Math.floor((s % 86400) / 3600);
  const m = Math.floor((s % 3600) / 60);
  const sec = s % 60;
  // drop leading day field once it is zero, for a cleaner read
  return d > 0
    ? `${pad(d)}d ${pad(h)}:${pad(m)}:${pad(sec)}`
    : `${pad(h)}:${pad(m)}:${pad(sec)}`;
 };
 export type CountdownProps = {
  durationInSeconds: number;
  format?: "mm:ss" | "dd:hh:mm:ss";
  label?: string;
 };
 export const Countdown: React.FC<CountdownProps> = ({
  durationInSeconds,
  format = "mm:ss",
  label = "",
 }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  // ceil so the last whole second ("1") is shown for its full duration,
  // and the display reaches "0" exactly on the final frame.
  const remaining = Math.max(0, Math.ceil(durationInSeconds - frame / fps));
  const ended = remaining === 0;
  return (
    <AbsoluteFill
      style={{
        justifyContent: "center",
        alignItems: "center",
        background: "#0b0d17",
        color: "#fff",
        fontFamily: "Inter, system-ui, sans-serif",
      }}
    >
      {label && (
        <div style={{ fontSize: 36, opacity: 0.7, marginBottom: 16, letterSpacing: 4 }}>
          {label.toUpperCase()}
        </div>
      )}
      <div
        style={{
          fontSize: 180,
          fontWeight: 800,
          fontVariantNumeric: "tabular-nums", // equal-width digits → no jitter
          lineHeight: 1,
          color: ended ? "#ff4d4d" : "#fff",
        }}
      >
        {ended ? formatTime(0, format) : formatTime(remaining, format)}
      </div>
    </AbsoluteFill>
  );
 };
 ```
 Register it so `durationInFrames` matches the countdown exactly — the video ends when the timer does:
 ```tsx
 import { Composition } from "remotion";
 import { Countdown } from "./Countdown";
 const FPS = 30;
 const DURATION_SECONDS = 300; // 5-minute "starting soon" timer
 export const RemotionRoot = () => (
  <Composition
    id="Countdown"
    component={Countdown}
    durationInFrames={DURATION_SECONDS * FPS}
    fps={FPS}
    width={1920}
    height={1080}
    defaultProps={{ durationInSeconds: DURATION_SECONDS, format: "mm:ss", label: "Starting soon" }}
  />
 );
 ```
 Render any duration/format without touching code — duration is a prop:
 ```bash
 npx remotion render Countdown out/sale.mp4 \
  --props='{"durationInSeconds":86400,"format":"dd:hh:mm:ss","label":"Sale ends in"}'
 ```
 To hold a final state (e.g. "WE'RE LIVE") instead of ending on `00:00`, extend `durationInFrames` past the countdown and branch on `ended`.
 ## 2. Count down to a fixed date (live web component)
 For a real-time page that targets a calendar moment. Drift-free because remaining time is `target − Date.now()` recomputed each frame, never a decrement.
 ```js
 // targetISO must include an offset, e.g. "2026-07-01T09:00:00-07:00",
 // so the deadline is unambiguous regardless of the viewer's timezone.
 function startCountdown(targetISO, el) {
  const target = new Date(targetISO).getTime();
  const pad = (n) => String(n).padStart(2, "0");
  let lastShown = -1;
  function tick() {
    const remainingMs = Math.max(0, target - Date.now());
    const s = Math.floor(remainingMs / 1000);
    if (s !== lastShown) {
      const d = Math.floor(s / 86400);
      const h = Math.floor((s % 86400) / 3600);
      const m = Math.floor((s % 3600) / 60);
      el.textContent = `${pad(d)}:${pad(h)}:${pad(m)}:${pad(s % 60)}`;
      lastShown = s;
    }
    if (remainingMs > 0) requestAnimationFrame(tick);
    else el.textContent = "00:00:00:00"; // or swap to an "It's live" state
  }
  requestAnimationFrame(tick);
 }
 ```
 Timezone notes:
 - Bake the offset into the target string (`-07:00`, `Z`). A bare `"2026-07-01T09:00:00"` is parsed as the viewer's *local* time and every viewer sees a different deadline.
 - To show "ends 9am in *your* timezone everywhere," instead pick the wall-clock time per locale and let each viewer's `Date` resolve it — but that is a different deadline per region. Decide which you want before building.
 ## 3. "Starting soon" stream screen
 Livestream lead-in screens hold 5–10 minutes: a clean brand block, social handles, and a calm looping background, with the timer as the focal point. Keep it low-clutter — chat and music carry the wait; the screen just signals "we're about to start."
 ```tsx
 import { AbsoluteFill, useCurrentFrame, useVideoConfig, interpolate } from "remotion";
 export const StartingSoon: React.FC<{ durationInSeconds: number; handle: string; brand: string }> = ({
  durationInSeconds,
  handle,
  brand,
 }) => {
  const frame = useCurrentFrame();
  const { fps, durationInFrames } = useVideoConfig();
  const remaining = Math.max(0, Math.ceil(durationInSeconds - frame / fps));
  const pad = (n: number) => String(n).padStart(2, "0");
  // seamless looping gradient: angle cycles over loopFrames with no seam
  const loopFrames = fps * 8;
  const angle = interpolate(frame % loopFrames, [0, loopFrames], [0, 360]);
  return (
    <AbsoluteFill
      style={{
        background: `linear-gradient(${angle}deg, #141a3a, #0b0d17 60%)`,
        color: "#fff",
        fontFamily: "Inter, system-ui, sans-serif",
        justifyContent: "center",
        alignItems: "center",
      }}
    >
      <div style={{ fontSize: 64, fontWeight: 800, marginBottom: 8 }}>{brand}</div>
      <div style={{ fontSize: 28, opacity: 0.6, letterSpacing: 6, marginBottom: 40 }}>
        STARTING SOON
      </div>
      <div style={{ fontSize: 200, fontWeight: 800, fontVariantNumeric: "tabular-nums", lineHeight: 1 }}>
        {pad(Math.floor(remaining / 60))}:{pad(remaining % 60)}
      </div>
      <div style={{ position: "absolute", bottom: 60, fontSize: 30, opacity: 0.7 }}>{handle}</div>
    </AbsoluteFill>
  );
 };
 ```
 Export as MP4 and add it as a Media/Video source in OBS, or use a looping playout for a browser source. Common durations: 300s (5 min) or 600s (10 min) at 1920×1080.
 ## 4. Seamless looping background
 Any motion whose period divides the timeline evenly wraps without a seam. Read animation phase as `frame % loopFrames` so the value at the wrap equals the value at frame 0.
 ```tsx
 const loopFrames = fps * 6;            // one full cycle every 6 seconds
 const phase = (frame % loopFrames) / loopFrames; // 0 → 1, repeats
 const driftY = Math.sin(phase * Math.PI * 2) * 40; // returns to start each cycle
 ```
 Use sine/cosine (inherently periodic) or `interpolate(frame % loopFrames, [0, loopFrames], [a, a])` with matching start/end so there is no jump. Keep contrast low and motion slow — the number is the subject.
 ---
 ## Built by the team behind iart.ai
 This skill is part of an open motion-graphics collection from iart.ai — the AI motion agent that turns data, scripts, and designs into editable motion graphics (Remotion → MP4). If you'd rather not hand-build this, iart.ai can render countdown videos from a template with a set time and brand — change the text/data and re-export. → [iart.ai](https://iart.ai/?utm_source=github&utm_medium=reference&utm_campaign=tiktok-video-skills&utm_content=ref_footer&utm_term=countdown-video)
@@ -0,0 +1,146 @@
 # Digit Flip & Roll Transitions
 Two ways to animate a digit changing. Both are driven by the frame (deterministic) so they render identically every time — no CSS transition clock that the renderer can disagree with.
 Pick by tone:
 | Effect | Feel | Best for |
 |---|---|---|
 | Odometer reel | smooth, continuous glide | launch countdowns, premium/minimal timers |
 | Flip card | mechanical "snap", split-flap board | sale urgency, retro/airport-board style |
 ## Shared idea
 A single displayed digit is a stack of glyphs `0..9` laid out vertically. Showing digit `d` means translating the stack so glyph `d` sits in the window: `translateY(-d × digitHeight)`. Animate the *offset*, not the text, and you get a roll. The trick for a countdown is that the offset is continuous: between whole seconds the digit eases from its old value toward its new one.
 ## Odometer reel (Remotion, frame-driven)
 ```tsx
 import React from "react";
 import { useCurrentFrame, useVideoConfig, interpolate, Easing } from "remotion";
 const DIGIT_H = 160; // px per glyph
 const ROLL_FRAMES = 12; // how long a single digit roll takes
 // Animated single digit: rolls from `prev` to `value` over the last ROLL_FRAMES
 // of the current second.
 const Reel: React.FC<{ value: number; prev: number; secondProgress: number }> = ({
  value,
  prev,
  secondProgress,
 }) => {
  // secondProgress: 0→1 across the current whole second.
  // Start the roll near the end of the second so the number "settles" on change.
  const t = interpolate(secondProgress, [0.7, 1], [0, 1], {
    extrapolateLeft: "clamp",
    extrapolateRight: "clamp",
    easing: Easing.bezier(0.22, 1, 0.36, 1),
  });
  // continuous position between prev and value
  const shown = prev + (value - prev) * t;
  const offset = -shown * DIGIT_H;
  return (
    <div style={{ height: DIGIT_H, width: 110, overflow: "hidden", position: "relative" }}>
      <div style={{ transform: `translateY(${offset}px)` }}>
        {[0, 1, 2, 3, 4, 5, 6, 7, 8, 9].map((n) => (
          <div
            key={n}
            style={{
              height: DIGIT_H,
              lineHeight: `${DIGIT_H}px`,
              textAlign: "center",
              fontSize: 140,
              fontWeight: 800,
              fontVariantNumeric: "tabular-nums",
            }}
          >
            {n}
          </div>
        ))}
      </div>
    </div>
  );
 };
 // Renders an mm:ss reel where each digit rolls.
 export const ReelClock: React.FC<{ durationInSeconds: number }> = ({ durationInSeconds }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const elapsed = frame / fps;
  const remaining = Math.max(0, Math.ceil(durationInSeconds - elapsed));
  const prevRemaining = Math.max(0, remaining + 1); // value one second ago
  const secondProgress = elapsed % 1; // 0→1 within the current second
  const digits = (s: number) =>
    [Math.floor(s / 600) % 10, Math.floor(s / 60) % 10, Math.floor(s / 10) % 10, s % 10];
  const cur = digits(remaining);
  const prev = digits(prevRemaining);
  return (
    <div style={{ display: "flex", gap: 8, color: "#fff", background: "#0b0d17", padding: 40 }}>
      {cur.map((d, i) => (
        <React.Fragment key={i}>
          {i === 2 && <div style={{ fontSize: 140, fontWeight: 800 }}>:</div>}
          <Reel value={d} prev={prev[i]} secondProgress={secondProgress} />
        </React.Fragment>
      ))}
    </div>
  );
 };
 ```
 Notes:
 - Each digit only rolls when it actually changes; a digit whose `prev === value` sits still because `shown` stays constant.
 - A `9 → 0` rollover rolls *backward* through the strip (the cheap-looking part). To make tens/units roll the natural way on a carry, render an extra `0` glyph below the `9` and clamp — covered as an exercise; for most timers the backward roll at the tens boundary is unnoticeable at speed.
 - `ROLL_FRAMES` is unused above because the roll is tied to `secondProgress`; expose it instead if a fixed-length roll is preferred.
 ## Flip card (split-flap)
 The top half of the old digit folds down over a static bottom half, revealing the new digit. Pure CSS keyframe version — fine for a live web page; for Remotion, drive the `rotateX` off `secondProgress` the same way as the reel so it stays deterministic.
 ```css
 .flip { position: relative; width: 110px; height: 160px; perspective: 600px; }
 .flip .card {
  position: absolute; inset: 0;
  display: flex; align-items: center; justify-content: center;
  font-size: 140px; font-weight: 800; font-variant-numeric: tabular-nums;
  backface-visibility: hidden;
 }
 .flip .top    { clip-path: inset(0 0 50% 0); transform-origin: bottom; }
 .flip .bottom { clip-path: inset(50% 0 0 0); }
 /* on change, animate the leaf folding down */
 .flip .leaf {
  position: absolute; inset: 0; transform-origin: bottom;
  animation: fold .45s cubic-bezier(.36,0,.66,-0.2) forwards;
 }
@keyframes fold {
  0%   { transform: rotateX(0deg); }
  100% { transform: rotateX(-90deg); }
 }
 ```
 ```js
 // swap the digit and replay the fold whenever the value changes
 function setFlip(el, newDigit) {
  if (el.dataset.v === String(newDigit)) return; // no change → no flip
  el.dataset.v = String(newDigit);
  el.querySelector(".top").textContent = newDigit;
  el.querySelector(".bottom").textContent = newDigit;
  const leaf = el.querySelector(".leaf");
  leaf.textContent = newDigit;
  leaf.style.animation = "none";
  void leaf.offsetWidth;            // reflow → restart the animation
  leaf.style.animation = "";
 }
 ```
 Drive `setFlip` from the same `requestAnimationFrame` + `performance.now()` loop in the cookbook (only call it when the displayed second changes), so the flips fire on real time and never drift.
 ## Choosing
 - **Launch / premium:** odometer reel, slow ease, large tabular digits, muted palette.
 - **Flash sale:** flip card for the mechanical urgency, or reel with a faster roll and a hot accent color on `mm:ss`.
 - **Stream "starting soon":** either works, but keep it calm — a single reel on `mm:ss` reads better than a busy split-flap for a 5–10 minute hold.
@@ -0,0 +1,24 @@
 # Lower Thirds
 Build a clean, branded lower third — the name/role caption that lives in the bottom band of the frame — that animates in, holds long enough to read, and exits without stealing the shot. The craft is restraint: a crisp reveal, a strong type hierarchy, correct safe-area placement, and one template that drives a whole roster of speakers. For creators producing interviews, panels, podcasts, and broadcast-style titles.
 ## When it activates
 - "Make an animated lower third" or "add lower thirds."
 - "Create a name tag/name lower third" or "do a speaker name overlay."
 - "Build broadcast titles" or "animate a title/name/role caption."
 - "Template lower thirds across a list of names."
 ## Example prompts
 - "Add a lower third with the speaker's name and role, branded to my colors."
 - "Build a staggered slide-in name plate for a podcast guest."
 - "Template one lower-third design across a roster of 12 panelists."
 ## What's inside
 - `SKILL.md` — enter/exit animation, in/out timing and dwell, safe-area conventions, and brand styling.
 - `references/lower-third-component.md` — a reusable lower-third component.
 ---
 Part of **[Short-Form Video Skills](../../)** · Built by **[iart.ai](https://iart.ai/?utm_source=github&utm_medium=readme&utm_campaign=tiktok-video-skills&utm_content=skill_footer&utm_term=lower-thirds)** — the AI motion agent for editable, on-brand motion graphics.
@@ -0,0 +1,146 @@
 ---
 name: lower-thirds
 description: This skill should be used when the user asks to "make an animated lower third", "add lower thirds", "create a name tag/name lower third", "build broadcast titles", "animate a title/name/role caption", "do a speaker name overlay", or "template lower thirds across a list of names". Covers enter/exit animation (slide/wipe/mask reveal), in/out timing & dwell, safe-area & broadcast conventions, name-vs-role type hierarchy, brand styling, and rendering one design across many names.
 version: 0.1.0
 ---
 # Lower Thirds
 Build a clean, branded lower third — the name/role caption that lives in the bottom band of the frame — that animates in, holds long enough to read, and exits without stealing the shot. The craft is restraint: a crisp reveal, a strong type hierarchy, correct safe-area placement, and one template that drives a whole roster of speakers.
 ## When to use
 - Speaker/interview name tags, panel rosters, talking-head captions.
 - Broadcast-style titles, news straps, podcast/webinar name plates.
 - Templating one design across a list of names/titles → many clips (the payoff).
 ## Anatomy
 A lower third is two text lines plus a graphic bed, placed in the lower band:
 | Element | Role | Type treatment |
 |---|---|---|
 | **Name** (primary) | Who | Largest, heaviest, tightest tracking |
 | **Role/title** (secondary) | What/where | ~45–60% of name size, lighter weight, often a brand accent color |
 | **Bar / panel / accent** | Reads against any background | Solid or 70–85% opacity; an accent rule ties to brand |
 Keep it to two lines. A name line + role line is the whole job — extra lines erode the hierarchy and crowd the safe area.
 ## Three rules that prevent cheap-looking titles
 1. **Never hard-cut a title on or off.** A bare appear/disappear reads as a mistake. Even a 12-frame fade or slide makes it feel produced.
 2. **Stagger, don't slam.** Animate the bar first, then the name, then the role, each offset by 3–6 frames. Everything arriving at once feels flat; a short cascade feels designed.
 3. **Hold long enough to read twice.** Roughly 3–5s on screen (read it aloud twice). Too short and it's missed; too long and it nags. Animate in/out, never mid-segment.
 ## Enter & exit animations
 Pick one motion language and reuse it. The most reliable, premium-reading reveals:
 | Reveal | Feel | How |
 |---|---|---|
 | **Slide + fade** | Clean, default | Translate in ~24–40px while fading; ease-out on enter |
 | **Wipe bar** | Broadcast | A bar scales/sweeps in (`scaleX`/clip), text fades behind it |
 | **Mask reveal** | Premium | Clip text to a moving rectangle so letters "wipe on" |
 Use asymmetric easing: a snappy `ease-out` (`cubic-bezier(.22,1,.36,1)`) on enter, a quicker `ease-in` on exit. Exit faster than you entered (~⅔ the duration) so the title gets out of the way.
 ```css
 /* Mask reveal: text wipes on left→right, no plugin needed */
 .lt-name { clip-path: inset(0 100% 0 0); animation: wipe .5s cubic-bezier(.22,1,.36,1) forwards; }
@keyframes wipe { to { clip-path: inset(0 0 0 0); } }
 ```
 ## In/out timing & dwell
 Think in three phases. Budget frames, not vibes (at 30fps):
 | Phase | Budget | Note |
 |---|---|---|
 | Enter | 12–18f (0.4–0.6s) | Staggered: bar → name → role |
 | Hold | 90–150f (3–5s) | The readable dwell; scale with line length |
 | Exit | 8–12f (0.27–0.4s) | Faster than enter |
 In code, drive every state from the current frame (or a paused timeline), not wall-clock time — a video renderer demands deterministic frames. Express enter/hold/exit as a single progress curve so the same component works live in a browser and frame-by-frame in a renderer.
 ## Safe area & broadcast conventions
 The lower third must survive every screen and platform UI. Compose inside the **title-safe area** (inner ~90% / margin 5%) and respect platform chrome:
 | Frame | Anchor | Avoid |
 |---|---|---|
 | 16:9 (1920×1080) | Left edge at ~5% margin; baseline ~80–85% down | Outer 5% (title-safe), action-safe outer 10% |
 | 9:16 (1080×1920) | Same left margin; **lift the band up** | Bottom ~18% (captions/UI), top ~12% |
 | 1:1 (1080×1080) | Lower band, center-left | Outer 5% |
 Anchor to the **left** and grow rightward so names of different lengths stay pinned and never re-center awkwardly. Keep the role line within the same left margin as the name. For 9:16, do not park the title at the very bottom — platform captions and buttons sit there.
 ## Type hierarchy & brand styling
 Hierarchy is the whole design. Make the name unmistakably dominant:
 - **Size contrast** ≥ 1.6× (name vs role). If unsure, push the name bigger, not the role.
 - **Weight + color**: name in bold/near-white; role in a lighter weight and a **brand accent** color (one accent, used consistently).
 - **Contrast for legibility**: text rides over unknown footage. Use a solid/semi-opaque bar, a subtle scrim, or a soft text shadow so it reads over both bright and dark plates.
 - **Brand lock**: pin font, accent color, bar style, and corner radius in one theme object so every title across a series matches.
 ## Templating one design across a list
 The reason to build this in code: change the text/data, re-export — no re-animating. Make name/role/theme **props**, never hardcoded, then map a roster to instances.
 ```jsx
 const ROSTER = [
  { name: "Ada Lovelace",  role: "Founder, Analytical Engines" },
  { name: "Grace Hopper",  role: "Rear Admiral, US Navy" },
  { name: "Alan Turing",   role: "Mathematician" },
 ];
 // One <LowerThird> design; map the list → many instances (sequence them in a renderer)
 {ROSTER.map((p, i) => <LowerThird key={p.name} {...p} theme={BRAND} startFrame={i * 150} />)}
 ```
 In a renderer, make the roster an input prop and render once per row (`--props`) to emit one branded clip per person — same animation, same brand, only the text changes. See `references/lower-third-component.md` for the full runnable component and batch script.
 ## Output checklist
 - Two lines only: dominant name, secondary role (≥1.6× size contrast).
 - Animated in and out (no hard cut); enter staggered bar→name→role; exit faster.
 - Hold 3–5s (readable twice); motion only at the ends, never mid-segment.
 - Left-anchored inside title-safe; 9:16 band lifted above the bottom-18% UI zone.
 - Text legible over any plate (bar/scrim/shadow); one brand accent throughout.
 - Name/role/theme are props — one template renders the whole roster.
 ## Deliver & verify (rendered stills → MP4)
 > **Packaged helper** (`scripts/`): tile your stills with `scripts/contact-sheet.sh sheet.png f-hook.png f-mid.png f-end.png`, then assert the encode with `scripts/probe-mp4.sh out.mp4 [WxH] [fps]`. See `scripts/README.md`.
 The lower third ships as a Remotion composition (`<Composition>` + zod `schema` + `defaultProps`, name/role/theme as props) — enter/dwell/exit all driven by `useCurrentFrame()`, never `Date.now()` / `Math.random()` / timers. Deliverable = `out/*.mp4` + the project (re-render per roster row). 9:16 vertical (1080×1920) is the default.
 **Verify loop — render stills → inspect → encode.** Sample the three phases so you catch a stagger or safe-area bug before encoding (or batching the whole roster).
 ```bash
 # Stills at enter / dwell / exit — WITH SHIPPED PROPS (a real roster row, not defaults)
 npx remotion still LowerThird out/f-enter.png --frame=10  --props='{"name":"Ada Lovelace","role":"Founder, Analytical Engines"}'
 npx remotion still LowerThird out/f-dwell.png --frame=75  --props='{"name":"Ada Lovelace","role":"Founder, Analytical Engines"}'
 npx remotion still LowerThird out/f-exit.png  --frame=N   --props='{"name":"Ada Lovelace","role":"Founder, Analytical Engines"}'
 # Inspect each PNG — focus the DWELL frame (fully on screen):
 #  - hierarchy holds: name dominant (>=1.6x role), role in brand accent; both fully revealed, not mid-wipe
 #  - brand lock: font, accent color, bar/scrim correct; legible over the plate
 #  - 9:16 safe area: band LIFTED above the bottom ~20-35% UI zone, clear of top ~12% and the right action rail; left-anchored inside title-safe
 #  - enter/exit frames show partial reveal (animation actually runs), not a hard cut
 npx remotion render LowerThird out/lower-third.mp4 --props='{"name":"Ada Lovelace","role":"Founder, Analytical Engines"}'
 npx remotion render LowerThird out/demo.gif --codec=gif                # README proof clip
 ```
 **Batch roster**: verify ONE row via stills *before* rendering all names — catch a layout/overflow bug once, not N times. Use `npx remotion compositions` for `durationInFrames`/`fps` to pick the dwell + exit frames.
 **Before you finish:**
 1. Stills render cleanly at enter, dwell, and exit — no missing font/brand assets.
 2. At the dwell frame: name dominant over role, brand accent + bar correct, fully (not partly) revealed.
 3. The band is inside the 9:16 safe area — lifted above the bottom UI zone, clear of top and right rail — at every checked frame.
 4. Frame-driven only — no `Date.now()` / `Math.random()` / timers; enter/exit show motion, never a hard cut.
 5. A real roster row (not `defaultProps`) renders correctly; MP4 encoded, GIF optional.
 ## Reference files
 - `references/lower-third-component.md` — a complete runnable lower-third: a Remotion component with staggered spring enter, readable hold, and faster exit driven purely by frame; a typed theme object for brand lock; the list→many-instances sequencing pattern; a per-row batch render script; plus a dependency-free CSS/HTML version of the same design with mask-reveal and wipe-bar variants.
@@ -0,0 +1,268 @@
 # Lower-Third Component — runnable code
 A complete, production-grade lower third you can drop in. Two paths:
 1. **Remotion** (frame-deterministic, renders to MP4, batches over a roster).
 2. **CSS/HTML** (no dependencies, for the web or a quick preview) with mask-reveal and wipe-bar variants.
 Both share the same design language: a left-anchored bar, a dominant name, a brand-accent role line, a staggered enter, a readable hold, and a faster exit.
 ---
 ## 1. Remotion component (props-driven, frame-deterministic)
 The animation is a pure function of `frame`, so it renders identically every time and stays in sync with the renderer. Enter staggers the bar, name, then role; exit is computed from the end of the clip so the title leaves faster than it arrived.
 ```tsx
 // LowerThird.tsx
 import {
  AbsoluteFill, Sequence, interpolate, spring,
  useCurrentFrame, useVideoConfig,
 } from "remotion";
 // --- Brand lock: change once, every title matches -------------------------
 export type Theme = {
  font: string;
  bar: string;        // panel/bar color
  name: string;       // primary text color
  role: string;       // accent color for the role line
  radius: number;
  marginPct: number;  // left/safe margin as % of width
 };
 export const BRAND: Theme = {
  font: "Inter, system-ui, sans-serif",
  bar: "rgba(12,14,22,0.86)",
  name: "#FFFFFF",
  role: "#6EE7F0",     // single brand accent
  radius: 10,
  marginPct: 5,
 };
 export type LowerThirdProps = {
  name: string;
  role: string;
  theme?: Theme;
  holdSeconds?: number; // readable dwell, default 4s
 };
 // Staggered enter via spring; exit via a quick fade/slide near the end.
 const useEnterExit = (delayFrames: number, holdSeconds: number) => {
  const frame = useCurrentFrame();
  const { fps, durationInFrames } = useVideoConfig();
  // ENTER: spring 0→1, offset by delayFrames (the cascade)
  const enter = spring({
    frame: frame - delayFrames,
    fps,
    config: { damping: 200, stiffness: 180, mass: 0.6 },
  });
  // EXIT: faster than enter — last 10 frames of the clip
  const exitStart = durationInFrames - 10;
  const exit = interpolate(frame, [exitStart, durationInFrames], [1, 0], {
    extrapolateLeft: "clamp",
    extrapolateRight: "clamp",
  });
  const opacity = enter * exit;
  const x = interpolate(enter, [0, 1], [-32, 0]); // slide in from left
  return { opacity, x };
 };
 const Line: React.FC<{
  delay: number; holdSeconds: number; children: React.ReactNode;
  size: number; weight: number; color: string; tracking?: number;
 }> = ({ delay, holdSeconds, children, size, weight, color, tracking = 0 }) => {
  const { opacity, x } = useEnterExit(delay, holdSeconds);
  return (
    <div style={{
      opacity,
      transform: `translateX(${x}px)`,
      fontSize: size, fontWeight: weight, color,
      letterSpacing: tracking, lineHeight: 1.15, whiteSpace: "nowrap",
    }}>
      {children}
    </div>
  );
 };
 export const LowerThird: React.FC<LowerThirdProps> = ({
  name, role, theme = BRAND, holdSeconds = 4,
 }) => {
  const { width, height } = useVideoConfig();
  const bar = useEnterExit(0, holdSeconds); // bar leads the cascade
  const left = (width * theme.marginPct) / 100;
  const baseline = height * 0.80;            // sit ~80% down, inside title-safe
  return (
    <AbsoluteFill style={{ fontFamily: theme.font }}>
      <div style={{
        position: "absolute", left, top: baseline,
        opacity: bar.opacity,
        transform: `translateX(${bar.x}px)`,
      }}>
        {/* panel behind text guarantees legibility over any plate */}
        <div style={{
          background: theme.bar, borderRadius: theme.radius,
          padding: "14px 22px 16px",
          borderLeft: `4px solid ${theme.role}`,   // accent rule ties to brand
          backdropFilter: "blur(6px)",
        }}>
          <Line delay={4}  holdSeconds={holdSeconds} size={46} weight={800} color={theme.name} tracking={-0.5}>
            {name}
          </Line>
          <Line delay={8}  holdSeconds={holdSeconds} size={26} weight={500} color={theme.role}>
            {role}
          </Line>
        </div>
      </div>
    </AbsoluteFill>
  );
 };
 ```
 Why each choice matters:
 - **`spring` per line, offset by `delay`** gives the bar→name→role cascade. Same offsets everywhere keep titles consistent.
 - **Exit derived from `durationInFrames`** means any clip length exits cleanly without per-instance tuning, and it's quicker than the enter (10f vs the spring's settle).
 - **`whiteSpace: nowrap` + left anchor** keeps long and short names pinned to the same edge — no awkward re-centering across a roster.
 - **`borderLeft` accent + semi-opaque panel** is the brand tie plus the legibility guarantee over unknown footage.
 ### Roster → many instances (one design, a whole panel)
 Sequence the same component down a list. Each person gets a slot; only the text changes.
 ```tsx
 // Roster.tsx
 import { Series } from "remotion";
 import { LowerThird, BRAND } from "./LowerThird";
 const ROSTER = [
  { name: "Ada Lovelace", role: "Founder, Analytical Engines" },
  { name: "Grace Hopper", role: "Rear Admiral, US Navy" },
  { name: "Alan Turing",  role: "Mathematician" },
 ];
 export const Roster: React.FC = () => (
  <Series>
    {ROSTER.map((p) => (
      <Series.Sequence key={p.name} durationInFrames={150 /* ~5s @30fps */}>
        <LowerThird name={p.name} role={p.role} theme={BRAND} />
      </Series.Sequence>
    ))}
  </Series>
 );
 ```
 ### Batch: one branded clip per person
 Make the roster an input prop and render once per row, so each speaker becomes a standalone overlay clip — identical animation and brand, only the text differs.
 ```bash
 #!/usr/bin/env bash
 # render one transparent-friendly lower-third clip per person in roster.json
 # roster.json: [{"name":"Ada Lovelace","role":"Founder, Analytical Engines"}, ...]
 set -euo pipefail
 mkdir -p out
 jq -c '.[]' roster.json | while read -r row; do
  slug=$(echo "$row" | jq -r '.name' | tr '[:upper:] ' '[:lower:]-')
  npx remotion render LowerThird "out/${slug}.mp4" --props="$row"
 done
 ```
 For overlay-ready output with transparency, render the `LowerThird` composition (transparent background) to a codec that keeps alpha, e.g. `--codec=prores --prores-profile=4444`, or `--image-format=png` for a PNG sequence.
 ---
 ## 2. CSS / HTML version (no dependencies)
 The same design without a framework — for the web, OBS browser sources, or a fast look-test. Includes both a **slide+fade** default and a **mask-reveal** name, plus a **wipe-bar** variant.
 ```html
 <div class="lt" style="--accent:#6EE7F0">
  <div class="lt-bar">
    <div class="lt-name">Ada Lovelace</div>
    <div class="lt-role">Founder, Analytical Engines</div>
  </div>
 </div>
 <style>
 :root { font-family: Inter, system-ui, sans-serif; }
 .lt {
  position: absolute; left: 5%; top: 80%;   /* title-safe, left-anchored */
 }
 .lt-bar {
  display: inline-block;
  background: rgba(12,14,22,0.86);
  backdrop-filter: blur(6px);
  border-left: 4px solid var(--accent);
  border-radius: 10px;
  padding: 14px 22px 16px;
  /* bar leads the cascade: slide + fade in, then a faster fade out */
  animation: lt-in .5s cubic-bezier(.22,1,.36,1) both,
             lt-out .3s ease-in 4.5s forwards;     /* hold ~4s, exit faster */
 }
 .lt-name {
  font-size: 46px; font-weight: 800; color: #fff; letter-spacing: -.5px;
  line-height: 1.15; white-space: nowrap;
  /* MASK REVEAL: letters wipe on left→right, staggered after the bar */
  clip-path: inset(0 100% 0 0);
  animation: lt-wipe .5s cubic-bezier(.22,1,.36,1) .12s forwards;
 }
 .lt-role {
  font-size: 26px; font-weight: 500; color: var(--accent);
  line-height: 1.15; white-space: nowrap;
  opacity: 0;
  animation: lt-fade .4s ease-out .22s forwards;   /* role arrives last */
 }
@keyframes lt-in   { from { opacity: 0; transform: translateX(-32px); }
                     to   { opacity: 1; transform: none; } }
@keyframes lt-out  { to   { opacity: 0; transform: translateX(-16px); } }
@keyframes lt-wipe { to   { clip-path: inset(0 0 0 0); } }
@keyframes lt-fade { to   { opacity: 1; } }
 /* Mobile/9:16: lift the band above the bottom UI/caption zone */
@media (max-aspect-ratio: 1/1) { .lt { top: 70%; } }
 </style>
 ```
 ### Wipe-bar variant (broadcast feel)
 Swap the bar animation so a colored bar sweeps in and the text rides behind it:
 ```css
 .lt-bar.wipe {
  position: relative; overflow: hidden;
  animation: lt-in .45s cubic-bezier(.22,1,.36,1) both,
             lt-out .3s ease-in 4.5s forwards;
 }
 .lt-bar.wipe::before {
  content: ""; position: absolute; inset: 0;
  background: var(--accent);
  transform-origin: left;
  animation: lt-sweep .55s cubic-bezier(.76,0,.24,1) both;  /* sweep across, then reveal */
 }
@keyframes lt-sweep { 0% { transform: scaleX(0); } 60% { transform: scaleX(1); }
                      100% { transform: scaleX(0); transform-origin: right; } }
 ```
 The CSS clock (`animation`) is fine for live/web playback. For a deterministic MP4, prefer the Remotion path above — a frame renderer and CSS timers disagree, which causes flicker or desync at export.
 ---
 ## Quick reference
 | Need | Knob |
 |---|---|
 | Slower/faster reveal | enter duration 12–18f / `.5s` |
 | Longer dwell | `holdSeconds` / the `4.5s` exit delay |
 | Bigger name dominance | name `fontSize` (keep ≥1.6× the role) |
 | Rebrand everything | the `BRAND` theme object / `--accent` |
 | 9:16 placement | `baseline 0.80→0.70` / the media query |
 ---
 ## Built by the team behind iart.ai
 This skill is part of an open motion-graphics collection from iart.ai — the AI motion agent that turns data, scripts, and designs into editable motion graphics (Remotion → MP4). If you'd rather not hand-build this, iart.ai can generate branded lower-thirds from a list of names/titles, one-click — change the text/data and re-export. → [iart.ai](https://iart.ai/?utm_source=github&utm_medium=reference&utm_campaign=tiktok-video-skills&utm_content=ref_footer&utm_term=lower-thirds)
@@ -0,0 +1,24 @@
 # Short-Form Video
 Engineer a 9:16 video that survives the swipe. Short-form is a retention machine, not a small launch film: a hook that earns the first second, pattern interrupts that reset attention every few seconds, and often a loop that buys watch-time past 100%. The craft is timing, not polish. For creators making Reels, TikToks, and YouTube Shorts (7–60s, vertical).
 ## When it activates
 - "Make a Reels/TikTok/YouTube Shorts video" or "build a short-form video template."
 - "Write a hook for a short" or "fix the first 3 seconds."
 - "Edit for retention," "add pattern interrupts," or "pace cuts for a vertical video."
 - "Make a video loop" or "set up 9:16 safe areas."
 ## Example prompts
 - "Build a reusable 9:16 short-form template — one design, many topics."
 - "Fix the drop-off in this Reel: tighten pacing and add pattern interrupts."
 - "Write three hook options for a 30-second educational short."
 ## What's inside
 - `SKILL.md` — the retention arc, hook grammar, and pacing rules.
 - `references/retention-pacing.md` — deeper guidance on retention editing and pacing.
 ---
 Part of **[Short-Form Video Skills](../../)** · Built by **[iart.ai](https://iart.ai/?utm_source=github&utm_medium=readme&utm_campaign=tiktok-video-skills&utm_content=skill_footer&utm_term=short-form-video)** — the AI motion agent for editable, on-brand motion graphics.
@@ -0,0 +1,155 @@
 ---
 name: short-form-video
 description: This skill should be used when the user asks to "make a Reels/TikTok/YouTube Shorts video", "build a short-form video template", "write a hook for a short", "edit for retention", "add pattern interrupts", "make a video loop", "fix the first 3 seconds", "pace cuts for a vertical video", or "set up 9:16 safe areas". Covers the hook→retention→loop grammar of vertical short-form (distinct from a launch hype film).
 version: 0.1.0
 ---
 # Short-Form Video
 Engineer a 9:16 video that survives the swipe. Short-form is not a small launch film — it is a retention machine: a hook that earns the first second, pattern interrupts that reset attention every few seconds, and often a loop that buys watch-time past 100%. The craft is timing, not polish.
 ## When to use
 - Reels / TikTok / YouTube Shorts (7–60s, vertical 9:16).
 - Retention editing: fixing drop-off, adding pattern interrupts, tightening pacing.
 - Hooks, seamless loops, repeatable short-form templates (one design, many topics).
 ## Story structure (the retention contract)
 Short-form storytelling is a contract with the viewer's thumb: every second must re-earn the next one. The narrative is shaped *backwards from the retention curve*, not forwards from an intro. Lock these before touching the timeline.
 - **One idea per video.** A short carries exactly one payoff. A second idea splits attention and the curve sags in the middle — make it a second video instead. If you can't name the single takeaway in a sentence, you don't have a short yet.
 - **Open a loop in the first ~3s, close it last.** The hook poses a question or gap (the open loop); the payoff answers it. The viewer stays because the loop is open — so never answer it early, and never bury the payoff under setup.
 - **No dead air.** Every beat either advances the idea or resets attention. Cut anything that does neither. Silence, slow ramps, throat-clearing intros ("hey guys, in this video…") are where viewers swipe.
 - **Why the curve, not the cut, is the unit of work.** The algorithm distributes whatever holds the per-second retention curve flat; a "good" edit that flattens the curve loses to an ugly one that keeps it up. You are editing the *curve*, and the hook gates everything after it — fix it first.
 The narrative spine (the `Hook → Setup → Body → Payoff/loop` arc is budgeted in the table below):
 | Move | Story job | Failure if missed |
 |---|---|---|
 | Hook | Open the loop; promise the payoff | Swipe in first 3s |
 | Tension hold | Keep the gap open through the body | Flat middle, mid-drop |
 | Payoff | Close the loop — the one idea, delivered | "Wasted my time," no share |
 | Loop / CTA | Feed back to frame 0, or one clear ask | No re-watch, no action |
 (`The retention arc` table below assigns seconds to each move; this section is the narrative logic and ordering behind it. `Hook grammar` lists the hook archetypes.)
 ## The one metric that drives everything
 **Retention, not production value.** The algorithm distributes whatever holds viewers; ~87% decide to stay or swipe inside 3 seconds, and the threshold for distribution sits near **70%+ average view-through** (Shorts ~73%, TikTok ~78%, Reels ~65%). Every decision below trades against that curve. A flawless shot that bores at 0:04 loses to an ugly one that holds.
 ## The retention arc
 | Beat | Job | Budget (of a 20s short) |
 |---|---|---|
 | Hook (0–1s) | One frame + one line that creates an open loop | 0–1s |
 | Setup | Pay off *why watch* — promise, stakes, or the gap | 1–4s |
 | Body | Deliver value in beats; one idea per beat | 4–17s |
 | Payoff / loop | Close the loop — or feed it back to frame 0 | 17–20s |
 Scale the *body*, never the hook. A 60s short has a longer body and more beats — the same 1-second hook.
 ## Hook grammar (first ~1s)
 The hook is a sentence + a visual that opens a curiosity gap the brain needs closed. Pick one pattern and commit:
 | Hook type | Shape | Best for |
 |---|---|---|
 | Open loop | "The reason your X keeps Y…" (answer delayed) | most content |
 | Direct promise | "3 ways to ___ in 30 seconds" | educational / listicle |
 | Pattern interrupt | snap-zoom / whip-pan / visual mismatch in frame 1 | entertainment |
 | Negation | "Stop doing ___" / "You're ___ wrong" | strong opinions |
 Two rules: the hook line is **on-screen as text by frame 1** (85% watch muted), and the most striking *visual* is also the first frame — never a slow ramp-in. Hold a strong opening frame; do not fade up from black.
 ## Pattern interrupts & cut rhythm
 A pattern interrupt is any change that resets attention: a hard cut, zoom punch, b-roll insert, sound effect, caption pop, or angle change. In short-form, density is high — a *visual change every ~2–4 seconds*; videos with an interrupt roughly every 4s hold ~58% vs ~41% for a static talking head. The killer is a flat middle: TikTok throttles distribution when the watch-through curve flattens, so never stitch the body from low-energy takes.
 ```js
 // Drive every interrupt off the FRAME, not wall-clock — renders deterministically.
 import { useCurrentFrame } from "remotion";
 const fps = 30;
 const cuts = [0, 1.2, 3.0, 5.4, 8.0, 11.2, 14.0]; // seconds — uneven on purpose
 const frame = useCurrentFrame();
 const shot = cuts.findIndex((t, i) => frame < (cuts[i + 1] ?? Infinity) * fps);
 ```
 Vary the interval — a metronome reads as boredom; uneven cuts read as momentum. A punch-in zoom is the cheapest interrupt that needs no new footage:
 ```jsx
 import { useCurrentFrame, interpolate, spring, useVideoConfig } from "remotion";
 const PunchIn = ({ at, children }) => {
  const frame = useCurrentFrame(); const { fps } = useVideoConfig();
  const s = spring({ frame: frame - at * fps, fps, config: { damping: 12, stiffness: 200 } });
  const scale = interpolate(s, [0, 1], [1, 1.12]); // snap to 112% on the beat
  return <div style={{ transform: `scale(${scale})`, transformOrigin: "50% 45%" }}>{children}</div>;
 };
 ```
 ## Captions
 Most viewers watch muted, so on-screen captions are not optional — they carry the content and double as a pattern interrupt when each phrase pops in. Keep 4–7 words per line, high contrast, inside the safe area. **Do not re-implement caption animation here** — use the `caption-animation` skill for word-by-word timing, karaoke highlight, and styling; this skill only places captions on the retention timeline and inside the 9:16 safe zone.
 ## Loops & re-watch
 A seamless loop counts each re-watch as fresh watch-time — a clean 8s loop watched 3× is 300% view-through, the strongest possible signal. Two techniques: match the **last frame to the first** (same composition, position, color) so the cut is invisible, and write a **sentence loop** — phrase the hook so the payoff feeds back into frame 0 ("…and that's why I never — " → loops to the start). Best length for re-watch is ~7–15s.
 ## 9:16 safe areas
 Compose inside the universal safe zone so platform UI never covers text or faces.
 | Zone | Pixels (1080×1920) | Avoid |
 |---|---|---|
 | Universal safe (all platforms) | center **900×1400** | anything critical outside it |
 | Top | keep clear ~120px | profile / sound UI |
 | Bottom | keep clear ~320px | captions, CTA, hashtags, audio bar |
 | Right | keep clear ~120px | like / comment / share rail |
 Put the hook text and key subject in the center 900×1400 box. Reserve the bottom ~320px even if it looks empty in the editor — that is where the platform paints its own captions and buttons.
 ## Output checklist
 - Hook line is on-screen text by frame 1; strongest visual is the first frame (no fade-up).
 - One open loop / promise set in the first ~4s.
 - A visual pattern interrupt every ~2–4s; intervals uneven; no flat middle.
 - Captions present (via `caption-animation`), 4–7 words, inside safe area.
 - Loop closed — matched first/last frame or a sentence that feeds frame 0.
 - Composed inside the 900×1400 center box; bottom 320px / top 120px / right 120px kept clear.
 - Every animated value derived from `useCurrentFrame()` — no CSS/library timers.
 ## Deliver & verify (rendered stills → MP4)
 > **Packaged helper** (`scripts/`): tile your stills with `scripts/contact-sheet.sh sheet.png f-hook.png f-mid.png f-end.png`, then assert the encode with `scripts/probe-mp4.sh out.mp4 [WxH] [fps]`. See `scripts/README.md`.
 The short ships as a Remotion composition (`<Composition>` + zod `schema` + `defaultProps`) — every cut, punch-in, and interrupt driven by `useCurrentFrame()`, never `Date.now()` / `Math.random()` / timers. Deliverable = `out/*.mp4` + the project (re-render per topic). 9:16 vertical (1080×1920) is the default.
 **Verify loop — render stills → inspect → encode.** Three frames test the three things that make or break retention: the hook, the pacing, and the loop seam.
 ```bash
 # Stills at hook / mid-body / last frame — WITH SHIPPED PROPS (the real topic, not defaults)
 npx remotion still Short out/f-hook.png --frame=10  --props='{"topic":"...","hook":"..."}'   # ~first 3s reads instantly
 npx remotion still Short out/f-mid.png  --frame=N   --props='{"topic":"...","hook":"..."}'
 npx remotion still Short out/f-end.png  --frame=L   --props='{"topic":"...","hook":"..."}'   # L = durationInFrames-1
 # Inspect each PNG:
 #  - HOOK frame (~frame 0-ish / first 3s): hook line is on-screen text and reads instantly; strongest visual already up (no fade-up)
 #  - LOOP seam: compare f-hook(frame 0) vs f-end(last frame) — same composition/position/color for an invisible loop cut
 #  - 9:16 safe area: hook + key subject inside the center 900x1400 box; clear of top ~12%, bottom ~20-35% (captions/CTA/audio), right action rail
 npx remotion render Short out/short.mp4 --props='{"topic":"...","hook":"..."}'   # encode once stills verify
 npx remotion render Short out/demo.gif --codec=gif                                # README proof clip
 ```
 **Per topic / batch**: verify ONE topic via stills *before* rendering all of them. Use `npx remotion compositions` for `durationInFrames`/`fps` to pick the mid + last frames.
 **Before you finish:**
 1. Stills render cleanly at the hook, mid, and last frame — no errors.
 2. The hook frame reads instantly (on-screen text + strongest visual up front, no fade-up); first vs last frame match for a clean loop seam.
 3. Hook + subject + captions sit inside the 9:16 center 900×1400 safe box at every checked frame.
 4. Frame-driven only — no `Date.now()` / `Math.random()` / timers; cuts uneven, no flat middle.
 5. A real topic's shipped props (not `defaultProps`) render correctly; MP4 encoded, GIF optional.
 ## Reference files
 - `references/retention-pacing.md` — a complete runnable Remotion `<Short>` composition: a frame-driven shot scheduler with uneven cuts, the PunchIn pattern interrupt, an on-screen hook, a 9:16 safe-area overlay, and a seamless first/last-frame loop. Plus a hook-pattern library, a retention-curve debugging method, per-platform safe-zone maps, and the template×topic batch-render pattern.
@@ -0,0 +1,209 @@
 # Retention Pacing — Short-Form Video Reference
 Deep reference for the `short-form-video` skill: a full runnable Remotion short, a hook library, a retention-debugging method, per-platform safe zones, and batch output. All timing is frame-driven so renders are deterministic.
 ## 1. A complete `<Short>` composition
 One self-contained vertical short: frame-driven shot scheduler with uneven cuts, a punch-in pattern interrupt, an on-screen hook, a 9:16 safe-area overlay (dev only), and a seamless loop. Topic content is a prop, so the same file renders many shorts.
 ```tsx
 // Short.tsx — 1080×1920, 30fps. Register at 600 frames (20s) for a clean loop.
 import {
  AbsoluteFill, useCurrentFrame, useVideoConfig,
  interpolate, spring, Sequence, Img,
 } from "remotion";
 type Beat = { at: number; text: string; src?: string };  // at = seconds
 export type ShortProps = {
  hook: string;                 // on-screen by frame 1
  beats: Beat[];                // body, one idea each
  loopText: string;             // sentence that feeds back to frame 0
 };
 // --- frame-driven shot scheduler: uneven cuts read as momentum ---
 const useShot = (cuts: number[]) => {
  const { fps } = useVideoConfig();
  const frame = useCurrentFrame();
  let i = 0;
  for (let k = 0; k < cuts.length; k++) if (frame >= cuts[k] * fps) i = k;
  const startF = cuts[i] * fps;
  const endF = (cuts[i + 1] ?? cuts[i] + 2) * fps;
  const local = (frame - startF) / (endF - startF); // 0→1 within shot
  return { index: i, local, startF };
 };
 // --- punch-in: the cheapest pattern interrupt, snaps on the cut ---
 const PunchIn: React.FC<{ startF: number; to?: number; children: React.ReactNode }> = ({
  startF, to = 1.1, children,
 }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const s = spring({ frame: frame - startF, fps, config: { damping: 13, stiffness: 220 } });
  const scale = interpolate(s, [0, 1], [1, to]);
  return <AbsoluteFill style={{ transform: `scale(${scale})`, transformOrigin: "50% 45%" }}>{children}</AbsoluteFill>;
 };
 // --- hook: text present from frame 0, micro-overshoot, no fade-up ---
 const Hook: React.FC<{ text: string }> = ({ text }) => {
  const frame = useCurrentFrame();
  const { fps } = useVideoConfig();
  const pop = spring({ frame, fps, config: { damping: 9, stiffness: 260 } });
  const scale = interpolate(pop, [0, 1], [0.9, 1]);
  return (
    <div style={{
      position: "absolute", top: 360, left: 90, right: 90, // inside 900-wide safe box
      transform: `scale(${scale})`, transformOrigin: "0 0",
      fontFamily: "Inter, sans-serif", fontWeight: 800, fontSize: 76, lineHeight: 1.05,
      color: "#fff", textShadow: "0 4px 24px rgba(0,0,0,.55)",
    }}>{text}</div>
  );
 };
 export const Short: React.FC<ShortProps> = ({ hook, beats, loopText }) => {
  const { fps, durationInFrames } = useVideoConfig();
  const frame = useCurrentFrame();
  const cuts = [0, ...beats.map((b) => b.at)];     // hook shot + one per beat
  const { index, startF } = useShot(cuts);
  const current = index === 0 ? null : beats[index - 1];
  // seamless loop: match the LAST 0.5s back toward the opening frame
  const tailF = durationInFrames - frame;
  const loopFade = interpolate(tailF, [0, fps * 0.5], [0, 1], { extrapolateLeft: "clamp", extrapolateRight: "clamp" });
  return (
    <AbsoluteFill style={{ backgroundColor: "#0b0b0f" }}>
      <PunchIn startF={startF}>
        {current?.src && <Img src={current.src} style={{ width: "100%", height: "100%", objectFit: "cover" }} />}
      </PunchIn>
      {index === 0 && <Hook text={hook} />}
      {/* body caption — placement only; styling/word-timing belongs to caption-animation */}
      {current && (
        <div style={{
          position: "absolute", left: 90, right: 90, bottom: 380, // above the 320px bottom UI band
          fontFamily: "Inter, sans-serif", fontWeight: 700, fontSize: 60, color: "#fff",
          textAlign: "center", textShadow: "0 3px 18px rgba(0,0,0,.6)",
        }}>{current.text}</div>
      )}
      {/* loop sentence rises as the clip ends, easing the eye back to frame 0 */}
      <div style={{
        position: "absolute", left: 90, right: 90, bottom: 380, opacity: 1 - loopFade,
        fontFamily: "Inter, sans-serif", fontWeight: 800, fontSize: 64, color: "#fff", textAlign: "center",
      }}>{loopText}</div>
      <SafeZone />{/* remove for final render */}
    </AbsoluteFill>
  );
 };
 ```
 Register it with a duration that *is* the loop length:
 ```ts
 // Root.tsx
 import { Composition } from "remotion";
 import { Short } from "./Short";
 export const Root = () => (
  <Composition
    id="Short" component={Short}
    durationInFrames={600} fps={30} width={1080} height={1920}
    defaultProps={{
      hook: "You're editing Shorts wrong —",
      beats: [
        { at: 1.2, text: "Cut every 2–4 seconds", src: "b1.jpg" },
        { at: 4.0, text: "Never on a fixed grid", src: "b2.jpg" },
        { at: 7.5, text: "Kill the flat middle", src: "b3.jpg" },
        { at: 11.0, text: "Match last frame to first", src: "b4.jpg" },
      ],
      loopText: "…and that's why mine loop forever",
    }}
  />
 );
 ```
 ## 2. The 9:16 safe-area overlay (dev-only)
 Render this on top while editing; delete it before the final export.
 ```tsx
 import { AbsoluteFill } from "remotion";
 export const SafeZone: React.FC = () => (
  <AbsoluteFill style={{ pointerEvents: "none" }}>
    {/* universal safe box: center 900×1400 in 1080×1920 */}
    <div style={{ position: "absolute", left: 90, top: 260, width: 900, height: 1400, outline: "2px dashed #39d", opacity: .6 }} />
    {/* platform UI bands to keep clear */}
    <div style={{ position: "absolute", top: 0, left: 0, right: 0, height: 120, background: "rgba(255,0,0,.12)" }} />
    <div style={{ position: "absolute", bottom: 0, left: 0, right: 0, height: 320, background: "rgba(255,0,0,.12)" }} />
    <div style={{ position: "absolute", bottom: 320, top: 120, right: 0, width: 120, background: "rgba(255,128,0,.10)" }} />
  </AbsoluteFill>
 );
 ```
 ## 3. Hook pattern library
 The hook is a sentence that opens a gap the brain must close, plus the most striking frame as frame 0. Copyable shapes:
 | Pattern | Template | Note |
 |---|---|---|
 | Open loop | "The real reason your ___ keeps ___ …" | answer withheld until payoff |
 | Direct promise | "___ in 30 seconds, no ___ needed" | name the payoff + the timebox |
 | Negation | "Stop ___. You're doing it backwards." | strong-opinion content |
 | Pattern interrupt | snap-zoom / whip / hard visual mismatch | entertainment, no text needed |
 | Stakes | "This ___ cost me $___ — don't repeat it" | story / case-study |
 | Listicle | "3 ___ that ___ (the 3rd one ___ )" | tees up a forward reference |
 Rules that matter more than the wording: (1) the hook text is on-screen by frame 1 — most viewers are muted; (2) frame 0 is the best frame, never a fade-up from black; (3) one gap only — stacking two hooks closes neither.
 ## 4. Retention-curve debugging
 Treat the per-second retention graph (TikTok Analytics, YT Studio "Audience retention", Reels) as a profiler.
 | Symptom on the curve | Likely cause | Fix |
 |---|---|---|
 | Cliff at 0:00–0:02 | weak hook / slow first frame | new hook line; cut the ramp-in; lead with the best frame |
 | Steady gentle decline | normal — leave it | — |
 | Flat-then-drop in the middle | low-energy body, cuts too sparse | add interrupts; tighten cut spacing to 2–4s |
 | Bump back up near the end | viewers are looping | lean in — tighten the loop, shorten total length |
 | Spike at one timestamp | a re-watched moment | front-load that beat or make it the hook |
 Target ≥70% average view-through. Iterate the hook first — it moves the curve more than any other edit because it gates everything after it.
 ## 5. Per-platform safe zones
 All on a 1080×1920 canvas. The universal box (center 900×1400) is the intersection; design inside it and one master fits every platform.
 | Platform | Top clear | Bottom clear | Right clear | Notes |
 |---|---|---|---|---|
 | Universal (use this) | ~120px | ~320px | ~120px | center 900×1400 holds on all |
 | TikTok | ~108px | ~320px | ~120px | caption + button rail at bottom-right |
 | Instagram Reels | ~120px | ~310px | ~84px | audio bar + caption bottom |
 | YouTube Shorts | ~120px | ~300px | ~60px | channel + subscribe bottom band |
 | TikTok Ads | ~108px | ~370px | ~120px | extra room for the CTA button |
 When unsure, design to the *largest* margin (TikTok Ads bottom 370px) and nothing ever clips.
 ## 6. Template × topic — batch output
 The payoff of code-driven shorts: lock the design once, swap only the props, render N videos. Make topic content a prop (already done above), keep one theme object, and loop over JSON files.
 ```jsx
 // theme.ts — one source of truth so 50 shorts stay on-brand
 export const theme = { font: "Inter", hookSize: 76, bodySize: 60, bg: "#0b0b0f", fg: "#fff", accent: "#39d" };
 ```
 ```bash
 # render the same Short template for every topic file in /topics
 for f in topics/*.json; do
  name=$(basename "$f" .json)
  npx remotion render Short "out/$name.mp4" --props="$f"
 done
 ```
 Each `topics/*.json` is one `ShortProps` object (`hook`, `beats`, `loopText`). Keep the hook line, cut points, and loop sentence per-topic; everything else stays fixed so the series reads as one brand.
 ---
 ## Built by the team behind iart.ai
 This skill is part of an open motion-graphics collection from iart.ai — the AI motion agent that turns data, scripts, and designs into editable motion graphics (Remotion → MP4). If you'd rather not hand-build this, iart.ai can batch-produce short-form videos from one template × data — change the text/data and re-export. → [iart.ai](https://iart.ai/?utm_source=github&utm_medium=reference&utm_campaign=tiktok-video-skills&utm_content=ref_footer&utm_term=short-form-video)
@@ -0,0 +1 @@
 ../../.agents/skills/caption-animation
@@ -0,0 +1 @@
 ../../.agents/skills/countdown-video
@@ -0,0 +1 @@
 ../../.agents/skills/lower-thirds
@@ -0,0 +1 @@
 ../../.agents/skills/short-form-video
@@ -1,143 +0,0 @@
 ---
 name: website-builder-setup
 description: "Install the full AI website builder stack — UI/UX Pro Max, Framer Motion animations, and 21st.dev components. One skill, three tools, zero coding experience needed."
 ---
 # Website Builder Setup
 This skill walks you through installing everything you need to build professional, animated websites with Claude Code. No coding experience required.
 ## What Gets Installed
 | Tool | What it does |
 |------|-------------|
 | **UI/UX Pro Max** | Gives Claude access to 50+ design styles, 161 color palettes, 57 font pairings. Your sites look designed, not generated. |
 | **Framer Motion** | Adds smooth animations — page transitions, hover effects, scroll reveals. Makes sites feel alive. |
 | **21st.dev Magic** | A library of 100+ polished React components Claude can pull from. Production-quality building blocks. |
 ## Workflow
 When this skill is triggered, walk the user through each step one at a time. Be encouraging and clear — assume they have zero coding experience. If any step fails, don't stop. Acknowledge it, give them the manual command, and keep moving.
 ---
 ### Step 1: Check Prerequisites
 > Before we start, let me make sure you have what we need.
 Run this silently:
 ```bash
 node --version 2>&1 && npm --version 2>&1
 ```
 - If Node.js is installed → say "You're good — Node.js is installed. Let's go."
 - If NOT installed → say:
 > You need Node.js first. Go to https://nodejs.org and download the LTS version. Install it, restart your terminal, then come back and run `/website-builder-setup` again. Takes 2 minutes.
 Stop here if Node is missing.
 ---
 ### Step 2: Install UI/UX Pro Max
 > **Step 1 of 3: UI/UX Pro Max**
 >
 > This gives me a massive design library — 50+ styles, 161 color palettes, 57 font pairings. When you ask me to build a website, I'm pulling from a real design system instead of guessing. This is why the output won't look like generic AI slop.
 >
 > Installing now...
 Run:
 ```bash
 npm install -g uipro-cli 2>&1
 ```
 Then:
 ```bash
 uipro init --ai claude 2>&1
 ```
 - On success → "UI/UX Pro Max is installed. Your design stack is ready."
 - On failure → "Hit a snag. You can try manually later: `npm install -g uipro-cli && uipro init --ai claude`. Let's keep going."
 ---
 ### Step 3: Install Framer Motion
 > **Step 2 of 3: Framer Motion**
 >
 > This teaches me how to add real animations to your websites — smooth page transitions, hover effects, scroll-triggered reveals. The stuff that makes a $500 site look like a $10,000 site.
 >
 > Installing now...
 Run:
 ```bash
 npm install framer-motion 2>&1
 ```
 - On success → "Framer Motion is installed. Your sites will have real animations now."
 - On failure → "Hit a snag. You can try manually later: `npm install framer-motion`. Moving on."
 ---
 ### Step 4: Set Up 21st.dev Magic
 > **Step 3 of 3: 21st.dev Components**
 >
 > This connects me to a library of 100+ beautifully designed React components. Instead of building everything from scratch, I pull from production-quality building blocks — buttons, navbars, hero sections, cards, footers — all pre-designed and ready to use.
 >
 > This one needs a free API key. Here's how to get it:
 >
 > 1. Go to **https://21st.dev/magic/console**
 > 2. Sign up or log in (it's free)
 > 3. Copy your API key
 > 4. Paste it here when I ask for it
 Wait for the user to provide their API key.
 Once they provide it, add the MCP server to their Claude Code config:
 Read `~/.claude.json`, find the `mcpServers` object, and add:
 ```json
 "21st-dev-magic": {
  "command": "npx",
  "args": ["-y", "@21st-dev/magic@latest"],
  "env": {
    "API_KEY": "THEIR_KEY_HERE"
  }
 }
 ```
 After writing the config:
 > 21st.dev Magic is connected. You'll need to restart Claude Code for this one to kick in — just close and reopen your terminal after we're done.
 ---
 ### Step 5: Done
 > **You're all set.** Here's what you just installed:
 >
 > - **UI/UX Pro Max** — 50+ styles, 161 palettes, 57 font pairings
 > - **Framer Motion** — smooth, professional animations
 > - **21st.dev Magic** — 100+ production-ready components
 >
 > **To build your first website, just tell me:**
 > - What your business does
 > - Who it's for
 > - What vibe you want (dark, minimal, bold, playful, etc.)
 >
 > I'll handle the rest. Try something like:
 >
 > *"Build me a landing page for my consulting business targeting small business owners. Dark theme, modern, with animations."*
 >
 > **Important:** Restart Claude Code first so 21st.dev loads in. Then let's build something.
 ## Rules
 - Walk through each step ONE AT A TIME
 - Never dump all instructions at once
 - If any install fails, don't stop — acknowledge, give manual command, keep moving
 - Be encouraging and casual throughout
 - Assume zero coding experience
 - After everything is installed, prompt them to build their first site
@@ -1,60 +0,0 @@
 # LookAtU: Product Plan (PRD)
 ## What is it? (the 4th-grade version)
 LookAtU is a helper for parents. The parent has an app. The child has an app. The parent can see where the child is, see what the child does on the phone, choose which apps the child can use, and check calls and messages. If the child is in danger, the child taps a big **panic button** and the parent gets an alert right away.
 ## Who is it for?
 - **Parents** of kids who have their own phone.
 - **Kids**, who need a simple way to ask for help.
 ## Core features
 1. **Live location**: the parent sees where the child is, any time.
 2. **Activity monitor**: which apps are used and for how long.
 3. **App control**: the parent can allow, block, or limit apps, and approve new installs.
 4. **Calls and messages**: the parent can check call history and messages.
 5. **Panic button**: the child taps once. The parent gets an alert with the child's location.
 ## Trust and safety rules (built in from day one)
 - The child **knows** the app is on their phone. No hidden spying. This is the honest way to do it, and app stores require it.
 - The parent signs in with a real account and a strong password.
 - Data is private and encrypted. Only the parent sees it.
 - Rules about monitoring messages differ by country and by the child's age. We must check the law for each country before launch.
 ## Phased roadmap
 ### Phase 1: Quick win (TODAY)
 A good-looking website (one page) that explains LookAtU and collects sign-ups.
 - Hero, 5 feature cards, "how it works", trust section, FAQ
 - Waitlist form that checks the email is real-looking
 - Works on phones and computers
 - **Done when:** page loads with no errors and the form and buttons work.
 ### Phase 2: Make it real
 - Connect the waitlist form to a real service so emails are saved.
 - Add animations (Framer Motion) and better pictures.
 - Add privacy and terms pages.
 ### Phase 3: Parent accounts
 - Sign up and log in.
 - A simple parent dashboard (website).
 - Link a parent to a child.
 ### Phase 4: Phone apps
 - Child app and parent app (Android first, then iPhone).
 - Live location and the panic button with alerts (push notifications and SMS).
 ### Phase 5: Monitoring and control
 - App usage, app blocking and install approval.
 - Call and message history (after legal review).
 ## How we test at every phase
 1. Page loads with **no errors**.
 2. Buttons and forms **work**.
 3. Real services (database, email, maps, alerts) **work**.
 4. **Security check**: passwords, private data, no secrets in code.
 ## Open questions for the owner
 - Which countries first?
 - Free or paid? (price)
 - Android first, or iPhone first?
 - Final name and logo?
@@ -1,229 +0,0 @@
 <!doctype html>
 <html lang="en">
 <head>
 <meta charset="utf-8">
 <meta name="viewport" content="width=device-width, initial-scale=1">
 <title>LookAtU – Know your child is safe</title>
 <meta name="description" content="LookAtU helps parents see where their child is, guide their phone use, and gives kids a panic button for emergencies.">
 <style>
 :root{
  --bg:#0b1220; --bg2:#111a2e; --card:#16213a; --text:#eaf0ff; --muted:#a3b1d1;
  --brand:#4f8cff; --brand2:#7c5cff; --danger:#ff4d5e; --ok:#31d0a0; --line:#243253;
 }
 *{box-sizing:border-box}
 html{scroll-behavior:smooth}
 body{margin:0;font-family:system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;background:var(--bg);color:var(--text);line-height:1.6}
 a{color:inherit}
 .wrap{max-width:1080px;margin:0 auto;padding:0 20px}
 header{position:sticky;top:0;z-index:10;background:rgba(11,18,32,.85);backdrop-filter:blur(8px);border-bottom:1px solid var(--line)}
 .nav{display:flex;align-items:center;justify-content:space-between;height:64px}
 .logo{font-weight:800;font-size:1.3rem;text-decoration:none}
 .logo span{color:var(--brand)}
 .nav a.link{margin-left:22px;text-decoration:none;color:var(--muted);font-size:.95rem}
 .nav a.link:hover{color:var(--text)}
 .btn{display:inline-block;border:0;cursor:pointer;font:inherit;font-weight:700;padding:12px 22px;border-radius:12px;color:#fff;text-decoration:none;background:linear-gradient(135deg,var(--brand),var(--brand2));transition:transform .15s}
 .btn:hover{transform:translateY(-2px)}
 .btn.ghost{background:transparent;border:1px solid var(--line);color:var(--text)}
 .hero{padding:80px 0 60px;text-align:center;background:radial-gradient(900px 400px at 50% -10%,rgba(79,140,255,.25),transparent)}
 .hero h1{font-size:clamp(2.2rem,6vw,3.8rem);line-height:1.1;margin:0 0 18px}
 .hero h1 em{font-style:normal;background:linear-gradient(135deg,var(--brand),var(--brand2));-webkit-background-clip:text;background-clip:text;color:transparent}
 .hero p{max-width:620px;margin:0 auto 28px;color:var(--muted);font-size:1.15rem}
 .cta{display:flex;gap:12px;justify-content:center;flex-wrap:wrap}
 .phone{margin:48px auto 0;width:240px;border:2px solid var(--line);border-radius:34px;padding:18px;background:var(--bg2);box-shadow:0 20px 60px rgba(0,0,0,.4)}
 .map{height:130px;border-radius:16px;background:linear-gradient(135deg,#1c2b4d,#22365f);position:relative;overflow:hidden}
 .pin{position:absolute;left:50%;top:50%;width:16px;height:16px;margin:-8px;border-radius:50%;background:var(--ok)}
 .pin::after{content:"";position:absolute;inset:-10px;border-radius:50%;border:2px solid var(--ok);animation:pulse 2s infinite}
@keyframes pulse{from{transform:scale(.6);opacity:1}to{transform:scale(1.8);opacity:0}}
 .phone p{margin:12px 0 4px;font-size:.9rem;color:var(--muted)}
 .panic{margin-top:6px;width:100%;padding:12px;border:0;border-radius:14px;background:var(--danger);color:#fff;font-weight:800;font-size:1rem;cursor:pointer}
 section{padding:70px 0}
 section.alt{background:var(--bg2)}
 h2{font-size:clamp(1.6rem,4vw,2.4rem);margin:0 0 10px;text-align:center}
 .sub{text-align:center;color:var(--muted);max-width:620px;margin:0 auto 40px}
 .grid{display:grid;gap:18px;grid-template-columns:repeat(auto-fit,minmax(240px,1fr))}
 .card{background:var(--card);border:1px solid var(--line);border-radius:18px;padding:24px}
 .card .ic{font-size:2rem}
 .card h3{margin:10px 0 6px}
 .card p{margin:0;color:var(--muted)}
 .card.sos{border-color:var(--danger)}
 .steps{counter-reset:s}
 .steps .card{position:relative;padding-top:50px}
 .steps .card::before{counter-increment:s;content:counter(s);position:absolute;top:14px;left:20px;width:28px;height:28px;border-radius:50%;background:var(--brand);display:grid;place-items:center;font-weight:800}
 .trust li{margin:10px 0;color:var(--muted)}
 .trust b{color:var(--text)}
 details{background:var(--card);border:1px solid var(--line);border-radius:14px;padding:16px 20px;margin:10px auto;max-width:720px}
 summary{cursor:pointer;font-weight:700}
 details p{color:var(--muted);margin:10px 0 0}
 form{max-width:480px;margin:0 auto;display:flex;gap:10px;flex-wrap:wrap}
 input[type=email]{flex:1 1 220px;padding:13px 14px;border-radius:12px;border:1px solid var(--line);background:var(--bg);color:var(--text);font:inherit}
 input[type=email]:focus-visible,.btn:focus-visible,summary:focus-visible,button:focus-visible{outline:3px solid var(--brand);outline-offset:2px}
 #msg{text-align:center;margin-top:14px;min-height:1.5em}
 #msg.ok{color:var(--ok)} #msg.err{color:var(--danger)}
 .note{text-align:center;color:var(--muted);font-size:.85rem;margin-top:8px}
 .sr{position:absolute;left:-9999px}
 .trap{position:absolute;left:-9999px;height:0;overflow:hidden}
 select{padding:13px 14px;border-radius:12px;border:1px solid var(--line);background:var(--bg);color:var(--text);font:inherit}
 .consent{flex:1 1 100%;font-size:.9rem;color:var(--muted)}
 .consent input{margin-right:8px}
 .consent a{color:var(--brand)}
 footer a{margin:0 8px}
 footer{padding:30px 0;border-top:1px solid var(--line);color:var(--muted);font-size:.9rem;text-align:center}
@media (prefers-reduced-motion:reduce){.pin::after{animation:none}html{scroll-behavior:auto}}
@media (max-width:640px){.nav a.link{display:none}}
 </style>
 </head>
 <body>
 <header>
  <div class="wrap nav">
    <a class="logo" href="#top">Look<span>At</span>U</a>
    <nav>
      <a class="link" href="#features">Features</a>
      <a class="link" href="#how">How it works</a>
      <a class="link" href="#trust">Trust</a>
      <a class="link" href="#faq">FAQ</a>
      <a class="btn" style="margin-left:22px;padding:9px 16px" href="#join">Join waitlist</a>
    </nav>
  </div>
 </header>
 <main id="top">
  <div class="hero">
    <div class="wrap">
      <h1>Know your child is <em>safe</em>,<br>anytime you want.</h1>
      <p>See where they are, guide how they use their phone, and give them a big red button to call for help when it matters most.</p>
      <div class="cta">
        <a class="btn" href="#join">Join the waitlist</a>
        <a class="btn ghost" href="#features">See what it does</a>
      </div>
      <div class="phone" aria-hidden="true">
        <div class="map"><div class="pin"></div></div>
        <p>Alex is at school · just now</p>
        <button class="panic" tabindex="-1">SOS</button>
      </div>
    </div>
  </div>
  <section id="features">
    <div class="wrap">
      <h2>Everything a parent needs</h2>
      <p class="sub">Five simple tools, in one app.</p>
      <div class="grid">
        <div class="card"><div class="ic">📍</div><h3>Live location</h3><p>Open the app and see where your child is right now.</p></div>
        <div class="card"><div class="ic">📊</div><h3>Activity monitor</h3><p>See which apps they use and for how long, every day.</p></div>
        <div class="card"><div class="ic">🔒</div><h3>App control</h3><p>Allow, block or limit apps. Approve new installs before they happen.</p></div>
        <div class="card"><div class="ic">💬</div><h3>Calls &amp; messages</h3><p>Check call history and messages so you can spot trouble early.</p></div>
        <div class="card sos"><div class="ic">🚨</div><h3>Panic button</h3><p>One tap and you get an alert with their location, right away.</p></div>
      </div>
    </div>
  </section>
  <section id="how" class="alt">
    <div class="wrap">
      <h2>How it works</h2>
      <p class="sub">Set up takes a few minutes.</p>
      <div class="grid steps">
        <div class="card"><h3>Install on both phones</h3><p>You get the parent app. Your child gets the child app.</p></div>
        <div class="card"><h3>Link them together</h3><p>Scan a code on your child's phone to connect the two.</p></div>
        <div class="card"><h3>Choose your rules</h3><p>Pick which apps are allowed and what you want to see.</p></div>
      </div>
    </div>
  </section>
  <section id="trust">
    <div class="wrap" style="max-width:720px">
      <h2>Built on trust, not secrets</h2>
      <p class="sub">Safety works best when families talk about it.</p>
      <ul class="trust">
        <li><b>Your child knows.</b> The app is always visible on their phone. LookAtU is never hidden.</li>
        <li><b>Private by design.</b> Data is encrypted and only the parent account can see it.</li>
        <li><b>You stay in charge.</b> Choose what to watch and turn features on or off at any time.</li>
        <li><b>Follows the law.</b> Rules about monitoring differ by country and a child's age. We check them before we launch anywhere.</li>
      </ul>
    </div>
  </section>
  <section id="faq" class="alt">
    <div class="wrap">
      <h2>Questions</h2>
      <p class="sub">&nbsp;</p>
      <details><summary>Is LookAtU available now?</summary><p>Not yet. This page is for our waitlist. Join and we will email you when it opens.</p></details>
      <details><summary>Can my child hide the app?</summary><p>No. The app is always visible, and your child knows it is there.</p></details>
      <details><summary>What happens when my child presses the panic button?</summary><p>You get an instant alert with your child's location, so you can call them or get help.</p></details>
      <details><summary>Which phones will it work on?</summary><p>We plan to start with Android, then iPhone. Tell us which one you need when you join.</p></details>
      <details><summary>How much will it cost?</summary><p>We have not set the price yet. Waitlist members will hear first.</p></details>
    </div>
  </section>
  <section id="join">
    <div class="wrap">
      <h2>Join the waitlist</h2>
      <p class="sub">Be the first to know when LookAtU opens.</p>
      <form id="waitlist" novalidate>
        <label for="email" class="sr">Email address</label>
        <input id="email" name="email" type="email" placeholder="you@example.com" autocomplete="email" required>
        <label for="phone" class="sr">Your child's phone</label>
        <select id="phone" name="phone">
          <option value="Android">Android phone</option>
          <option value="iPhone">iPhone</option>
          <option value="Both">Both</option>
        </select>
        <div class="trap" aria-hidden="true"><label for="website">Leave this empty</label><input id="website" name="website" type="text" tabindex="-1" autocomplete="off"></div>
        <label class="consent" for="agree"><input id="agree" name="agree" type="checkbox"> I agree to the <a href="privacy/">Privacy Policy</a> and want emails about LookAtU.</label>
        <button class="btn" id="send" type="submit">Notify me</button>
      </form>
      <div id="msg" role="status" aria-live="polite"></div>
      <p class="note" id="note">We only use your email to tell you when LookAtU opens. No spam.</p>
    </div>
  </section>
 </main>
 <footer><div class="wrap">© <span id="yr">2026</span> LookAtU. Early preview. <a href="privacy/">Privacy</a> <a href="terms/">Terms</a></div></footer>
 <script>
 // PASTE YOUR FORM URL BETWEEN THE QUOTES (example: https://formspree.io/f/abcdwxyz). While empty, the form runs in demo mode.
 var FORM_ENDPOINT = 'https://formspree.io/f/mljgogkr';
 (function(){
  var form=document.getElementById('waitlist'),email=document.getElementById('email'),msg=document.getElementById('msg'),
      btn=document.getElementById('send'),note=document.getElementById('note');
  document.getElementById('yr').textContent=new Date().getFullYear();
  if(!FORM_ENDPOINT){note.textContent='Demo mode: emails are not saved yet.';}
  function say(cls,t){msg.className=cls;msg.textContent=t;msg.scrollIntoView({block:'nearest'});}
  form.addEventListener('submit',function(e){
    e.preventDefault();
    var v=email.value.trim();
    if(!/^[^\s@]+@[^\s@]+\.[^\s@]{2,}$/.test(v)){say('err','Please enter a real email address, like you@example.com.');email.focus();return;}
    if(!document.getElementById('agree').checked){say('err','Please tick the box to agree to the Privacy Policy.');return;}
    if(document.getElementById('website').value){say('ok','Thank you! You are on the list.');return;}
    if(!FORM_ENDPOINT){say('ok','Thank you! You are on the list (demo, not saved).');form.reset();return;}
    btn.disabled=true;say('','Sending...');
    var data=new FormData();data.append('email',v);data.append('phone',document.getElementById('phone').value);
    fetch(FORM_ENDPOINT,{method:'POST',headers:{'Accept':'application/json'},body:data})
    .then(function(r){
      if(!r.ok){return r.text().then(function(t){throw new Error('Error '+r.status+' '+t.slice(0,120));});}
      say('ok','Thank you! You are on the list.');form.reset();
    })
    .catch(function(err){
      say('err','Could not send. ('+(err&&err.message?err.message:'network problem')+') Please try again in a minute.');
      if(window.console)console.error('Waitlist error:',err);
    })
    .then(function(){btn.disabled=false;msg.scrollIntoView({block:'nearest'});});
  });
 })();
 </script>
 <script type="module">
 // Framer Motion ("motion") adds the animations. If it fails to load, the page still shows everything.
 try{
  var m=await import('https://cdn.jsdelivr.net/npm/motion@11.11.13/+esm');
  if(!matchMedia('(prefers-reduced-motion: reduce)').matches){
    m.animate('.hero h1,.hero p,.hero .cta',{opacity:[0,1],y:[24,0]},{duration:.7,delay:m.stagger(.12)});
    m.animate('.phone',{opacity:[0,1],y:[40,0]},{duration:.8,delay:.4});
    document.querySelectorAll('.card').forEach(function(c){
      m.inView(c,function(){m.animate(c,{opacity:[0,1],y:[24,0]},{duration:.5});});
      c.addEventListener('mouseenter',function(){m.animate(c,{y:-4},{duration:.2});});
      c.addEventListener('mouseleave',function(){m.animate(c,{y:0},{duration:.2});});
    });
  }
 }catch(e){}
 </script>
 </body>
 </html>
@@ -1,26 +0,0 @@
 <!doctype html>
 <html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Privacy Policy – LookAtU</title>
 <style>
 body{margin:0;background:#0b1220;color:#eaf0ff;font-family:system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;line-height:1.7}
 main{max-width:720px;margin:0 auto;padding:40px 20px}
 a{color:#4f8cff}h1{margin-top:0}h2{margin-top:32px}
 .draft{background:#16213a;border:1px solid #ff4d5e;border-radius:12px;padding:14px 18px;color:#a3b1d1}
 </style></head><body><main>
 <p><a href="../">&larr; Back to LookAtU</a></p>
 <h1>Privacy Policy</h1>
 <p class="draft"><strong>Draft.</strong> This page is a plain-language starting point. A lawyer must review it before LookAtU launches, because rules for children's data differ by country.</p>
 <h2>What we collect today</h2>
 <p>This website collects only the email address and phone type (Android, iPhone or both) that you type into the waitlist form.</p>
 <h2>Why we collect it</h2>
 <p>We use it only to tell you when LookAtU opens. We do not sell it. We do not use it for anything else.</p>
 <h2>Who sees it</h2>
 <p>The LookAtU team, and the service that stores the waitlist for us.</p>
 <h2>Your choices</h2>
 <p>You can ask us to delete your email at any time. Every email we send will have a way to unsubscribe.</p>
 <h2>The LookAtU app (coming later)</h2>
 <p>The app will handle location, activity and messages of children. Before launch we will publish full details here: what is collected, how it is protected, how long it is kept, and how a parent can delete it. The child will always be able to see that the app is installed.</p>
 <h2>Contact</h2>
 <p>Contact email: <em>to be added before launch</em>.</p>
 </main></body></html>
@@ -1,29 +0,0 @@
 <!doctype html>
 <html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">
 <title>Terms of Use – LookAtU</title>
 <style>
 body{margin:0;background:#0b1220;color:#eaf0ff;font-family:system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;line-height:1.7}
 main{max-width:720px;margin:0 auto;padding:40px 20px}
 a{color:#4f8cff}h1{margin-top:0}h2{margin-top:32px}
 .draft{background:#16213a;border:1px solid #ff4d5e;border-radius:12px;padding:14px 18px;color:#a3b1d1}
 </style></head><body><main>
 <p><a href="../">&larr; Back to LookAtU</a></p>
 <h1>Terms of Use</h1>
 <p class="draft"><strong>Draft.</strong> This page is a plain-language starting point. A lawyer must review it before LookAtU launches, because rules for children's data differ by country.</p>
 <h2>This is an early preview</h2>
 <p>This website is a preview of a product that is not released yet. Nothing here is an offer to sell.</p>
 <h2>Waitlist</h2>
 <p>Joining the waitlist is free and does not oblige you to buy anything. You can leave at any time.</p>
 <h2>Using LookAtU responsibly (when it launches)</h2>
 <ul>
 <li>LookAtU is for parents and legal guardians of their own children.</li>
 <li>It must not be used to watch another adult or someone else's child.</li>
 <li>The child must be able to see that the app is installed.</li>
 <li>Parents are responsible for following the laws in their country.</li>
 </ul>
 <h2>Emergencies</h2>
 <p>The panic button helps a child alert a parent. It does not replace the police or emergency services. In an emergency, call your local emergency number.</p>
 <h2>Contact</h2>
 <p>Contact email: <em>to be added before launch</em>.</p>
 </main></body></html>
@@ -0,0 +1,29 @@
 {
  "version": 1,
  "skills": {
    "caption-animation": {
      "source": "iart-ai/tiktok-video-skills",
      "sourceType": "github",
      "skillPath": "skills/caption-animation/SKILL.md",
      "computedHash": "e42c4828d3c6115dfb4d8fd3c3fd485b8e6a89c35a8835eee6dae39fb83210a4"
    },
    "countdown-video": {
      "source": "iart-ai/tiktok-video-skills",
      "sourceType": "github",
      "skillPath": "skills/countdown-video/SKILL.md",
      "computedHash": "dafb9127ededa76d0df08be73adc46e18d6ec3955153f6ecfd0f928984ce95b2"
    },
    "lower-thirds": {
      "source": "iart-ai/tiktok-video-skills",
      "sourceType": "github",
      "skillPath": "skills/lower-thirds/SKILL.md",
      "computedHash": "502c1a8a491e477dd855eb1a45469c09f6ff46a72ea841838d358d0a6a9fd790"
    },
    "short-form-video": {
      "source": "iart-ai/tiktok-video-skills",
      "sourceType": "github",
      "skillPath": "skills/short-form-video/SKILL.md",
      "computedHash": "893ea19615f3199159b9fe94f05e37a5e538e7e0c3af7f77f9f9bed7ff933423"
    }
  }
 }