Skip to content
hyperframes-keyframes logo

HyperFrames Keyframes

hyperframes-keyframes

Use when a HyperFrames composition needs a punch-in, punch-out, zoom, reframe, Ken Burns treatment, camera move, visual match/whip handoff, or other seek-safe 2D/3D keyframes; also for GSAP, CSS keyframes, Anime.js, WAAPI, FLIP, paths, masks, SVG morph/draw, text trails, 3D depth, or `hyperframes keyframes` diagnostics. Don't use for broad scene strategy, brand design, media sourcing, captions, or general video planning.

heygen-com/hyperframes509.7Kinstalls57Kstars

SKILL.md

Full skill instructions

Plugin installs: Before setup or freshness commands, follow plugin execution rules when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.

HyperFrames Keyframes

Keyframes are a pose contract: visible states, continuous subject identity, seek-safe runtime, verified pixels.

Use hyperframes-animation for broad scene recipes. Use hyperframes-cli for full command docs. Use references/​keyframe-patterns.md only when choosing implementation mechanisms, not visual style.

Creator editing boundary

Keyframes own visual motion, not clip assembly. Source-range hard cuts, trim, splice, and reorder belong to /​hyperframes-core: author one media element per kept range, place it with data-start and data-duration, and select its source offset with data-media-start. Adjacent ranges make a hard cut. A crossfade uses overlapping clips on different tracks plus visual opacity keyframes; sound fades use /​hyperframes-audio.

Creator requestTruthful mechanism
Punch-in / punch-outKeyframe scale with x/y or percentage translation on a non-timed visual/​crop wrapper inside the clip. Use a set/​short tween for a hard punch and a tween for a smooth move.
Smooth multi-state zoom or reframeKeep one subject wrapper alive and author multiple zoom/​reframe states as a pose ladder with per-segment easing.
Pan, reframe, or Ken Burns camera moveAnimate wrapper translation plus scale. Geometry is authored; this is not face tracking or automatic semantic reframing.
Chained camera movesChain labeled transform beats on one registered seek-safe timeline.
Match cut or whip pan/​hyperframes-animation owns the visual handoff; /​hyperframes-registry supplies primitives; keyframes preserve authored geometry, direction, and velocity. There is no automatic matching-frame discovery.
Crop and mask reframeInterpolate clip-path or a mask on an inner visual wrapper to crop/​reframe without changing source time. Polygon keyframes can form a polygon/​mask transition.
Directional wipe cut or iris/​reveal cutAnimate a mask/​clip boundary across overlapping visual clips; /​hyperframes-animation owns the handoff choreography.
Split-screen handoffKeep both visual clips placed by core, then keyframe their inner crop/​mask wrappers and divider geometry.
Constant source retime/​hyperframes-core owns normalized data-playback-rate (0.1..10) for render-safe picture and pitch-preserved sound. It is constant for the whole media element.
Source speed rampsA rate lane in data-automation on the <video>/<audio> (t in clip seconds, v 0.1..10, log interpolation); it wins over the constant rate.
Freeze / holdA visual pose, final source frame, or finished sub-composition can hold. Arbitrary mid-source freeze is not supported; preprocess a still/​derived segment, place it as its own clip, then resume with another source range.

When editing picture and sound together, load /​hyperframes-core, this skill for visual motion, and /​hyperframes-audio for fades, crossfades, volume automation, ducking/​carve, or effects on the placed tracks.

A visual transition or cropping treatment is not a temporal source trim or splice. /​hyperframes-core owns the timeline, clip timing, and source ranges; keyframes only animate the visible handoff or crop on wrappers inside those clips. For copyable combined picture/​sound recipes, use /​hyperframes-core → references/​creator-editing-recipes.md.

Procedure

  1. Identify the animated subject, visible states, final state, and runtime.
  2. Choose the smallest mechanism that proves the prompt. Read references/​keyframe-patterns.md only if the mechanism is unclear.
  3. Author seek-safe keyframes in the declared runtime. Build synchronously and register the runtime instance.
  4. Verify with hyperframes lint, hyperframes check, hyperframes keyframes, one focused --shot, and snapshots at proof times.
  5. If proof fails, fix the source keyframes and rerun the smallest failing diagnostic before rendering.

Contract

  • Name the moving subject.
  • Name the poses needed to prove the intended motion, including the final state.
  • Keyframe visible channels, not hidden helper state.
  • Preserve object identity when continuity matters.
  • Crossfade only when the intended motion is replacement or dissolve.
  • Hold readable or semantic states long enough to see.
  • Final frame is part of the animation, not cleanup.
  • Do not reset to rest unless requested.
  • Do not end on black unless requested.
  • If editing a starter scene, preserve layout, copy, assets, colors, and final state unless asked to redesign.

Runtime Rules

GSAP:

  • build synchronously at page load
  • use gsap.timeline({ paused: true })
  • register as window.__timelines[compositionId]
  • registry key must match data-composition-id
  • do not call tl.play() for render-critical motion
  • keep repeats finite

CSS keyframes:

  • finite duration and iteration count
  • deterministic delay
  • animation-fill-mode: both
  • use data-start when timing belongs to a clip

Anime.js:

  • create synchronously
  • autoplay: false
  • finite duration and loops
  • push every instance to window.__hfAnime

WAAPI:

  • finite duration
  • fill: "both"
  • deterministic construction
  • the text surface does not list WAAPI; verify with --shot (it seeks WAAPI) and snapshots

Never use for render-critical motion:

  • Date.now()
  • performance.now()
  • unseeded Math.random()
  • hover/​scroll triggers
  • timers
  • async-created timelines
  • unregistered requestAnimationFrame
  • infinite loops

GSAP Skeleton

const root = document.querySelector("[data-composition-id]");
const compositionId = root.dataset.compositionId;
const tl = gsap.timeline({ paused: true });

tl.addLabel("state-a", 0);
tl.to(".subject", {
  keyframes: [
    { x: 0, opacity: 1, duration: 0.2 },
    { x: 120, opacity: 1, duration: 0.4, ease: "power2.out" },
    { x: 100, opacity: 1, duration: 0.2, ease: "power2.inOut" },
  ],
  ease: "none",
});

window.__timelines = window.__timelines || {};
window.__timelines[compositionId] = tl;

Use labels for semantic states. Use position parameters instead of chained delays. Use immediateRender: false for later from()/fromTo() tweens touching the same property.

Keyframe Forms

  • Array keyframes: pose ladder with per-step duration/​ease.
  • Percentage keyframes: exact timing inside one tween.
  • Property arrays: compact multi-stop changes.
  • ease: "none" on the parent when each stop carries its own easing.
  • easeEach when every segment should share the same feel.

Do not copy numeric distances or timing from examples. Derive them from the actual composition geometry and duration.

For one subject moving between two boxes, prefer one continuous transform tween or FLIP. Split x/​y/​scale into multiple eased keyframes only when the viewer should feel distinct beats; every segment changes velocity and can read as a hitch.

Channels

Prefer compositor/​visual channels: x/​y/​z, xPercent/​yPercent, scale, rotationX/​Y/​Z, skew, transformOrigin, svgOrigin, opacity, autoAlpha, clip-path, masks, CSS vars, SVG path/​dash values, camera transforms, shader uniforms.

Avoid layout/​lifecycle channels: top/​left/​right/​bottom, width/​height, margin/​padding, display, visibility, late DOM creation, helper overlays doing subject motion.

For visibility changes, use autoAlpha on the registered seekable GSAP timeline, or a zero-duration tl.set() at an explicit boundary. Target only a non-clip element or a wrapper inside the clip; never target .clip itself. Never duration-tween raw visibility, and never tween display.

Mechanism Choice

Choose the smallest mechanism that proves the prompt:

NeedMechanism
Same subject changes box or hierarchyshared element / FLIP
Subject travels a visible routepath travel
Stroke grows or tracesstroke draw
Shape becomes another shapeshape interpolation
Reveal boundary is visibleclip, mask, or shader uniform
Many items move with orderstagger / indexed delay
Text itself movesline, word, character, or band subdivision
Surface bends, stretches, or cropsparent/​child counter-transform
UI has statesexplicit state machine
Scene has depthDOM 3D, Three.js, or WebGL camera/​object keyframes

Mechanisms can combine, but each one must clarify the idea. Decoration is not proof.

Timing

  • Anticipation only when it clarifies cause or direction.
  • Acceleration leaves rest.
  • Peak proof shows the mechanism unmistakably.
  • Follow-through sells energy and direction.
  • Overshoot only when the subject should feel elastic or tactile.
  • Constant-speed path travel usually needs ease: "none".
  • Discrete UI states usually need a sharp ease-out.
  • Repeated elements need ordered offsets, not identical timing.
  • Final lockups need longer holds than transition poses.
  • Smoothness means continuous velocity on the same subject.
  • Do not overlap tweens that write the same transform property unless the overlap is intentional and verified.
  • Avoid animating large clip-path/​mask changes while the same hero surface is also scaling or traveling; use nested reveals after the main move settles.

Text

Preserve line boxes, word spacing, readability, and final fit. If text moves internally, move the glyphs or masked bands, not only decorations around the text. Snapshot readable frames.

SVG

For stroke growth prefer DrawSVGPlugin, then stroke-dasharray/stroke-dashoffset. For shape interpolation prefer MorphSVGPlugin; convert primitives to paths when needed and split complex silhouettes into simpler parts.

3D

Scale alone is fake depth. Use perspective on a stable parent, transform-style: preserve-3d, z travel, rotation, camera/​world motion, occlusion, and layer order when objects cross.

Use one or two diagnostic angles that expose the depth relationship. If angled proof shows no depth crossing, improve z/​camera/​occlusion.

Canvas / WebGL

Keyframe camera position, camera target, object transform, material opacity, shader uniforms, and postprocess intensity through deterministic state. Render from HyperFrames time. Use --ghost because marker boxes cannot see internal canvas motion.

CLI Proof

npx hyperframes lint
npx hyperframes check
npx hyperframes keyframes .
npx hyperframes keyframes . --json
npx hyperframes keyframes . --runtime all
npx hyperframes keyframes . --selector "<selector>" --shot "<file>" --samples <n>
npx hyperframes keyframes . --selector "<selector>" --shot "<file>" --layout strip --from <t0> --to <t1>
npx hyperframes keyframes . --shot "<file>" --ghost --angle <angle>
npx hyperframes snapshot . --at <times>

Choose <selector> for the real animated subject. Choose <times> for first frame, proof poses, final-minus-hold, and exact final. Choose <angle> only when depth must be proven.

ToolProves
keyframestargets, explicit stops, paths, traces, composed parent/​child motion, CSS stops, Anime registration
--shotghosts, route shape, time spacing, DOM 3D projection, focused selector proof
--layout stripin-place motion, overlaps, contact, subtle scale/​opacity, text waves
--ghostcanvas, WebGL, shader motion, rendered 3D
snapshot --atmasks, text readability, full state, final lockup, black/​reset tails

If selector proof looks wrong:

  1. rerun --json
  2. find the actual animated target
  3. shoot that target
  4. snapshot full frames
  5. trust painted pixels over logs

Diagnostic Reading

flat means no explicit middle poses. keyframes means explicit stops exist. motionPath means a route exists. trace means multi-stroke drawing. composed with means child motion inherits parent motion.

Even ghost spacing means constant speed. Clustered ghosts mean slow-in or settle. Large gaps mean fast travel.

A helper-selector shot is not proof. An onion shot over a broken full frame is not proof.

Error Handling

FailureFix
endpoint-onlyadd middle poses, hold peak proof, rerun --shot
identity breakkeep one element alive, use shared source/​final boxes, remove substitute crossfade
fake 3Dadd z/​camera travel, occlusion, angled proof
wrong finaladd final hold, snapshot final-minus-hold and exact final
unseekable runtimepause autoplay, register instance, remove timers, build synchronously
unreadable textpreserve line boxes, reduce displacement, add final hold, snapshot text frames

Done

Run hyperframes lint, hyperframes check, hyperframes keyframes, one focused --shot, and snapshots. Confirm first frame, proof poses, final-minus-hold, exact final, subject-owned motion, and no debug overlays.

More skills from heygen-com

hyperframes-core logo
heygen-com/hyperframes

hyperframes-core

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

57K 661.5K
View
hyperframes-animation logo
heygen-com/hyperframes

hyperframes-animation

All animation knowledge for HyperFrames — atomic motion rules, multi-phase scene blueprints, scene transitions, broader motion-design techniques, AND the seven runtime adapters (GSAP default, plus Lottie, Three.js, Anime.js, CSS keyframes, Web Animations API, TypeGPU). Use for any motion or animation task: pick 2-4 rules and compose, or load a blueprint, or look up runtime-specific API (e.g. GSAP eases / Lottie player / Three.js mixer). Also covers auditing an existing composition's choreography (animation map) and 24 named text-animation effects. HyperFrames-native: single paused timeline, seek-safe, deterministic.

57K 653.9K
View
hyperframes-creative logo
heygen-com/hyperframes

hyperframes-creative

Non-animation creative direction for HyperFrames videos. Use for design spec (frame.md / design.md) handling, palettes, typography, narration, beat planning, audio-reactive visuals, composition patterns, and brand / style decisions. For atomic motion patterns and scene blueprints, use `hyperframes-animation`.

57K 624.7K
View
general-video logo
heygen-com/hyperframes

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated motion-first unit, including an animated title. Route fresh creation through hyperframes before using this skill.

57K 428.7K
View
remotion-to-hyperframes logo
heygen-com/hyperframes

remotion-to-hyperframes

Migrate React-based Remotion video compositions to HyperFrames HTML with validated frame-accuracy.

57K 374.9K
View
product-launch-video logo
heygen-com/hyperframes

product-launch-video

Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.

57K 360.2K
View
faceless-explainer logo
heygen-com/hyperframes

faceless-explainer

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a website (/product-launch-video — promo or tour). Unclear → /hyperframes.

57K 350.7K
View
motion-graphics logo
heygen-com/hyperframes

motion-graphics

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI animation (scroll, cursor, callouts), or fusing a real image's geometry into a chart. Usually under 10s (up to ~30s), no narration or live-action subject; renders to MP4 or transparent overlay. Longer / narrated / multi-scene → /general-video. Unclear → /hyperframes.

57K 349.8K
View
embedded-captions logo
heygen-com/hyperframes

embedded-captions

Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet `anchor` rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.

57K 314.3K
View
pr-to-video logo
heygen-com/hyperframes

pr-to-video

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

57K 306.4K
View
music-to-video logo
heygen-com/hyperframes

music-to-video

Turn a music track (an audio file, a video to pull audio from, or a track generated from a mood brief) into a beat-synced video — lyric video, slideshow, or kinetic promo. The music drives all pacing; any user-supplied images/videos are cut onto the same beat grid, and a complete video needs zero assets. Narrated pieces → the input-matched workflow (see /hyperframes). Unclear → /hyperframes.

57K 287.6K
View
slideshow logo
heygen-com/hyperframes

slideshow

Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't explicitly ask for a slideshow, confirm before authoring. Unclear → /hyperframes.

57K 275.4K
View

Popular AI tools

Kaiber logo
Video

Kaiber

Generate, edit, and beat-sync AI video with leading models in one workspace.

Paid
View
Vimcal logo
Productivity

Vimcal

The world's fastest calendar for remote work

Free
View

Transform Your Design with AI Designer by ImgCreator.ai

Freemium
View
Akool AI logo
Content & writing

Akool AI

Revolutionizing Video Production with AI-Powered Creativity

Paid
View

Extend an image past the frame and let AI fill the new aspect ratio.

Freemium
View
StarByFace logo
Security

StarByFace

Discover your celebrity doppelgänger with StarByFace!

Free
View
C

ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.

Freemium
View
Opus Clip logo
Coding & apps

Opus Clip

Opus.ai: Revolutionize Your Web Experience

Free
View