What problem does it solve? Porting an existing Remotion (React) video composition to HyperFrames by hand is error-prone: timing math, easing curves, sequencing offsets, and media handling all differ between the two frameworks, and a translation that merely "looks right" can silently diverge from the original render. This Skill provides a structured lint-translate-validate workflow that produces a faithful HyperFrames HTML composition and measures fidelity against the Remotion baseline. ## Core Features & Use Cases - Source linting before translation: scripts/lint_source.py scans the Remotion project for blockers (useState/useReducer-driven animation, side-effect hooks, async calculateMetadata, third-party React UI libraries) and recommends the runtime interop pattern instead of producing broken HTML. - API mapping references: Topic references cover sequencing, timing/springs/easings, media, transitions, Lottie, fonts, and parameters, mapping each Remotion API to its HyperFrames HTML/GSAP equivalent. - 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: A user says "migrate my Remotion project to HyperFrames" — the Skill lints the source, translates the composition into an index.html with a paused GSAP timeline, renders both versions, and gates the result on SSIM thresholds while writing a TRANSLATION_NOTES.md for any lossy mappings. ## Quick Start Ask the assistant to port your existing Remotion composition source to HyperFrames and validate the result with the SSIM render diff.