← ClaudeAtlas

remotion-md-video-workflowlisted

Orchestrate this repository's resumable talking-head video workflow from source video and transcript through conservative recut, verbatim bilingual captions, semantic VisualBrief planning, approved Remotion components, static-first or full-video human review, and approval-gated validated source-resolution delivery. Use when initializing, running, resuming, diagnosing, reviewing, or delivering a video project in video-remotion/remotion-md, including future Web-console operations backed by the same manifest and runner.
SeanLab612/seanlab-studio · ★ 4 · AI & Automation · score 67
Install: claude install-skill SeanLab612/seanlab-studio
# Remotion MD Video Workflow Keep the speaker primary. Treat Remotion as a deterministic renderer and keep speech understanding outside the render process. This is the single operator-facing orchestration Skill. Keep durable rules in typed modules, manifests, and the linked reference documents rather than expanding this file with implementation detail. Split out a subordinate Skill only when a capability has an independent user trigger, lifecycle, approval gate, and test contract; retain this Skill as the stable entry point that sequences them. ## Start a project 1. Confirm the source video path. Accept an existing word-level transcript when supplied; otherwise use cached video-use Scribe transcription. 2. Initialize a versioned manifest: ```bash npm run project:init -- --id <project-id> --title "<title>" --source <video> [--transcript <transcript-json>] ``` 3. Read the generated `projects/<project-id>/project.json` before running it. Never put API keys in the manifest. 4. Read [references/workflow-contract.md](references/workflow-contract.md) when changing stages, approvals, artifacts, or Web integration. 5. Run the Doctor and project preflight before paid calls, transcription, or rendering: ```bash npm run doctor -- --project projects/<project-id>/project.json npm run project:preflight -- --project projects/<project-id>/project.json ``` The formal runner repeats preflight as its first resumable stage. A warning is inspectable; a failed check blocks downstream work.