تشغيل أي مهارة في Manus بنقرة واحدة

remotion-to-hyperframes

النجوم١٠٩

التفرعات١٠

آخر تحديث١١ يونيو ٢٠٢٦ في ١٠:٣٦

Compatibility shim for the legacy `/remotion-to-hyperframes` skill name. Use when an old project, note, or user request asks to migrate Ralphy Remotion work; translate the intent into the current HyperFrames composition model and follow the editor and HyperFrames playbooks.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

alecs5am

alecs5am/ralphy

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

المهن الحاسوبية الأخرىمهن الحاسوب والرياضيات·SOC 15-1299

SKILL.md

readonly

name	remotion-to-hyperframes
namespace	user
description	Compatibility shim for the legacy `/remotion-to-hyperframes` skill name. Use when an old project, note, or user request asks to migrate Ralphy Remotion work; translate the intent into the current HyperFrames composition model and follow the editor and HyperFrames playbooks.

remotion-to-hyperframes

Trigger

Use this only when a request explicitly references legacy Remotion material, old Remotion files, or migration from Remotion to HyperFrames.

Hard invariants

HyperFrames HTML is the current source of truth for Ralphy video compositions.
Do not introduce new Remotion dependencies or render paths.
Preserve project artifacts append-only; snapshot existing HyperFrames index.html with ralphy hyperframes save-version <project> before non-trivial edits.

Workflow

Inventory the legacy request and map it to scenes, media tracks, captions, and transitions.
Read docs/playbooks/editor.md and docs/playbooks/hyperframes.md.
Implement or describe the migration in HyperFrames terms.
Render through ralphy render <project> when a final mp4 is requested.

Outputs

Deliver a HyperFrames migration plan, code change, or render result depending on the user request.

المزيد من هذا المستودع

نفس المستودع

social-publish

alecs5am/ralphy

Publish or schedule a finished Ralphy Unit through the active workspace's saved Postiz connection. Prepares the target-shaped title, description, body, CTA, hashtags, thread parts, and required Postiz settings, then calls `ralphy publish` and records provenance for later analytics. USE WHEN the user asks to "publish this", "post it now", "schedule this post", "send this to Telegram", "post this thread to X", "publish the reel", or "put this on YouTube/Instagram". DO NOT FIRE for copy-only requests with no posting intent; use social-copy instead.

2026-07-13109

dev-loop

alecs5am/ralphy

Run an autonomous, issue-driven development loop over Ralphy itself — the same cadence as a focused maintainer session: pick the open `notes/issues/`, order them by dependency, then for each issue dispatch a scoped sub-agent, review its diff, run the real gates, and commit + push to main before moving to the next. Sequential by default (one agent at a time) so changes never collide on shared files. Default scope is ALL open issues with a safety limit of 25; the user can widen the scope or raise the limit in their prompt. Pauses for the user only at genuine decision forks and before any paid generation or irreversible/outward-facing action. USE WHEN the user types `/dev-loop`, says "work through the issues", "run the dev loop", "grind the backlog", "implement all the open issues", "keep going through notes/issues until done", or after `/dev-issues` has filed a batch they now want executed. DO NOT FIRE for a single issue (just implement it), for content/video production, or when there are no open issues to exec

2026-07-13109

dev-publish-template

alecs5am/ralphy

Publish a finished Ralphy unit and its reusable blocks to the public library. Use when the user asks to publish a template, unit, style, recipe, or asset to the library. The CLI prepares the entity bundle; the sibling ralphy-web repository owns the committed library and upload script.

2026-07-13109

dev-release

alecs5am/ralphy

Cut a Ralphy CLI release across GitHub Releases, Homebrew, and npm. Use when the user asks to release, tag, publish, or prepare release notes for the CLI. Public documentation and the marketing site live in sibling repositories and are synchronized separately when their content is affected.

2026-07-13109

fixer

alecs5am/ralphy

The eval-to-repair loop — the consumer of the evaluator's report (#409). Reads the eval output (eval-deep-vision.json's `what_to_redo` first, else eval.json `findings[]`), runs `ralphy project repair-plan <id>` to classify every finding by owner (art-director / scenarist / editor) and order it by severity, presents the ordered plan grouped by owner, gets the user's approval, then applies targeted fixes through the EXISTING `ralphy` verbs (art-director regen / scenarist rewrite / editor recut), re-renders, re-evals, and compares the old vs new verdict. HARD GATE: no paid model regeneration runs until the user approves the plan (or previously opted into batch repair). The deterministic `repair-plan` step itself makes ZERO model calls and is safe to run unprompted. USE WHEN the user says "fix the eval", "repair this render", "make it shippable", "fix the issues / problems / findings", "address the eval", "now fix it", "make the fixes", or hands off a failed / warn eval and asks what's next. ALSO FIRE right after

2026-07-13109

templater

alecs5am/ralphy

The full extract → classify → blueprint → de-dup → publish pipeline for a finished `.ralphy/workspaces/<ws>/projects/<id>/`. Reads its `units/*/unit.json` (#069) as the Unit source of truth, then factors the project into ALL FIVE entities — Unit + the four typed blocks Template (structure), Style (look), Recipe (effect/treatment), Asset (reusable media). Applies the recipe-vs-tag split (#082/#083): a candidate is a Recipe only if it carries an extractable artifact (ffmpeg filtergraph / HyperFrames snippet / encode recipe / prompt technique); otherwise it is a Tag on the Unit. Captures a per-unit Blueprint (#080), de-dups every block against the live library FIRST, then prints the exact ordered `publish-entity.ts` commands (dry-run → --push). Publishing itself is the #056 path. USE WHEN the user says any of: "save this as a template", "turn the project into a template", "templatify <project-id>", "extract a template from <project>", "decompose this project into blocks", "what units/blocks did this project prod

2026-07-13109

name	remotion-to-hyperframes
namespace	user
description	Compatibility shim for the legacy `/remotion-to-hyperframes` skill name. Use when an old project, note, or user request asks to migrate Ralphy Remotion work; translate the intent into the current HyperFrames composition model and follow the editor and HyperFrames playbooks.

remotion-to-hyperframes

Trigger

Use this only when a request explicitly references legacy Remotion material, old Remotion files, or migration from Remotion to HyperFrames.

Hard invariants

HyperFrames HTML is the current source of truth for Ralphy video compositions.
Do not introduce new Remotion dependencies or render paths.
Preserve project artifacts append-only; snapshot existing HyperFrames index.html with ralphy hyperframes save-version <project> before non-trivial edits.

Workflow

Inventory the legacy request and map it to scenes, media tracks, captions, and transitions.
Read docs/playbooks/editor.md and docs/playbooks/hyperframes.md.
Implement or describe the migration in HyperFrames terms.
Render through ralphy render <project> when a final mp4 is requested.

Outputs

Deliver a HyperFrames migration plan, code change, or render result depending on the user request.