mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-17 15:24:19 +00:00
fix(skill): beats must have continuous motion, not just entrance animations
The #1 quality problem: agents write entrance tweens in the first 1-2 seconds of a beat, then nothing happens for the remaining duration. A 13-second beat with 6 tweens = 11 seconds of static content. step-3: Animation Sequence section now explicitly requires events spanning the FULL beat duration. Nothing unchanged for more than ~2 seconds. beat-builder-guide: "Continuous motion" added as the first and most important rule — above all technical rules. Ken Burns drift, parallax, breathing, secondary elements appearing mid-beat.
This commit is contained in:
@@ -115,6 +115,10 @@ Tell the main agent:
|
||||
|
||||
---
|
||||
|
||||
## Continuous motion — the most important rule
|
||||
|
||||
A beat is a SCENE, not a single entrance animation. Your GSAP timeline should have events spread across the ENTIRE beat duration — not just entrance tweens in the first 1-2 seconds followed by nothing. If an element is on screen, it should be doing something: drifting, breathing, parallaxing, revealing new details, transforming. Nothing sits unchanged for more than ~2 seconds. After elements enter, add continuous hold motion: Ken Burns drift on images, subtle y/scale breathing on text, parallax layers moving at different speeds, secondary elements appearing mid-beat.
|
||||
|
||||
## Rules
|
||||
|
||||
- SCRIPT PLACEMENT: scripts inside `<template>`, never after `</template>`. Scripts outside see no DOM.
|
||||
|
||||
@@ -264,17 +264,13 @@ Two numbers Step 5 needs to wire `data-start` and `data-duration` correctly:
|
||||
|
||||
Example: `Transition in at: 4.2s · GSAP duration: 5.5s` → Step 5 sets `data-start="4.2" data-duration="5.5"`.
|
||||
|
||||
### Animation Sequence
|
||||
### Animation Sequence — must span the ENTIRE beat
|
||||
|
||||
Millisecond-level choreography for everything in this beat. The sub-agent executes this — it doesn't invent it. Every entrance, hold, camera move, layer event, and exit with a timestamp.
|
||||
A beat is a SCENE with internal life, not a single entrance followed by a static hold. Things should be happening throughout the entire duration — new elements appearing, existing elements transforming, camera drifting, details revealing, sub-moments unfolding.
|
||||
|
||||
If you know exact GSAP values — write them. If you don't, describe the feel and behavior specifically enough that the sub-agent can derive the right values: "snappy overshoot bounce settling into place" tells the sub-agent to use back.out; "slow heavy drift" tells it to use power1.inOut with a longer duration. Vague adjectives are useless — describe what the motion physically does and how it feels.
|
||||
If your animation sequence only has events in the first 2 seconds and the beat lasts longer, the rest is dead air. Plan moments across the full duration. Nothing should sit unchanged for more than ~2 seconds — if an element is on screen, give it continuous motion (drift, breathe, pulse, parallax).
|
||||
|
||||
FORMAT EXAMPLE of structure (write the real choreography for THIS beat):
|
||||
|
||||
- `0.0s`: [what appears or starts, and how it feels/behaves]
|
||||
- `0.Xs`: [next event — either exact values or precise behavioral description]
|
||||
- `[beat-end - 0.4s]`: [exit / transition fires]
|
||||
Describe the feel precisely: "snappy overshoot bounce settling into place" → back.out; "slow heavy drift" → power1.inOut. Vague adjectives are useless.
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user