Remotion entry point

Remotion renders video from React — a composition is a React component that receives frame and fps as context, computes layout and style deterministically from those values, and is captured frame-by-frame by a headless browser. The full authoring contract lives in /remotion-core; read it before writing composition code.

1. Start from project state

Apply the first matching row; do not evaluate lower state rows:

State	Action
Explicit migration of existing HyperFrames HTML to Remotion	Read `references/routes/hyperframes-to-remotion.md`, then route directly to that workflow. Skip the intent layer.
Specific operation on an existing Remotion project: inspect, diagnose, validate, preview, render, or deploy	Perform only that operation. Skip intent and workflow routing; load `/remotion-cli` and any required domain skills.
Specific edit to an existing project	Make the edit. Do not run the intent layer.
`BRIEF.md` exists	Read `workflow` and `flow`. Execute that workflow. Ask no brief questions.
No brief, but `remotion.config.ts` or `src/Root.tsx` exists	Resume from project files. Infer the owning workflow from existing compositions. If it cannot be determined uniquely, ask one routing-only question; do not run the intent interview.
Fresh creation	Run the intent layer — `references/intent-interview.md` — then route once using § 2 table.

If a fresh request does not identify the subject or input, ask what the video is about before routing. Check preferences before asking anything (references/intent-interview.md, step 1). A figma.com input changes intake, not routing.