The Working Approach
A product launch, a caption pass and an interactive deck are different deliverables even if all contain motion. HyperFrames routes by the requested result: a website-led promo, plain captions on existing footage, beat-synced music, a short motion graphic or a custom composition each has a separate path. The source also provides an explicit path for porting Remotion source.
Existing projects are not treated as blank starts. The router checks the brief and project artifacts, resumes the recorded workflow, or performs only the requested operation. For fresh creation, it captures intent in BRIEF.md, installs the selected workflow and loads specialist capabilities only as needed.
Expected Deliverables
- A workflow choice and BRIEF.md for fresh creation
- An editable HTML composition, with preview and supporting project files as the workflow requires
- A rendered video when requested; a navigable deck or reviewed storyboard can be a different endpoint
From Request to Production
- 01Identify the Project State
Distinguish fresh creation from an edit, a render-only operation or a project with an existing brief. Reuse recorded preferences rather than restarting the interview.
- 02Choose by Deliverable
Match the requested result to the workflow contract. Existing footage with captions is not a new explainer, and background music alone does not make a project music-led.
- 03Load the Required Capabilities
Install the selected creation workflow on demand. Bring in composition, motion, media, audio or CLI guidance for the work actually needed, rather than installing every workflow by default.
- 04Review and Render Deliberately
Use the workflow’s preview and checks, then render the agreed deliverable. HTML validation is not a substitute for watching the result; an explicit render-only request remains that operation.