docs(remotion-skill): only trigger on explicit migration ask

[jrusso1020]

Summary

Tightens the remotion-to-hyperframes SKILL.md trigger so the skill only fires when the user explicitly asks to migrate / port / convert a Remotion composition to HyperFrames — not when they merely have or mention Remotion code.

Why

User feedback on X from @jasonpurdy:

I understand why you have the remotion migration skill, but I would encourage you to not have that on by default, it was basically the same video as remotion, I turned it off and like the native version more.

He was A/B-testing HyperFrames vs Remotion. The migration skill auto-triggered, produced a translated output (essentially the same video as his Remotion one), and only after disabling the skill did he get a native HyperFrames composition that he preferred.

The previous SKILL.md description listed four triggering conditions, three of which were context-detection patterns:

1. the user provides Remotion source (.tsx files using useCurrentFrame, Sequence, …) and asks to port
2. the user pastes a Remotion entry point and wants HTML
3. the user links a Remotion repo and asks for the HyperFrames equivalent
4. the user says "port my Remotion project", "translate this Remotion code", …

Conditions (1)-(3) gave agents enough latitude to fire the skill when the user shared Remotion code as reference material or A/B-test context, even if they hadn't actually asked for a migration. Condition (4) is the only explicit-ask gate.

Fix

• Remove the context-detection conditions; gate strictly on explicit migration verbs (port, convert, migrate, translate, rewrite as HyperFrames) plus concrete trigger-phrase examples.
• Add explicit NOT clauses for the common false-positive cases:
  • authoring a NEW HyperFrames composition (even with similar Remotion code in the user's history)
  • mentioning Remotion in passing
  • sharing Remotion code as reference material
  • the specific @JasonPurdy case: "the same video as my Remotion one" — treat as a fresh build, not a migration
• Default recommendation when uncertain: route to the hyperframes skill instead.

The body of the SKILL.md is unchanged — translation guidance is correct once the gate is passed; this PR only tightens the gate itself.

Distribution note

Per project_hyperframes_plugin_distribution.md, hyperframes-oss skills auto-propagate to Cursor + Claude Code (which consume this repo directly), but openai/plugins is a manual mirror that needs a sync PR after merge. Adding to my follow-up list.

Test plan

• SKILL.md frontmatter description updated; body unchanged
• bunx oxfmt --check skills/remotion-to-hyperframes/SKILL.md passes
• commitlint conventional-commit format passes
• After merge: sync to openai/plugins/plugins/hyperframes/skills/remotion-to-hyperframes/SKILL.md

— Rames Jusso