What problem does it solve? Porting a Remotion (React) video composition to HyperFrames by hand is error-prone: frame-based timing, spring physics, sequencing, and media handling all map differently in a seek-driven HTML model, and some React patterns (useState, useEffect, async metadata) 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 so the port is measurably faithful. ## Core Features & Use Cases - Source linting with blockers and warnings: scripts/lint_source.py detects useState, useReducer, useEffect with dependencies, async calculateMetadata, and third-party React UI libraries as blockers, recommending the runtime interop pattern from PR #214 instead of a broken translation. - Complete API mapping references: Topic references cover sequencing, timing (interpolate, spring, Easing), media (Audio, Video, Img, IFrame), transitions, Lottie, fonts, and Zod parameters, translating each Remotion idiom into HyperFrames data attributes and GSAP tweens. - SSIM validation harness: render_diff.sh and frame_strip.sh compare the Remotion baseline render against the HyperFrames output frame-by-frame, with calibrated per-tier thresholds (T1-T4) and a test corpus for regression checking. - Use Case: A user says "port my Remotion project to HyperFrames". The Skill lints the source, loads only the relevant mapping references, emits 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 like @remotion/lambda config. ## Quick Start Ask the agent to port your existing Remotion composition to HyperFrames by pointing it at your Remotion source directory and requesting the migration explicitly.