What problem does it solve? Migrating an existing Remotion (React) video composition to HyperFrames by hand is error-prone: frame-based timing, spring physics, sequencing, and media handling all map differently, and some React patterns silently produce broken output. This Skill encodes the full API mapping, lints the source for untranslatable patterns, and validates the result with SSIM render diffs. ## Core Features & Use Cases - Source linting: scripts/lint_source.py scans the Remotion project and classifies findings as blockers (useState, useEffect with deps, async calculateMetadata, third-party React UI libraries), warnings (@remotion/lambda, delayRender, useMemo), or info (staticFile, interpolateColors), refusing translation when blockers exist and recommending the runtime interop pattern instead. - API translation references: Per-topic mapping guides cover composition parameters, sequencing, timing/springs/easings, media, transitions, Lottie, and fonts, converting Remotion idioms into data-* attributes and a single paused GSAP timeline. - Measured validation: scripts/render_diff.sh computes per-frame SSIM between the Remotion baseline and the HyperFrames render against tier-calibrated thresholds, and scripts/frame_strip.sh produces side-by-side frame strips for debugging failures. - Use Case: Given a Remotion project with a multi-scene composition using springs, audio, and staggered stat cards, lint the source, translate it to an index.html HyperFrames composition, render both versions, and confirm the translation passes the SSIM threshold before shipping. ## Quick Start Ask the AI to port your Remotion composition to HyperFrames by pointing it at your Remotion source directory and requesting a validated translation.