mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-15 22:08:03 +00:00
ukimsanov
14f218070f
introduction: the showcase file has a single h264 stream and no audio track, so 'press play - it has sound' was simply untrue. Removed the claim; the caption now only says what the clip is. workflows: the page listed all eight situations twice - once as cards linking to anchors a short scroll down, then again as full sections repeating the same 'best for' line. Collapsed both into one accordion per situation whose title is the chooser and whose body holds the brief and the copyable request, so the eight cards now lead somewhere real instead of jumping down the page. Dropped the five-step 'what happens after you choose' (it restates quickstart) and the six-part request checklist (it restates the prompting guide) in favour of links. 187 lines to 165, eleven headings to one; no starter request was lost.
138 lines
6.2 KiB
Plaintext
138 lines
6.2 KiB
Plaintext
---
|
|
title: "Choose a creation workflow"
|
|
sidebarTitle: "Choose a workflow"
|
|
description: "Find the situation that matches yours, copy the request, and let the agent confirm the direction before it builds."
|
|
---
|
|
|
|
You do not need to learn HyperFrames' internal workflow names. Open the situation that resembles yours, copy the request, and adjust it.
|
|
|
|
<Tip>
|
|
First HyperFrames project? Follow [Make your first video](/quickstart) instead — it walks the whole path once. This page is the faster route when you already know what HyperFrames is.
|
|
</Tip>
|
|
|
|
<AccordionGroup>
|
|
<Accordion title="A product, website, or launch brief" icon="rocket">
|
|
**Best for** launch videos, product tours, promos, and showcases that should use the product's real interface.
|
|
|
|
**Give the agent** a public URL or launch brief, the audience, the main promise, and any claims or screens that must appear.
|
|
|
|
```text
|
|
/hyperframes Make a 45-second launch video for https://example.com.
|
|
It is for small design teams. Show the real interface, focus on how quickly
|
|
a team can go from an idea to a shared result, and end with “Try it together.”
|
|
Keep the pacing confident rather than frantic.
|
|
```
|
|
|
|
[Product and website workflow →](/guides/product-launch-video)
|
|
</Accordion>
|
|
|
|
<Accordion title="Notes, an article, or an idea" icon="lightbulb">
|
|
**Best for** explainers where every visual is invented from the subject rather than captured from a product site.
|
|
|
|
**Give the agent** the source text, who needs to understand it, the desired takeaway, and the maximum length.
|
|
|
|
```text
|
|
/hyperframes Turn these notes into a 60-second visual explainer for a
|
|
non-technical audience. The viewer should understand the three stages and
|
|
why the second one prevents mistakes. Use diagrams and typography rather
|
|
than stock footage.
|
|
```
|
|
|
|
[Explainer workflow →](/guides/faceless-explainer)
|
|
</Accordion>
|
|
|
|
<Accordion title="Existing talking-head footage" icon="video">
|
|
Choose by what must happen to the clip:
|
|
|
|
| Desired result | Best route |
|
|
| --- | --- |
|
|
| Plain or expressive subtitles; footage otherwise untouched | Embedded captions |
|
|
| Titles, quotes, lower thirds, data callouts, or side panels over untouched footage | Talking-head recut |
|
|
| Remove pauses, reorder speech, replace shots, or change the underlying edit | Custom video |
|
|
|
|
```text
|
|
/hyperframes Add clean word-level captions to this interview clip. Keep the
|
|
footage and audio unchanged. Use high contrast and emphasize only the most
|
|
important phrase in each sentence.
|
|
```
|
|
|
|
[Captions and designed recuts →](/guides/captions-and-recuts)
|
|
</Accordion>
|
|
|
|
<Accordion title="A pull request" icon="code-pull-request">
|
|
**Best for** a feature reveal, fix explanation, refactor summary, or team changelog built from a GitHub PR.
|
|
|
|
**Give the agent** the PR link, the audience, the tone, and whether to emphasise user impact or implementation.
|
|
|
|
```text
|
|
/hyperframes Turn https://github.com/example/repo/pull/123 into a concise
|
|
feature reveal for product engineers. Lead with what changed for users,
|
|
then show the two most important code decisions. Keep it under 60 seconds.
|
|
```
|
|
|
|
[PR-to-video workflow →](/guides/pr-to-video)
|
|
</Accordion>
|
|
|
|
<Accordion title="A short motion-first idea" icon="wand-magic-sparkles">
|
|
**Best for** motion-is-the-message pieces, usually under ten seconds, with no narration.
|
|
|
|
**Give the agent** the exact text or data, dimensions, duration, visual tone, and whether the background must be transparent.
|
|
|
|
```text
|
|
/hyperframes Create a six-second vertical motion graphic announcing
|
|
“10 million renders.” Count up to the number, then reveal the label.
|
|
Use bold editorial type and export with a transparent background.
|
|
```
|
|
|
|
[Motion graphics workflow →](/guides/motion-graphics)
|
|
</Accordion>
|
|
|
|
<Accordion title="A music track" icon="music">
|
|
**Best for** lyric videos, beat-synced slideshows, visualisers, and promos where the music sets the pacing.
|
|
|
|
**Give the agent** the audio file, any lyrics, the media to cut, and the intended format.
|
|
|
|
```text
|
|
/hyperframes Make a 30-second vertical promo driven by this music track.
|
|
Cut the attached product stills on the major beats, reserve the chorus for
|
|
the strongest image, and end on the supplied logo.
|
|
```
|
|
|
|
[Music-to-video workflow →](/guides/music-to-video)
|
|
</Accordion>
|
|
|
|
<Accordion title="A presentation" icon="display">
|
|
**Best for** discrete slides with fragment reveals, speaker notes, branching, presenter mode, or clickable navigation.
|
|
|
|
Ask for a **slideshow** explicitly, so the result stays a navigable deck instead of becoming a rendered linear video.
|
|
|
|
```text
|
|
/hyperframes Build a ten-slide interactive product briefing from these
|
|
notes. Use progressive reveals, add speaker notes, and include a final
|
|
branch where the presenter can open either the roadmap or pricing detail.
|
|
```
|
|
|
|
[Slideshow workflow →](/guides/slideshow)
|
|
</Accordion>
|
|
|
|
<Accordion title="Something custom" icon="shapes">
|
|
**Best for** longer or unusual work: multi-scene montages, title cards, static loops, mixed media, or projects where you want to co-create the structure with the agent.
|
|
|
|
```text
|
|
/hyperframes Plan a 90-second brand reel from these three product films
|
|
and this logo. Co-design the structure with me before building: propose a
|
|
scene order and the feeling of each section, then wait for my approval.
|
|
```
|
|
|
|
[Custom video workflow →](/guides/general-video)
|
|
</Accordion>
|
|
</AccordionGroup>
|
|
|
|
## After you choose
|
|
|
|
Install the guidance once with `npx hyperframes skills update`, then send your request starting with `/hyperframes`. The agent confirms the creative direction before it builds, so correct the message, length, and format at that point rather than after a finished video exists.
|
|
|
|
When the first version opens, make direct visible edits in [Studio](/studio) and ask the agent for anything that affects the story, several scenes, or new media. Export from Studio's **Renders** panel. If something blocks you, start from the symptom in [Get unstuck](/help).
|
|
|
|
Writing a stronger request is its own short guide: [Give your agent a useful brief](/guides/prompting).
|