From 1fb4caddff61cf06a5dfa5899662ec78fa3b96ae Mon Sep 17 00:00:00 2001 From: James Date: Fri, 1 May 2026 01:05:41 +0000 Subject: [PATCH] docs(remotion-skill): only trigger on explicit migration ask MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User feedback (jasonpurdy on X, https://x.com/jasonpurdy/status/2049985508701556855) flagged that the remotion-to-hyperframes skill auto-triggered during an A/B test of HyperFrames vs Remotion, producing a translated output instead of a native HyperFrames composition. The user preferred the native version once he disabled the skill. The previous SKILL.md description listed four triggering conditions, three of which were context-detection patterns (the user provides Remotion source, pastes a Remotion entry point, links a Remotion repo). Agents could interpret any of those as authoritative even when the user wasn't asking for a migration. Tighten the trigger gate so the skill only fires on an explicit migration verb (port, convert, migrate, translate, rewrite as HyperFrames). Add explicit NOT clauses for the common false-positive cases — including the specific A/B-test case (the same video as my Remotion one — treat as a fresh build). Default recommendation when uncertain: use the hyperframes skill instead. The body of the SKILL.md is unchanged — translation guidance is correct once the gate is passed; this only tightens the gate itself. --- skills/remotion-to-hyperframes/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/remotion-to-hyperframes/SKILL.md b/skills/remotion-to-hyperframes/SKILL.md index 9f43af4fc..4deea5518 100644 --- a/skills/remotion-to-hyperframes/SKILL.md +++ b/skills/remotion-to-hyperframes/SKILL.md @@ -1,6 +1,6 @@ --- name: remotion-to-hyperframes -description: Translate a Remotion (React-based) video composition into a HyperFrames HTML composition. Use when (1) the user provides Remotion source (`.tsx` files using `useCurrentFrame`, `Sequence`, `AbsoluteFill`, `interpolate`, `spring`, `staticFile`, etc.) and asks to port, convert, or migrate it to HyperFrames; (2) the user pastes a Remotion entry point (`Root.tsx`, `Composition`) 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", "rewrite as HTML", or "I have a Remotion comp, make it HyperFrames". Skill detects unsupported patterns (useState, useEffect with side effects, async calculateMetadata, third-party React component libraries, `@remotion/lambda` features) and recommends the runtime interop escape hatch instead of attempting a lossy translation. +description: Translate an existing Remotion (React-based) video composition into a HyperFrames HTML composition. Use ONLY when the user explicitly asks to port, convert, migrate, translate, or rewrite a Remotion composition as HyperFrames — for example "port my Remotion project to HyperFrames", "convert this Remotion code to HyperFrames", "migrate from Remotion", "translate this Remotion comp", or "rewrite this as HyperFrames HTML". Do NOT use when (a) the user is authoring a NEW HyperFrames composition, even if they have or are A/B-testing a similar Remotion video; (b) the user mentions Remotion in passing without asking for migration; (c) the user shares Remotion code as reference material rather than asking for a translation; (d) the user asks for "the same video as my Remotion one" without explicitly asking to migrate the source — treat that as a fresh HyperFrames build. When in doubt, default to authoring a native HyperFrames composition with the `hyperframes` skill instead. Skill detects unsupported patterns (useState, useEffect with side effects, async calculateMetadata, third-party React component libraries, `@remotion/lambda` features) and recommends the runtime interop escape hatch instead of attempting a lossy translation. --- # Remotion to HyperFrames