菜单
The routine for making a film end to end in this repo - brief, direction, build, verify, score. Phases have pass-gates. Use when starting, reviewing, or shipping any video composition.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ytrofr/claude-remotion-editor --skill video-playbook命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
The law for making a film in this repo - what makes a shot cinematic rather than a slide, and a linter that enforces it. Use before authoring any composition, when a render "doesn't feel right", or when reviewing motion work.
React reducer state management with multi-undo, coalesced drag updates, and gesture-first dispatch. Use when building interactive editors, implementing undo/redo, or managing complex UI state.
Choose between Remotion, HyperFrames, or hybrid for new video work in this project. Use when asked "should I use Remotion or HyperFrames for X", "which framework for ___", before starting any new composition, or when evaluating migration of existing scenes. Covers the dual-stack decision matrix derived from the 2026-04-22 evaluation session.
基于 SOC 职业分类
正在显示 SKILL.md
| name | video-playbook |
| description | The routine for making a film end to end in this repo - brief, direction, build, verify, score. Phases have pass-gates. Use when starting, reviewing, or shipping any video composition. |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash |
The routine lives in routines.json (house schema: phases, each with a gate; steps
typed MACHINE / AGENT / PRINCIPLE). This file is the router.
1 MEASURE THE BRIEF gate: duration x script arithmetic done, conflict surfaced
2 DECLARE THE DIRECTION gate: one big idea + restraint statement written down FIRST
3 BUILD gate: doctrine linter clean
4 LOOK gate: range-rendered and actually watched, not stills alone
5 MEASURE THE ARTIFACT gate: probes run, negative controls fired
6 SCORE gate: blind, order-swapped, baseline present
Phase 2, the restraint statement. Before any code: what is the one big idea, and what will you deliberately NOT do? A direction without a stated restraint converges on the same shell every time, and "add more effects" is the default failure mode of fixing "it feels flat". Ask the grid-fallback question: if this were reduced to a plain centred layout, what idea would break? If the answer is "not much", the direction is not ready.
Phase 4, looking at it. Stills at mid-segment frames are clean by construction.
Flicker, mount flashes, transition seams and camera judder live between waypoints and
are invisible to a still. Range-render (--frames=A-B) anything with a camera move.
| what happened | the rule it became |
|---|---|
| A brief fixed 15s AND supplied a script measuring 302s | Measure the script before accepting the duration (phase 1) |
| 3 of 5 defects in one arm were visible ONLY in the render | Phase 4 is not optional |
A cutsheet guard emitted NaN: while its test matched nan: | Every gate needs a mutation that makes it fire |
| Full render broke, scoped render clean, 5 sessions of code edits | Same code + different output ⇒ vary the ENVIRONMENT (rule 57) |
scale: 0 eaten by || 1, read by the operator as "flickering" | ?? for every numeric default |
| feTurbulence at 1920x1080 cost 1.68 s/frame | Price the grade; grain renders at 1/3 res and scales up |
video-doctrine (the law + linter) · framework-selection (Remotion vs HyperFrames) ·
scripts/bench-video/ (probes + scoring) · video-storyboard (planning artifacts)