← ClaudeAtlas

remotion-md-creator-workflowlisted

Operate the complete remotion-md creator workflow from topic intake and global Agent selection through narration approval, shooting handoff, video workflow execution, static review, approval, and delivery. Use when the user wants one connected project rather than running script authoring and video production separately.
SeanLab612/seanlab-studio · ★ 4 · AI & Automation · score 67
Install: claude install-skill SeanLab612/seanlab-studio
# Remotion MD Creator Workflow This is the project-level controller. It delegates authoring to `remotion-md-narration-script` and video production to `remotion-md-video-workflow`, while preserving one Agent pin and one auditable artifact chain. ## Invariants - Create one `creator-project.json` before authoring. - Detect installed Agents and ask the user to choose one available Agent at project creation. - Pin that Agent with `fallback: none`. Use it for narration, intelligent recut, semantic planning, and choosing shared image ingredients for already-directed animation stages. The local system still owns deterministic visual contracts, compatibility checks, icon fallback, animation, and rendering. Never switch providers automatically. - If a project pins an explicit model, accept only an Agent/model pair approved by the versioned governance registry. A conformance run alone creates a candidate, not an approval. - Require human approval at the final-script and static-review gates. - Do not render a full review video by default. Render static review evidence first. For confirmed animations, render only bounded 540p motion-risk excerpts after static QA; projects without time-sensitive visuals may proceed from static approval to delivery. Keep full continuous review as an explicit strict option. - Resume from frozen artifacts. Do not regenerate semantics or narration merely to continue a run. ## State flow Read [references/state-machine.md](references/state-machine.m