What problem does it solve? Porting a Remotion (React-based) 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 some React patterns (useState, side effects, async metadata) cannot be translated at all. This Skill encodes the full API mapping, lints the source for untranslatable patterns, and validates the result with per-frame SSIM comparison so the translation is measurably correct. ## Core Features & Use Cases - Source linting with blocker detection: scripts/lint_source.py scans Remotion code for blockers (useState, useReducer, useEffect with deps, async calculateMetadata, third-party React UI libraries) and recommends the runtime interop pattern from PR #214 instead of a lossy translation. - Complete API mapping references: per-topic guides cover sequencing, timing (interpolate/spring/easing to GSAP), media, transitions, Lottie, fonts, and parameters, converting frame-based Remotion idioms into a paused GSAP timeline in a single HTML file. - SSIM-based validation harness: render_diff.sh and frame_strip.sh compare the Remotion baseline render against the HyperFrames output, with calibrated per-tier thresholds (T1–T3) and a frame-strip visual debugger for failures. - Use Case: A user says "port my Remotion project to HyperFrames" — the Skill lints the source, translates the composition into index.html with data-* attributes and a 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 migration.