remotion-video-pipelinelisted
Install: claude install-skill tomerhayundev/skills
# Remotion video pipeline
A pipeline where adding a clip is a data change, not an animation job. Built and
proven on a real product (nine scenes, four aspects, two locales, ~120 renders),
then generalized here so the next project starts from the lessons, not from zero.
**The core idea: a clip is a manifest row, not new code.** A 15-second ad is a
chain of frame ranges sliced out of scenes that already exist. Writing a new scene
is the last resort.
## Decide what the ask is
1. **Does it already exist?** List compositions (`remotion compositions` or the
project's dry-run). Often the ask is a file that is already rendered.
2. **Is it a new cut of existing footage?** Add a manifest row. Done.
3. **Is it a new product moment?** Write one new scene, register it, give it a
focus rect and a containment test. See [architecture](references/architecture.md).
4. **No pipeline yet?** Scaffold it in this order: tokens, one scene on the square
canvas, the registry, `expand()`, the chain `Clip`, the render script, then the
music bed. Each step is in [architecture](references/architecture.md).
5. **One continuous take, with an element that travels through every moment** (a
thread, a line, a cursor)? Not a manifest chain: see
[one-take-film](references/one-take-film.md) for its architecture, motion, camera and tests.
## Architecture in one screen
| Piece | Rule |
| --- | --- |
| Canvas | Author every scene on one square canvas (1920x1920). Each aspect ratio is a camera