# claude-video-kit

**English** · [中文](./README.zh.md) · [README.en.md](./README.en.md)

Turn a research brief or JSON script into a **vertical explainer** — TTS + caption alignment + Remotion — without opening a timeline editor.

**Who it's for:** people already writing research / technical explainers in Claude Code or Cursor who want a repeatable 9:16 pipeline with a **pre-render review gate**. **Who it's not for:** one-click “topic → AI b-roll Short” factories. We optimize for auditable scripts and reproducible motion graphics, not generative video lottery.

> **[v0.3.0-rc.1](https://github.com/runesleo/claude-video-kit/releases/tag/v0.3.0-rc.1) (public release candidate):** installable `video-explainer` Agent Skill. Independent review receipt must bind to the exact `script.json` before render. Skill never uploads or publishes.

## Fastest first success: Agent Skill

```bash git clone https://github.com/runesleo/claude-video-kit.git cd claude-video-kit npm ci --prefix remotion npx skills add runesleo/claude-video-kit --skill video-explainer npm run doctor -- --output /tmp/video-explainer-first-success npm run demo -- --output /tmp/video-explainer-first-success

# npm scripts are thin wrappers — the underlying command works the same: # node scripts/video-explainer.mjs demo --output /tmp/video-explainer-first-success ```

The Skill orchestrates this local clone (it does not bundle Remotion). Demo creates a script-bound pass receipt, uses macOS `say` as an explicitly **demo-quality** voice, renders 1080×1920, and runs the shorts verifier — no API key, no upload. For real projects: `review` then `render`; `fix` / `block` / missing / stale receipts cannot start rendering. The six review checks are product-defined; pass/fail is judged by the reviewer — the tool enforces process, not truth.

> Editing scripts or compositions? Read [docs/DESIGN.md](docs/DESIGN.md) first — it's the design system contract.

## What you get

- **One-command pipeline** — `./scripts/rende