remotion-composer

name	remotion-composer
description	Assemble finished shot assets into the compact Remotion render plan for this project. Use after composer artifacts and asset jobs exist, when writing or updating lesson-plan JSON, Remotion component props, sequence timing, presenter media placement, Hyperframes atom placement, and final timeline assembly.

Remotion Composer

Overview

Turn completed briefs and assets into a small component-facing render plan. Do not encode the full creative reasoning into JSON.

Inputs

• global-style-spec.json
• section-map.json
• completed shot briefs
• asset paths and durations
• transition map
• current Remotion component catalog

Rules

• Keep the final render plan minimal: timeline, component, timing, media, and props needed to render.
• Reuse component defaults and global style where possible.
• Use Remotion for timeline, layering, presenter media, captions, and source-aware transforms.
• Use Hyperframes atoms as media assets when the animation is pre-rendered HTML motion.
• Premount or buffer video-heavy assets when the implementation supports it.
• Make timing explicit enough to render deterministically.
• Keep one continuous presenter/audio track for the source recording. When showing the presenter as a docked widget over content, add a muted presenter layer with matching mediaStart; do not duplicate audio.
• Render plans must carry named presenter docks or reserved rectangles when content and presenter share the canvas.
• Do not use rough script timestamps for final cue timing. Use ASR/manual cue timestamps; mark scaled estimates as provisional.
• Preserve creator effect ownership from the shot brief. Render only executable Remotion-owned fields in the final plan; keep rationale, fallback, and QC targets in composer artifacts unless the renderer consumes them.

Output

Return:

• files changed
• render plan summary
• validation command
• remaining assumptions

Read references/render-plan-contract.md before changing the render plan contract.