What problem does it solve? Migrating an existing Remotion (React) video composition to HyperFrames by hand is error-prone: frame-based timing, springs, sequences, and media props all need faithful translation into HTML plus paused GSAP timelines, and silent visual regressions are hard to catch without measurement. ## Core Features & Use Cases - Source linting with blockers and warnings: scripts/lint_source.py detects untranslatable patterns (useState, useEffect with deps, async calculateMetadata, third-party React UI libraries) and recommends the runtime interop pattern instead of producing broken output. - API mapping references: per-topic guides cover sequencing, timing/easing, media, transitions, Lottie, fonts, and parameters so each Remotion API gets a concrete HyperFrames equivalent. - Measured validation: render_diff.sh computes per-frame SSIM against a Remotion baseline, frame_strip.sh visualizes diverging frames, and a tiered test corpus (T1-T4) gates translation quality. - Use Case: A user says "port my Remotion project to HyperFrames" — the skill lints the source, translates scenes into sub-composition HTML files, renders both versions, and verifies the SSIM diff passes the tier threshold. ## Quick Start Ask the AI to port your Remotion composition to HyperFrames by pointing it at your Remotion source directory and requesting a migration.