mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-19 19:36:04 +00:00
Real-AI-test artifact (huly opener): agent entered the app-name labels
("Linear, Jira, Slack, Notion, Docs") staggered, then held them for
~2 seconds while the beam built. To "keep them alive" during the hold,
the agent scheduled `tl.to(labels, { opacity: 1 }, "+=2")` — an
opacity-only breath. At 1920×1080 a 15% opacity oscillation is
invisible; the labels read as frozen for the first ~2s of the video.
Agent's own retro on the failure: "That opacity breath is invisible at
video scale — it's exactly the 'hold with breathing' micro-animation
the playbook tells you not to rely on. So functionally the labels are
frozen for ~2 seconds. It fights the hook."
User's instruction on encoding this as a rule (verbatim): "yes maybe
something like that, just so that AI wouldn't take it as oh damn it
gotta move and do something MOVEE, but just meaning it shouldn't
stay still..."
Encoded the rule in two places with calibrated language — explicitly
NOT "everything must bounce" but "presence requires life":
1. skills/website-to-hyperframes/references/step-3-storyboard.md —
new "Alive, not active" section in the opener-design block (right
after the hook patterns, before the CTA section). Names the
failure mode literally (opacity-only breath → reads as paused
slide), then lists the four valid continuous-motion patterns
(drift, camera dolly, wobble, parallax) with magnitudes calibrated
to be felt-not-watched. Reinforces "one pattern per element, don't
stack" so the orchestrator doesn't over-spec. Also notes the
carve-out: deliberate stillness as the CONCEPT (the Negative space
hook) stays valid — the difference is whether the stillness is
doing work.
Also touched the CTA paragraph to extend the rule there — the
"logo held still after entry" failure is the same failure mode in
the closing beat.
2. skills/website-to-hyperframes/references/beat-builder-guide.md —
- Extended landmine #6 (Hold with breathing) to explicitly call
out the opacity-breath variant as the most common version of
the failure, with the literal `opacity: 0.85 → 1.0` tween shape
so workers grep-match it in their own code.
- New landmine #8 "Alive, not active — no frozen readable text."
Names the rule, lists the four patterns, says "one per element,
don't stack" three different ways because the over-correction
("MOVEE!") is the second-order failure to head off. Closes with
a self-check: for every on-screen-for-more-than-1s element, can
you point at the GSAP tween carrying it through its lifetime?
If no, add one of the four.
Tone calibration:
- Explicit "fix is NOT make it move more"
- "Goal: the frame feels alive; the viewer can't point at 'the
motion' if asked" — defines the upper bound (subtlety)
- Magnitudes are floors (4-8px, 1.0→1.04+, ±1.5-3°), not pushes
- Negative space stillness as concept is preserved — the rule names
unintentional frozen-during-hold as the failure, not all stillness
No code change. The rule is doc-only because the perception gate
(check-rendered-perception.mjs) can't detect "this is visibly frozen
at video scale" — that's a quality judgment, not a binary failure.
Encoded as a sub-agent rule so workers honor it at write time, and
as a storyboard rule so orchestrators name the motion pattern per
element when they spec the beat.
Followups (separate):
- huly creative critique (opener stillness) — addressed by this rule.
- heygen creative critique (CSS cube instead of the real Orb mp4) —
addressed by commits 570dedbd (capture-video CLI) + e6aa7fed
(captured videos doc landmine).