remotion-video-production

remotion-video-production

Compatibility alias for `video-production` when a prompt, setup surface, or legacy workflow explicitly asks for Remotion video production. Use when the request names Remotion, React-based video rendering, compositions, scene components, or a legacy `remotion-video-production` catalog entry, but the real workflow is still the canonical programmable-video lane. Prefer `video-production` for general use. Triggers on: remotion-video-production, Remotion render pipeline, React video composition, migrate old Remotion skill.

46Star
6Fork
更新于 2026/10/2
请求的译文尚未完成,当前显示原始英文。
SKILL.md
只读
名称
remotion-video-production
描述

Compatibility alias for `video-production` when a prompt, setup surface, or legacy workflow explicitly asks for Remotion video production. Use when the request names Remotion, React-based video rendering, compositions, scene components, or a legacy `remotion-video-production` catalog entry, but the real workflow is still the canonical programmable-video lane. Prefer `video-production` for general use. Triggers on: remotion-video-production, Remotion render pipeline, React video composition, migrate old Remotion skill.

Note: This skill is a compatibility wrapper for video-production. Use it when the environment still references the Remotion-specific name, but execute the same canonical programmable-video workflow with the code-first programmable video mode selected.

Remotion Video Production

Read references/alias-routing.md and references/remotion-route-outs.md before handling broad or ambiguous Remotion requests.

When to use this skill

  • A legacy prompt, installed catalog, or setup surface still calls remotion-video-production

  • The user explicitly names Remotion, React-based video composition, scenes, compositions, or rendering from code

  • The safest behavior is to preserve backward compatibility while steering future usage toward video-production

When not to use this skill

  • The user can already adopt video-production directly with no compatibility concern

  • The request is really template/API automation with no Remotion-specific stack need

  • The task is only manual finishing or editorial polish with no code-first render layer

Instructions