ralphy-remotion

Redirect legacy Remotion references to HyperFrames render playbooks.

118|12|Updated May 5, 2026
One-click install
npx skills add https://github.com/alecs5am/ralphy --skill ralphy-remotion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralphy-remotion
Source: https://github.com/alecs5am/ralphy/tree/main/.agents/skills/ralphy-remotion
Command: npx skills add https://github.com/alecs5am/ralphy --skill ralphy-remotion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Compatibility shim for legacy Remotion references to redirect tasks to HyperFrames and current render playbooks, avoiding new Remotion code.

Core Features & Use Cases

  • Compatibility alias that redirects /ralphy-remotion references to HyperFrames.
  • Uses editor and HyperFrames playbooks for current render tasks.
  • Real-world use: when a user mentions "Ralphy Remotion" in a saved command or note, the agent follows HyperFrames workflow instead of writing Remotion code.

Quick Start

Tell the agent to treat legacy Remotion requests as HyperFrames tasks and follow the current playbooks for rendering.

Frequently Asked Questions about ralphy-remotion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy Remotion render tasks to a new workflow?

Redirect legacy Remotion references to HyperFrames by mapping saved commands and old project notes to current render playbooks, ensuring agents follow the modern workflow instead of generating deprecated Remotion code.

What is HyperFrames used for in video rendering automation?

HyperFrames functions as a modern render engine that executes video rendering playbooks, replacing deprecated Remotion workflows to maintain compatibility and automate rendering tasks.

Can I use my saved Remotion commands with a modern render engine?

Yes, references to Remotion in saved commands are intercepted and redirected to HyperFrames, allowing you to execute existing automation scripts through current render playbooks without manual rewriting.

Does the HyperFrames workflow require writing new Remotion code?

No, the HyperFrames workflow explicitly avoids writing new Remotion code by using a compatibility shim that routes legacy references directly to current render playbooks defined in AGENTS.md.

Why do my old Remotion project notes trigger the wrong render engine?

Old project notes mentioning Remotion trigger the wrong engine because they lack redirection; mapping these references to HyperFrames ensures the agent follows the current playbooks for final renders.

What are the limitations of using a compatibility shim for Remotion references?

The compatibility shim only redirects Remotion references to HyperFrames and does not execute Remotion code directly, meaning any rendering logic must be fully supported by the available HyperFrames render playbooks.