What problem does it solve? Porting 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 (state, effects, third-party UI libraries) cannot translate at all. This Skill encodes the full API mapping, lints the source for untranslatable patterns, and validates the result with SSIM-based visual diffing. ## Core Features & Use Cases - Source linting with escape hatch: scripts/lint_source.py scans the Remotion project and classifies findings as blockers (useState, useEffect with deps, async calculateMetadata, third-party React UI), warnings (@remotion/lambda, delayRender, useMemo), or info, recommending the runtime interop pattern from PR #214 when translation would be lossy. - Complete API translation references: Per-topic guides cover sequencing (Sequence/Series/Loop), timing (interpolate/spring/Easing to GSAP easings), media (Audio/Video/Img/staticFile), transitions, Lottie, fonts, and Zod parameters. - Measured validation: render_diff.sh computes per-frame SSIM between the Remotion baseline and the HyperFrames render against tier-calibrated thresholds, and frame_strip.sh produces side-by-side frame strips for debugging failures. - Use Case: A user asks to migrate their Remotion marketing video to HyperFrames. The Skill lints the source, translates the composition into an index.html with a paused GSAP timeline, renders both versions, and confirms the translation passes the SSIM threshold while writing TRANSLATION_NOTES.md for any dropped constructs. ## Quick Start Ask the assistant to port your Remotion composition to HyperFrames by pointing it at your Remotion source directory and requesting a one-way migration.