git:20260820.56c099a to v1.0.0

98 added, 117 removed. Audit A to A.

---

name: hyperframes

- description: Use when creating, editing, animating, or rendering video, motion graphics, promo videos, explainers, captions, slideshows, or HTML compositions with HyperFrames.

- metadata: { "tags": "video, animation, router, hyperframes, intent-routing" }

- ---

- # HyperFrames — start here

- HyperFrames renders video from HTML: a composition is an HTML file whose DOM declares timing with `data-*` attributes, whose animation runtime is seekable, and whose media playback is owned by the framework. The full authoring contract lives in `hyperframes-core/SKILL.md`; read it before writing composition HTML.

- Below: a **capability map** (the domain skills, loaded on demand) and the **intent router** (pick a workflow for any "make me a video" request).

- ## Capability map — the domain skills

- Atomic capabilities loaded on demand:

- | You want to… | Sub-Skill Path |

- |---|---|

- | **Author / edit an HTML composition** | `hyperframes-core/SKILL.md` |

- | **Animate** (GSAP, CSS, WAAPI, Three.js) | `hyperframes-animation/SKILL.md` |

- | **Author seek-safe keyframes & timelines** | `hyperframes-keyframes/SKILL.md` |

- | **Creative direction & palettes** | `hyperframes-creative/SKILL.md` |

- | **Audio & Media Engine** (TTS, BGM, SFX) | `hyperframes-media/SKILL.md` |

- | **Media resolve** (frozen BGM, SFX, images) | `media-use/SKILL.md` |

- | **CLI dev loop** (init, preview, render) | `hyperframes-cli/SKILL.md` |

- | **Install registry blocks** | `hyperframes-registry/SKILL.md` |

+ description: >-

+ Use when creating, editing, animating, rendering, inspecting, diagnosing, validating, previewing, publishing, or batch-rendering HyperFrames videos and projects. Triggers include promos, explainers, captions, title cards, overlays, slideshows, interactive decks, Remotion ports, Studio timelines, and mixes for placed audio.

+ author: HeyGen

+ coauthored: J StaR Films / Takomi

+ version: 1.0.0

---

- # Intent routing — pick a workflow

- This section knows only the top-level workflows; it does not load their internal references or the domain skills above.

- ## Before routing — confirm the input, not the spec

- Routing needs to know **what the video is about** — its input and subject. If that's unspecified ("make a video about our thing" with no URL, product, topic, or asset), ask before entering any workflow — committing to a workflow IS the routing decision. At most two questions:

- - **Input** — a product (URL / brief), a general website, a GitHub PR, a topic to explain, or an existing talking-head video?

- **Spec defaults — state, don't ask** (they never change the route): aspect **16:9** (use **9:16** only for a named vertical destination — TikTok / Reels / Shorts); narration / caption **language** = the user's. The chosen workflow re-confirms its own specifics at its first step.

- ## Workflow cheat-sheet

- | Workflow | Use it for |

- | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

- | `/product-launch-video` | **Selling a product** (SaaS, app, company / product site) — from a URL, brief, or script → a **promo**. The default for any commercial URL, even if the site is only named. |

- | `/website-to-video` | **Showing a site itself** — a tour / showcase built from the site's own screenshots. For non-commercial sites (portfolio, blog, docs, personal, event), or when the user wants a tour, not a promo. |

- | `/faceless-explainer` | **Explaining a topic / concept** from text — no product, no URL; every visual is LLM-invented |

- | `/pr-to-video` | A **GitHub PR / code change** → changelog / feature-reveal / fix / refactor explainer |

- | `/embedded-captions` | Adding **captions / subtitles** to an existing talking-head video (footage untouched) |

- | `/talking-head-recut` | Packaging an existing talking-head video with **designed graphic overlays** — lower-thirds, data callouts, kinetic titles, pull-quotes |

- | `/motion-graphics` | A short, **unnarrated, design-led motion graphic** — kinetic type, a stat / chart hit, a logo sting, a lower-third overlay |

- | `/music-to-video` | A **music track** → a **beat-synced** video — lyric video, slideshow, or kinetic promo; the music drives pacing (optional user images / videos cut onto the beat grid) |

- | `/slideshow` | A **presentation / pitch deck / interactive deck** — discrete slides, fragments, branching, hotspots; output is a navigable **deck**, not a rendered video |

- | `/general-video` | **Anything else** — longer or multi-scene pieces, a static loop / poster, a custom composition |

- | `/remotion-to-hyperframes` | **Porting an existing Remotion (React) composition** to HyperFrames (migration, not creation) |

- **Disambiguation (only where confusable):**

- - **Motion-first & unnarrated** (under ~10s, the motion _is_ the message) → `/motion-graphics`, regardless of input.

- - **A URL or script** — ask one thing: _is the site selling a product?_ **Yes** (SaaS / app / product / company site) → `/product-launch-video` — a promo, and the default for any commercial URL even if the site is only named. **No**, or the user just wants the site shown as-is (portfolio / blog / docs / personal / event) → `/website-to-video` — a tour. A GitHub PR link → `/pr-to-video`; a concept with no product or site → `/faceless-explainer`.

- - **Existing footage** — plain spoken-word subtitles → `/embedded-captions`; designed overlay cards → `/talking-head-recut`. Neither edits the footage itself (re-timing / recolor / reframe / reorder / audio is NLE editing — out of scope).

- - **A music track is the input** (an audio file, or a video to pull audio from) with **no narration** → `/music-to-video` — the music's beats/energy drive the pacing. (Narrated pieces stay with the input-matched workflow above; `/motion-graphics` is for short unnarrated motion that isn't music-driven.)

- - **A presentation / pitch deck / interactive deck** (discrete slides, navigation, presenter mode) → `/slideshow` — output is a navigable deck, not a rendered video. An explicit "slideshow" request proceeds directly; an adjacent trigger ("deck / slides / presentation / convert this page") makes `/slideshow` confirm it's a slideshow before authoring, and switch to the appropriate non-slideshow workflow if not.

- - **Length is a guide, not a gate** — intent picks the workflow; go to `/general-video` only when the piece is clearly longer than ~3 min, or is a static / loop / custom format.

+ **Plugin installs:** Before setup or freshness commands, follow [plugin execution rules](./references/plugin-installation.md) when this skill is inside a HyperFrames plugin. Standalone installs keep the update instructions below.

- ## If the matched workflow isn't installed

+ # HyperFrames entry point

- Once you've picked a workflow, check it's actually available to you. If the matched workflow skill isn't installed, don't fall back to guessing — tell the user to install it first:

+ HyperFrames **renders video from HTML** — a composition is an HTML file whose DOM declares timing with `data-*` attributes, whose animation runtime is seekable, and whose media playback is owned by the framework. The full authoring contract lives in `/hyperframes-core`; read it before writing composition HTML. Brief, storyboard, review, production, dispatch, and frame-worker contracts live in this skill's `references/`.

- - **Just this workflow:** `npx skills add heygen-com/hyperframes --skill <workflow-name>` (e.g. `--skill pr-to-video` — bare name, no leading `/`).

- - **All workflows at once:** `npx skills add heygen-com/hyperframes --all` (core + every workflow, skips the picker).

+ ## 1. Start from project state

- After they run it, re-read the workflow's skill and continue.

+ Apply the first matching row; do not evaluate lower state rows:

- ## Keeping skills current

+ | State | Action |

+ | ----------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

+ | Explicit port of existing Remotion source to HyperFrames | Read `references/routes/remotion-to-hyperframes.md`, then route directly to that workflow. Skip the intent layer. |

+ | Specific operation on an existing HyperFrames project: inspect, diagnose, validate, preview, render, publish, or batch-render | Perform only that operation. Skip intent and workflow routing; load `/hyperframes-cli` and any required domain skills. |

+ | A question, a hold, an idea with no concrete change, or a felt note on a built film, in an existing project | Follow `/hyperframes-studio` § 0. |

+ | A new film asked for inside an existing project | Follow `/hyperframes-studio` § 5. |

+ | Specific edit to an existing project | Make the edit. Do not run the intent layer. To know what is on a project's timeline (tracks, clips, starts, ends, what plays), run `npx hyperframes timeline [--json]` instead of reading `index.html` and every sub-composition file. |

+ | `BRIEF.md` exists | Read `workflow` and `flow`. Execute that workflow; `flow: companion` always executes in `/general-video`. Ask no brief questions. |

+ | No brief, but `hyperframes.json` or `STORYBOARD.md` exists | Resume from project files and recorded preferences. Infer the owning workflow from existing artifacts. If it cannot be determined uniquely, ask one routing-only question; do not run the intent interview. |

+ | Fresh creation | Run the intent layer — `references/intent-interview.md` — then route once using § 2's table. |

- HyperFrames skills are versioned. `npx hyperframes init` checks the installed skills against the latest on GitHub and installs/refreshes the **full** set whenever anything is out of date or missing — so a freshly init'd project always has the complete, latest set (and re-running init on an up-to-date project is a no-op). The check is a quick GitHub round-trip; offline (or rate-limited) it falls back to installing after a short timeout, so init never hard-fails on a network hiccup. The creation workflows scaffold with `init`, so starting a new project always runs this check and pulls our latest skills from GitHub when they're stale. The `--skip-skills` flag is currently neutered (a temporary measure while the skills.sh registry catches up): passing it no longer skips the check, so every `init` checks GitHub. CI/tests opt out via the `HYPERFRAMES_SKIP_SKILLS=1` env var.

+

- If a task is behaving unexpectedly, or before a long build, confirm the installed skills are current:

+ When you edit an existing project, bracket your edits with project history (`/hyperframes-cli`, Project history in your turn).

- - **Check:** `npx hyperframes skills check` (add `--json` for a machine-readable verdict; exits non-zero when anything is outdated **or missing**).

- - **Update:** `npx hyperframes skills update` — pulls the full set to the latest, **installing any not yet present** (same as init's install step).

+

- The CLI also surfaces a one-line reminder when a `render` / `lint` / `validate` run detects stale skills.

+ If a fresh request does not identify the subject or input, ask what the video is about before routing. Check preferences and recipes before asking anything (`references/intent-interview.md`, step 1). A `figma.com` input or a named recipe changes intake, not routing — the interview's "Adapt orthogonal inputs" section handles both.

- ## Workflow details

+ ### Keep the project's CLI current

- ### `/product-launch-video`

+ A scaffolded project pins `hyperframes@<version>` in its `package.json` scripts so renders stay reproducible; the pin never advances on its own, and a pinned run of an older CLI prints no warning about it. When resuming a project whose scripts carry a pin, probe once before the first render-affecting command:

- - **Input:** A product being marketed — **(a)** a product URL (crawled with headless Chrome for assets + brand tokens), **(b)** a script / brief that names the product's site even without a link (PLV resolves + crawls it, unless the user opts out), or **(c)** a script with no derivable site / "don't scrape" (no-capture mode — pick a style preset that supplies palette + design system). A supplied script can be the **verbatim** voice-over or **restructured** per scene — PLV asks.

- - **Output:** a product launch / SaaS **promo** as a HyperFrames composition → MP4 (sweet spot 30–90s) — the product's value is the subject, not a walkthrough of the site. For a plain tour of the site, use `/website-to-video`.

- - **Triggers:** "launch video for X", "promo for our site", "explain my SaaS in a minute", "turn my script into a 60s promo", "text-only launch video, don't scrape".

+ ```bash

+ npx hyperframes@latest upgrade --project . --check

+ ```

- ### `/website-to-video`

+ The probe is read-only and reports the pin against the latest release; keep the explicit `.` — on older CLI releases a bare `--project` followed by another flag consumes that flag as its directory value. When it reports the project behind — or any CLI output already shows it (the stderr notice `This project pins hyperframes@… (latest …)`, or `_meta.updateAvailable: true` in a `--json` result from a pinned script) — apply with `npx hyperframes@latest upgrade --project .`, then verify with `npx hyperframes check`. A passing check confirms the project's compositions still validate on the new version — not that rendered output is frame-identical to the old pin — so a successful bump is never silent: name the old and new version in the run's summary. A project with no composition yet needs no verification. If the check fails, revert the `package.json` change, continue on the pinned version, and report which version the project stays on and why. Act on the signal rather than relaying it to the user; never leave a bumped pin unverified.

- - **Input:** A website / URL whose goal is to show **the site itself**, not to sell a product. Best for non-commercial sites (portfolio, blog, docs, personal, event), or when the user explicitly wants a tour of a site as-is. Captured with headless Chrome for real screenshots + brand assets. If the site is selling something and the user wants a promo, use `/product-launch-video`.

- - **Output:** a site tour / showcase / social clip built from the site's own visuals → MP4.

- - **Triggers:** "turn this website into a video", "site tour from ", "social clip from our homepage", "I just have a URL — make something".

+ ## 2. Route fresh creation

- ### `/faceless-explainer`

+ Use the first matching row. Match the requested **deliverable**, not a word or file type mentioned in passing.

- - **Input:** Arbitrary text — a topic, article, or notes — being **explained**, with no product being marketed and no site to capture. (Forked from `/product-launch-video`; no headless Chrome.)

- - **Output:** faceless explainer → MP4, every visual LLM-invented per scene (typography / abstract / diagram / data-viz); ships the `pin-and-paper` preset. (sweet spot 30–90s).

- - **Triggers:** "faceless explainer about X", "explain how DNS works as a video", "turn this article into an explainer", "explainer from my notes".

+ | Priority | Request | Workflow |

+ | -------- | ------------------------------------------------------------------------------------------------------------------ | -------------------------- |

+ | 1 | Explicitly port an existing Remotion source | `/remotion-to-hyperframes` |

+ | 2 | Author a presentation, pitch deck, or navigable interactive deck | `/slideshow` |

+ | 3 | Add plain captions or subtitles to existing talking-head footage without changing it | `/embedded-captions` |

+ | 4 | Add designed graphic overlays to existing talking-head, interview, or podcast footage without changing the footage | `/talking-head-recut` |

+ | 5 | Build a beat-synced video from a music track, with no narration or website capture | `/music-to-video` |

+ | 6 | Create an explicitly short, unnarrated, motion-first unit, typically under 10s | `/motion-graphics` |

+ | 7 | Explain a GitHub pull request or code change from a PR reference | `/pr-to-video` |

+ | 8 | Market or showcase a website, product site, app, or company from a URL or site-specific brief | `/product-launch-video` |

+ | 9 | Explain a topic, article, or notes with invented visuals and no product or site capture | `/faceless-explainer` |

+ | 10 | Any other custom video or composition | `/general-video` |

- ### `/pr-to-video`

+ Before finalizing the route, read `references/routes/<workflow>.md` — one small file per route: the canonical input/output/trigger contract (available before lazy-installed workflow skills are present) plus that route's interview entry. If the candidate does not satisfy its contract, continue routing instead of forcing the match. Read only the matched route's file.

- - **Input:** A **GitHub pull request** — a PR URL, an `owner/repo#N` ref, or "this PR" — read via the `gh` CLI (not a site to scrape).

- - **Output:** code-change explainer (changelog / feature-reveal / fix / refactor) → MP4 — diff highlights, before/after, file-tree + impact scenes. ≤ (sweet spot 30–90s).

- - **Triggers:** "make a video about this PR", "turn PR #1187 into a changelog video", "release-notes video from github.com/org/repo/pull/123".

+ ### Resolve common ambiguities

- ### `/embedded-captions`

+ - A short animated title, logo sting, stat hit, chart hit, map hit, or standalone lower-third is `/motion-graphics` when it is unnarrated and motion is the message. A static title card, narrated sequence, longer montage, or custom loop is `/general-video`.

+ - An explicitly short motion graphic may use a URL, tweet, article, or screenshot as source material. A generic "make a video from this site" request is `/product-launch-video`.

+ - Existing footage with captions routes to `/embedded-captions`; footage with designed information cards routes to `/talking-head-recut`. Retiming, reordering, recoloring, reframing, or remixing footage is a custom edit and falls through to `/general-video`.

+ - A music file selects `/music-to-video` only when its beat grid drives the piece. Music used as a bed does not override the subject-matched route.

+ - "I want a storyboard" changes the review process, not the workflow. With no other routing signal, use `/general-video`. A confirmed sketched `storyboard.html` may itself be the requested deliverable; the review loop defines that stop point.

+ - Specialized narrative workflows support up to about 3 minutes and are strongest around 30–90s. Route a clearly longer piece to `/general-video`. Length never overrides an explicit port, deck, caption, overlay, or music-driven deliverable.

- - **Input:** An existing **talking-head video** (MP4) to caption — actual footage, not a URL or brief. Transcribed locally (Whisper, no API key) and matted (RVM) so the subject can occlude captions.

- - **Output:** the same footage **untouched**, with a caption layer — **Standard** (verbatim lower-third rail + an embedded climax behind the subject) or **Cinematic** (every caption composited behind the subject). Any length.

- - **Triggers:** "add captions / subtitles to this video", "captions behind the subject", "cinematic captions for my clip".

+ ## 3. Route once, then leave

- ### `/talking-head-recut`

+ For fresh creation the intent layer (`references/intent-interview.md`) runs the full conversation — memory, triage, pitch round, must-haves, run-shape, hand-off — and **ends by writing `BRIEF.md`. The brief is the only routing artifact the workflow reads**; nothing later re-opens this skill or the interview. Answer every later "what did the route require?" from `BRIEF.md`.

- - **Input:** An existing **talking-head / interview / podcast video** (MP4) to package with on-screen graphics — actual footage. Transcribed locally (Whisper). The clip plays in full underneath, untouched.

- - **Output:** the same footage with timed **graphic-overlay cards** — kinetic titles, lower-thirds, data callouts, pull-quotes, side panels, picture-in-picture — synced to the transcript. Any length.

- - **Triggers:** "package this video", "add graphic overlays / lower-thirds / data callouts to my talk", "turn this interview into a graphics-packaged edit".

+ ## 4. Install and enter the workflow

- ### `/motion-graphics`

+ Before reading the selected workflow, install or refresh it and the core domain skills:

- - **Input:** A short, design-led motion graphic where the **motion is the message** — typically under ~10s, no narration. Genres: kinetic typography, a stat / number count-up, a chart hit, a logo sting, a lower-third / overlay, or a search-driven page / tweet / headline shot.

- - **Output:** a short motion graphic → MP4 or a **transparent overlay** (alpha WebM / MOV) for a lower-third / callout.

- - **Triggers:** "an 8s logo sting", "animate this stat", "a kinetic-type intro", "turn this tweet into a motion graphic", "a transparent lower-third overlay".

+ ```bash

+ npx hyperframes skills update <workflow-name>

+ ```

- ### `/music-to-video`

+ Use the bare name without `/`. If the command fails, surface the error; do not reconstruct the workflow from memory. Everything else about installation — the core-vs-lazy split, what `init` refreshes, diagnosis, CI opt-out, and the no-CLI fallback — lives in `references/skill-lifecycle.md`.

- - **Input:** A **music track** — an audio file, or a video to pull the audio from — with **no narration and no website capture**. Optionally, user-supplied images / videos to weave in. The track is analyzed once into a deterministic beat / energy map (`audiomap.json`) the whole video is built on.

- - **Output:** a **beat-synced** HyperFrames composition → MP4 where the music drives pacing. Typography and templates are the floor (a complete video needs zero assets); any supplied media is cut onto the same beat grid (beat-cut / ken-burns). The genre — lyric video, slideshow, kinetic promo — emerges from the per-frame choices; the pipeline never branches on it.

- - **Triggers:** "make a video for this song", "beat-synced video from this track", "lyric video", "turn this music into a video", "music visualizer / kinetic promo to this beat".

+ ## 5. Load domain skills on demand

- ### `/slideshow`

+ | Need | Skill |

+ | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------ |

+ | Composition structure, timing attributes, tracks, variables, determinism | `/hyperframes-core` |

+ | Motion rules, scene blueprints, transitions, runtime adapters | `/hyperframes-animation` |

+ | Seek-safe GSAP, CSS, Anime.js, WAAPI, FLIP, paths, masks, SVG, 3D keyframes, or `hyperframes keyframes` diagnostics | `/hyperframes-keyframes` |

+ | Design specs, concept, palette, typography, narration, beat planning | `/hyperframes-creative` |

+ | Images, icons, logos, audio, captions, grades, LUTs, reusable media | `/media-use` |

+ | Voiceover carve, audio effect chains, automation envelopes, or one chain/fader across several tracks (submix bus) | `/hyperframes-audio` |

+ | Init, lint, check, snapshots, compare, batch render, Studio, render, publish, or diagnostics | `/hyperframes-cli` |

+ | Registry blocks and components | `/hyperframes-registry` |

+ | A named look, effect, treatment, or transition — CRT scanlines, glitch, film grain, shimmer sweep, confetti burst — BEFORE hand-building it | `/hyperframes-registry` |

+ | Figma assets, tokens, components, or storyboard frames as reconstructed motion | `/figma` |

- - **Input:** A **presentation / pitch deck / interactive deck** to author — a brief, an outline, or an existing page to convert to slides. Not a request for a rendered video; if the intent is ambiguous, the skill confirms "do you want this as a HyperFrames slideshow?" before authoring.

- - **Output:** a runnable HyperFrames composition + a **JSON island** the player's `SlideshowController` reads to turn the GSAP timeline into a navigable **deck** — discrete slides, fragment reveals, branching sequences, hotspot navigation, presenter mode, and speaker notes. The deliverable is a deck, not an MP4.

- - **Triggers:** "make a pitch deck / presentation / slide deck", "an interactive deck", "convert this page into slides", "a slideshow with presenter mode".

+ Creator edit phrases are cross-domain requests. Load every skill named in the matching row:

- ### `/general-video`

+ | Creator request | Required domains |

+ | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

+ | “cut this footage”, hard cut, trim, splice, reorder, or use a source range | `/general-video` + `/hyperframes-core`; core owns `data-start`, `data-duration`, `data-media-start`, and track layout. |

+ | zoom in here, punch-in / punch-out, smooth multi-state zoom or reframe, Ken Burns, or camera move | `/general-video` + `/hyperframes-core` + `/hyperframes-keyframes`; animate the inner visual/crop wrapper, not the timed clip. |

+ | match cut or whip pan camera transition | `/general-video` + `/hyperframes-animation` + `/hyperframes-keyframes` + `/hyperframes-registry`; search/install a transition primitive before hand-authoring. |

+ | fade, crossfade, track gain/volume, automation, duck/carve, audio effects, or one effect across several tracks | `/general-video` + `/hyperframes-core` + `/hyperframes-audio`; core places clips, audio mixes placed tracks — including a submix bus over a group of them. |

+ | picture and sound edits that combine cuts with camera motion or mixing | `/general-video` + `/hyperframes-core` + `/hyperframes-keyframes` when there is visual motion + `/hyperframes-audio` when sound is faded, mixed, ducked, automated, or processed. |

+ | lay out a project so it reads well in Studio: caption track, tracks per element kind, sub-compositions, safe zones | `/hyperframes-studio` + `/hyperframes-core`; studio owns the layout conventions, core owns each edit. |

+ | source or generate media, or preprocess an unsupported mid-source freeze | `/media-use`; sourcing/generation/preprocessing only, never placed-track mixing. |

- - **Input:** Anything not above — a creative brief, a single element to animate, an edit to a composition you're building. Input- and length-agnostic.

- - **Output:** a HyperFrames composition (any length / format) via the original flow: design system → prompt expansion → plan → layout-before-animation → build (delegating to the `hyperframes-`\* skills) → validate.

- - **Triggers:** "make a title card", "animate this", "a longer brand / sizzle reel", "a multi-scene composition", "a static loop / poster", any "make a video" that fits no row above.

+ Constant `data-playback-rate` is render-safe for picture and pitch-preserved

+ sound. Speed ramps are a `rate` lane in `data-automation`.

+ For copyable edit contracts, load `/hyperframes-core` → `references/creator-editing-recipes.md`.

- ### `/remotion-to-hyperframes`

+ Broad feedback about how photographic media looks or behaves also routes to

+ `/media-use`, even when the user never says “color grading” or “effect”: fix

+ dark/flat/boring footage, stylize a clip, hide a face, or improve a media

+ reveal. Read `./media-use/references/media-treatments.md` before editing a

+ treatment; it governs how footage is treated, never whether media may be used.

+ Do not substitute a generic LUT, CSS filter/overlay, or opacity tween for an

+ existing canonical treatment primitive. Keep text/layout/motion-only edits in

+ their owning domain.

+ During a build with important photographic media, include one grounded

+ media-polish scan in the final quality pass; leaving suitable media unchanged is

+ a valid result.

- - **Input:** An existing **Remotion** (React) composition's source — the user **explicitly** asks to port / convert / migrate it. One-way (Remotion → HyperFrames); not creation-from-input. A passing mention of Remotion is not a trigger.

- - **Output:** a HyperFrames HTML composition translated from the Remotion source, graded against the Remotion render (SSIM eval harness + tiered test corpus).

- - **Triggers:** "port my Remotion project to HyperFrames", "convert this Remotion comp", "migrate from Remotion".

+ Domain skills never take ownership of the end-to-end deliverable. Load only what the active workflow needs.