Remotion To Hyperframes

First, keep this skill fresh — confirm with the user before running: npx hyperframes skills update remotion-to-hyperframes. A fast no-op when everything is current; otherwise it refreshes this skill plus the core domain skills it depends on before you rely on them.

Remotion to HyperFrames

The front door is /hyperframes. Use this only to port an existing Remotion (React) composition’s source into HyperFrames, one way. Authoring a new composition, re-creating from a non-Remotion source (After Effects, Framer Motion, plain React / CSS — there is no Remotion source to translate), a passing Remotion mention, or any uncertainty → read /hyperframes first: the intent layer owns every route decision.

Overview

Translate Remotion (React-based) video compositions into HyperFrames (HTML + GSAP) compositions. Most Remotion idioms have direct HyperFrames equivalents — the translation is mechanical for ~80% of typical compositions. This skill encodes the mapping and guards against the lossy 20% by refusing to translate patterns that don’t fit HF’s seek-driven model and recommending the runtime interop pattern from PR #214 (opens in a new tab) instead.

The skill ships with a tiered test corpus (T1–T4, 4 fixtures total) that grades translations against measured SSIM thresholds. Don’t translate without running the eval — a translation that “looks right” but renders 0.05 SSIM lower than the validated baseline is silently wrong.

When to use

Use this skill ONLY when the user explicitly asks to migrate from Remotion. Example trigger phrases:

• “port my Remotion project to HyperFrames”
• “convert this Remotion code to HyperFrames”
• “migrate from Remotion”
• “translate this Remotion comp”
• “rewrite this as HyperFrames HTML”

Do NOT use this skill when:

• (a) The user is authoring a new HyperFrames composition, even if they have or are A/B-testing a similar Remotion video.
• (b) The user mentions Remotion in passing without asking for migration.
• (c) The user shares Remotion code as reference material rather than asking for a translation.
• (d) The user asks for “the same video as my Remotion one” without explicitly asking to migrate the source — treat that as a fresh HyperFrames build.

NOT SUPPORTED (decline — this is not what this skill does):

• The reverse direction. Exporting a HyperFrames composition back out to Remotion (or to any other framework) is not a workflow — the translation is Remotion → HyperFrames only. Say so plainly.
• Non-Remotion sources. An After Effects project (.aep), a Framer Motion / plain-React / CSS animation, or any other tool’s source is not a Remotion composition — there is no Remotion source to translate. Re-create it natively via /general-video, or decline if HyperFrames can’t represent it.

When in doubt, default to authoring a native HyperFrames composition with /general-video (the general HyperFrames authoring flow) instead.

Workflow

Step 1: Lint the source

Run scripts/lint_source.py (opens in a new tab) over the Remotion source directory. The lint detects patterns that can’t translate cleanly:

• Blockers (refuse + recommend interop): useState, useReducer, useEffect/useLayoutEffect with non-empty deps, async calculateMetadata, third-party React UI libraries (MUI, Chakra, Mantine, antd, shadcn, Radix, NextUI).
• Warnings (translate after dropping the construct): @remotion/lambda config, delayRender, useCallback, useMemo, custom hooks.
• Info (translate with note): staticFile, interpolateColors.

If any blocker fires, stop. Read references/escape-hatch.md (opens in a new tab) and surface the recommendation message. Warnings don’t stop translation — drop the offending construct in step 3 and note the gap in TRANSLATION_NOTES.md. @remotion/lambda config is the canonical warning case: the skill drops the import + renderMediaOnLambda(...) calls but translates the rest of the composition.

Step 2: Plan the translation

Read references/api-map.md (opens in a new tab) — the index of every Remotion API and its HF equivalent or per-topic reference. Identify which topic references you’ll need based on what the source uses:

Don’t load all of them — load only what the specific source needs.

Search the live catalog for any visual effect the table does not map. When the source paints a look with no HF API equivalent — a scanline/CRT overlay, a glitch or chromatic-aberration pass, a shader wipe, a film-grain treatment — run npx hyperframes catalog --query "<the effect, in plain English>" --json before hand-writing it in GSAP. The search needs nothing installed: no project, no prior add, no account. It ranks the whole hosted registry (~400 blocks and components) from any directory, and transitions.md already takes this route for clockWipe() / iris() via npx hyperframes add sdf-iris. A real component is closer to the source than a hand-approximation, so it usually raises the SSIM rather than lowering it — but the render diff in Step 4 is still the arbiter. Hand-write the effect when a search returns nothing that fits, and record the substitution in TRANSLATION_NOTES.md either way.

Step 3: Generate the HF composition

Emit index.html with:

• Root <div id="stage"> carrying the composition’s data-composition-id, data-start="0", data-duration (in seconds), data-fps, data-width, data-height, plus one data-* per scalar prop.
• One host <div> per scene with data-composition-src="compositions/<scene>.html" and data-start / data-duration / data-track-index. The root holds no nested layout.
• One compositions/<scene>.html per scene (a <template> sub-composition): its inline <style> for layout (CSS sets the from state of every animated property), its markup, and one paused gsap.timeline({paused: true}) in the scene’s local time. Every Remotion useCurrentFrame() derivation becomes a tween on that timeline at the offset within the scene.
• window.__timelines["<scene-id>"] = tl; in each scene file, and window.__timelines["<composition-id>"] for the root’s own (possibly empty) timeline.

Custom React subcomponents inline as repeated HTML using the prop interface as the template (see parameters.md (opens in a new tab) for the per-instance data-* pattern).

Step 4: Validate

Run the eval harness — references/eval.md (opens in a new tab) for the full guide. Quick path:

# Render Remotion baseline (after npm install in the fixture)
cd remotion-src && npx remotion render <CompositionId> out/baseline.mp4

# Render HF translation
cd ../hf-src && npx hyperframes render --skill=remotion-to-hyperframes --output ../hf.mp4

# SSIM diff
../../scripts/render_diff.sh ./remotion-src/out/baseline.mp4 ./hf.mp4 ./diff

Threshold: ~0.02 below p05 of the source’s complexity tier (see eval.md‘s validated thresholds table). If the diff fails, run scripts/frame_strip.sh (opens in a new tab) to see which frames diverged, then re-read the relevant timing/sequencing/media reference.

Critical: both renders must use matching pixel format. Set Config.setVideoImageFormat("png") + Config.setColorSpace("bt709") in the Remotion source’s remotion.config.ts — otherwise the diff measures encoder differences (~0.05 SSIM hit), not translation fidelity.

Step 5: Document gaps

Anything that didn’t translate cleanly (volume ramps dropped, custom presentations approximated, fonts substituted) gets a TRANSLATION_NOTES.md written next to the HF output. See references/limitations.md (opens in a new tab) for the format.

What this skill explicitly does NOT do

• Translate React state machines. Compositions that drive animation via useState + useEffect are not deterministic frame-capture targets in HyperFrames’ seek-driven model. Recommend the runtime interop pattern.
• Run Remotion’s render pipeline alongside HyperFrames. That’s the runtime interop pattern from PR #214 (opens in a new tab) — a separate solution for compositions that fail this skill’s lint.

(@remotion/lambda is not a blocker — Lambda config is deployment, not animation. The skill drops it as a warning and translates the rest. See references/escape-hatch.md (opens in a new tab).)

How to grade your own translation

Run the test corpus orchestrator:

./assets/test-corpus/run.sh

It runs T1, T2, T3 (render + diff) and T4 (lint validation), prints a per-tier pass/fail table, and emits an aggregate JSON report. Use this to verify the skill is working end-to-end on a clean checkout — and as a regression check after editing any reference.

Validated baseline (as of 2026-04-27):