fx-cover-story

Turn a talking-head shot into a magazine cover — a giant Vogue-style serif masthead rises in letter by letter behind the speaker's head, with optional issue line and coverlines. Renders an MP4 for Ree

SKILL.md

GitHub

Video Studio: run every command from the Video Studio folder; ENGINE is engines/video-fx/engine (set up already: node "engines/video-fx/engine/fx.mjs" doctor should be all ✔). These lines win over the steps below where they differ:

  • Footage from a studio job: the source is jobs/<id>/source.*. Put configs and renders in jobs/<id>/fx/ (<effect>.json, <Effect>.mp4), never next to the original.
  • Never transcribe again. Before the first still or render of a range: node studio/words-convert.mjs video-fx projects/<id>/transcript/words.json jobs/<id>/fx/words-<start>-<end>.json <start> <end>, then add --words jobs/<id>/fx/words-<start>-<end>.json (same --start/--end) to every still/render of that range. To pick moments, read projects/<id>/transcript/words.json instead of fx.mjs words. Use words (Whisper small on CPU) only for a video that isn't a studio job.
  • Brand: captions use the brand purple, not gold/yellow: every config gets "captions": {"accent": "#C4B5FD"} (plus any style/y settings), the same block in every segment of one video. Graphics that take a colour use styles/brand.json (accent #8B5CF6, accentLight #C4B5FD, accentDeep #4C1D95).
  • Content: headlines, checklist items, chart labels and phone messages come from what Bryan actually says or the Content OS script's cue tags; real numbers only. Generic app mockups only, never posing as a real company's product.
  • Deliver: the spliced full video goes to jobs/<id>/preview.mp4 (review) or final.mp4 (approved); log each effect with its time range in edits.json so the review page can take notes on it. Sounds: these renders have none; add them after with studio/sfx.mjs like any style.
  • If doctor shows ✖: in engines/video-fx/engine: npm install; uv venv .venv --python 3.12 + uv pip install --python .venv/Scripts/python.exe -r requirements.txt; the matting model into models/ (URL in engines/video-fx/install.mjs); node fx.mjs browser. Don't run install.mjs (it copies these skills into ~/.claude/skills).
  • Licences: Remotion is free for companies of up to 3 people; the cut-out model (Robust Video Matting) is GPL-3.0 and is downloaded, never committed.

Cover Story — Claude Video FX 16/17

A huge white Didone word (like EDIT) fills the top of the frame and rises in letter by letter with a soft blur. The speaker is cut out and layered on top, so their head covers the bottom of the letters, exactly like a printed magazine cover. Optional small issue line under it and coverlines down the sides.

This effect cuts the speaker out of the background (person matte, cached after the first run). Output: 1080×1920, 30 fps H.264 MP4 with the original audio.

When to use it

  • Opening a video about a single big idea ("FOCUS", "SCALE", "EDIT").
  • Introducing yourself or a topic as if you're the cover story.
  • Any "text behind the person" moment where one word should own the screen.

The engine

Every Claude Video FX skill renders through one local Remotion engine:

ENGINE="engines/video-fx/engine"

The first time in a session, run node "$ENGINE/fx.mjs" doctor. If any line shows ✖, stop and follow the setup steps in the video-fx skill (or tell the user to run the kit installer). Never edit files inside the engine to make a single video work; everything is controlled through the config JSON.

Workflow

  1. Read the video. node "$ENGINE/fx.mjs" words "<video>" prints a timestamped transcript of the whole file (cached); add --detail for every word's start → end. Pick the 3–12 second stretch the user means, or the one this effect suits best. Snap the range to speech: start ~0.1s before its first word, end ~0.2s after its last word, so nothing is clipped.
  2. Decide the deliverable.
    • The clip is the moment → render that range and deliver the MP4.
    • A moment inside a longer video → render the moment's range, then put it back with splice (step 7) and deliver the full video (mention the segment file too). If the range ends before the video does, add "window": [0, <range length − 0.4>]: the effect has fully left by the window end, so keep that after the last word the graphics belong to. Captions must match the rest of the video: either caption everything (render the captions effect over the whole file with the same "captions" block as this config and splice into that render) or set "captions": {"enabled": false} here and splice into the original. The video-fx skill covers multi-effect videos.
  3. Write the config as <video name> - cover-story.json next to the video (or in the folder the user names). The engine never modifies the source video; every output is a new file. Repair misheard names with "fixes" (e.g. {"cloud code": "Claude Code"}).
  4. Check one frame before the full render: node "$ENGINE/fx.mjs" still cover-story "<video>" --start <s> --end <s> --config "<config.json>" --at <seconds into the clip> --out "<folder>/check.png" then look at the PNG. The first still or render of a new range also makes the transcript and the cut-out (about 1s of processing per 9 frames, cached per exact --start/--end, so settle the range first); after that, it's fast. The CLI prints where every "@word" lands — fix any line marked ! (word not found, default time used).
  5. Render: node "$ENGINE/fx.mjs" render cover-story "<video>" --start <s> --end <s> --config "<config.json>" --out "<folder>/<video name> - Cover Story.mp4"
  6. Review: node "$ENGINE/fx.mjs" sheet "<output.mp4>" --fps 4 writes <output>-sheet.png next to the MP4 (use --fps 2 for clips over 10s, --from/--to to zoom into a moment). For small text, grab a full-size frame: node "$ENGINE/fx.mjs" frame "<output.mp4>" --at <s>. Re-render if anything is off.
  7. Splice (moments inside a longer video): node "$ENGINE/fx.mjs" splice "<video>" --segments "<segment.mp4>@<start s>" --out "<folder>/<video name> - edited.mp4". It re-encodes the whole video to high-quality H.264 under the original (first) audio track.
  8. Tell the user the output path(s), the time range used and what the effect shows.

--start/--end cut the source down to that range (times in seconds of the original file); everything in the config is relative to the start of that range. "window": [from, to] (seconds into the range) runs the effect for only part of it, with untouched footage outside. Add --draft for a quick half-resolution preview.

Options

Option Default What it does
title "EDIT" masthead word, 1 short word reads best (EDIT, FOCUS, SCALE)
at 0.15 when the letters start rising (seconds or "@word")
outAt null optional: when the cover text fades away (null = stays to the end)
overlap 0.45 how much of the letter height the head covers, 0-1 (0.45 = classic cover)
y "auto" "auto" (place from the head position) or a 0-1 fraction for the top of the letters
widthFraction 0.9 masthead width as a fraction of the frame
weight 500 Bodoni Moda weight: 400, 500 or 700
letterSpacing -0.01 letter spacing in em (negative = tighter)
stagger 3 frames between letters
letterFrames 16 frames each letter takes to rise
color "#FFFFFF" text colour
issue "" small line under the masthead, e.g. "THE AI ISSUE · NO. 01" (empty = none)
coverlines [] list of {"title": "10x", "sub": "your output"} shown on the sides
coverlinesY 0.5 where the coverlines start, 0-1 of frame height

Run node "$ENGINE/fx.mjs" info cover-story to print these with the full default config.

Writing the config

  • title: one short word (3–6 letters reads best) that names the topic; take it from the transcript's key noun or the user's brand. Longer words get smaller automatically.
  • at: start a beat before the word is said ("@scale-0.2") or at 0.1–0.3s.
  • issue and coverlines are optional; only add them if the video has real numbers or phrases to put there (e.g. {"title": "10x", "sub": "more content"}).
  • overlap controls how much of the word the head hides (0.3 = mostly visible, 0.6 = heavily covered).

Example

Line: "This new Opus model should be capable of doing three absolutely mind-blowing things."

{
  "title": "OPUS",
  "issue": "THE MODEL ISSUE · NO. 01",
  "coverlines": [
    { "title": "3x", "sub": "mind-blowing upgrades" },
    { "title": "Swarms", "sub": "hundreds of agents" }
  ]
}

Captions

Captions are on by default, word by word, timed from the transcript. Put caption settings under "captions" in the config. This effect's defaults: style pop, centred at 74% of the frame height.

Option Default What it does
enabled true false hides captions (or pass --no-captions)
style "pop" pop white bold words with a coloured key word · caps ALL CAPS · twoTier small line + one huge key word · serif small line + big gold italic serif word with sparkles · tracked small wide-spaced caps · box words on black chips, key word on a yellow chip
y 0.74 vertical centre of the caption, 0 = top, 1 = bottom
emphasis "auto" "auto" highlights the strongest word per phrase, "none", or a list like ["course", "editing"]
accent "#FFE14D" colour of highlighted words
size 72 font size in px at 1080 wide
maxWords / maxChars 4 / 22 how much text one caption phrase holds
uppercase false force capitals

Timing references

Any option that takes a time accepts seconds from the start of the range (1.5), seconds before the end (-1), or a spoken word: "@course" (first time it is said in the range), "@course#2" (second time), "@course+0.3" / "@course-0.2" (offset), "@course:end" (when it finishes), "@build_your_own" (a phrase; underscores for spaces). Matching ignores case and punctuation, runs after fixes, and falls back to "starts with" ("@edit" finds "editing"). Words are counted within the rendered range only. A word that isn't found silently uses the effect's default time, so read the timing lines the CLI prints.

Getting it right

  • The masthead is placed from where the head is. If the speaker's head is very high in frame, set y (e.g. 0.05) and lower overlap.
  • Busy or bright backgrounds make white letters hard to read; try "color": "#111111" on light walls.
  • Keep captions low (captions.y ≥ 0.72) so they don't collide with coverlines.
  • The issue line and coverlines sit in front of the speaker (so they stay readable); keep them short so they don't run across the face or hair.
  • The cut-out follows the person. Things in front of them (a mic, a hand passing over the mic) can partly stay or partly vanish for a few frames; pick a range where the hands are clear if it matters.
  • If the render fails, read the error: "Video not found" means a bad path; "Matting model missing" or Python errors mean the install is incomplete (run doctor); a timeout usually means the machine is overloaded, so render again with fewer apps open.