Remotion

Explains Remotion conventions for structuring React video components, managing timelines, and avoiding render bottlenecks. References common gotchas and performance wins.

Generates a test case for the web renderer with setup, assertions, and edge cases. Integrates with your existing test suite structure.

Helps structure and draft MDX documentation pages for an API or framework, ensuring consistency in tone, examples, and formatting across your docs site.

Watches a video file or transcript and produces a structured report: key points, timestamps, speaker breakdown, and actionable takeaways.

Scaffolds a Remotion <Demo> component with live code preview, editable parameters, and rendered output—ready to paste into a docs page.

Packages a new .wav or .mp3 and its metadata into the Remotion sound-effects library format, then opens a pull request to merge it upstream.

Adds your name, bio, portfolio link, and rates to the official Remotion experts page so clients can find and hire you directly.

Takes the current branch and commits, writes a clear PR description with context and change summary, then opens it against your main branch.

Generates folder structure, package.json, build config, test setup, and docs templates. Registers the package in your workspace and updates CI/CD and release checklists.

Scaffolds a complete effect—implementation, exports, tests, docs, and demo—then commits it to the Remotion library with previews and skill updates.

Creates parent–child and blocking relationships between GitHub issues using native issue links. Surfaces blockers and unblocks teams stuck waiting on upstream work.

Commits staged changes, generates a clear title and description based on the diff, and opens a PR without leaving Claude.

Takes your rough commit messages or change summary and suggests a PR title that says what changed and why — no jargon, scannable at a glance.

Reports the installed version of Remotion and flags if an upgrade or downgrade would resolve a known issue or unlock a feature.

Takes a title and description and posts a properly formatted GitHub issue with correct Remotion naming conventions and safe multiline Markdown that won't render weird.

Scaffolds the option definition, CLI parser, config setter, and doc update needed to add a flag to the Remotion CLI. Handles boilerplate so you focus on logic.

Takes a Dependabot security bump, updates every package.json instance across the monorepo, re-locks dependencies, and pushes a clean commit ready to merge.

Reads the current version on main, increments the patch by one, and updates the AvailableFrom field in your pull request automatically.

Reads a failing test, merge conflict, or lint error and outputs the exact code change needed — no guessing, no reruns.

Add a browser WebCodecs bug to the Remotion Mediabunny WebCodecs bugs docs page. Use when given a Chromium, WebKit, or Firefox issue URL that should be tracked in packages/docs/docs/mediabunny/webcodecs-bugs.mdx, especially when needing to look up the issue title, filing date, reporter, and resolution state before editing the MDX table.

Wait for a Remotion pull request to become mergeable, handle merge conflicts, distinguish genuine CI failures from flakes, rerun flaky checks through the flake skill, and merge the PR. Use when asked to run /merge, merge a current PR after checks pass, or shepherd a Remotion PR through CI to merge.

Track Remotion CI flakes in issue

'Fix newly added optional parameters, optional React props, and optional type/interface members in Remotion monorepo diffs by converting internal APIs to required nullable values and updating call sites. Use when a PR, review, or user asks to forbid new `foo?: T` / `param?: T` additions except for exported or documented public APIs where requiring the value would be breaking.'

Release a new Remotion version

Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs. Use when a file is too large for Git or when a PR should avoid committing media binaries by hosting them on remotion.media.

Upgrade Mediabunny and related @mediabunny packages across the Remotion repo. Use when asked to update Mediabunny to the latest version.

Add a new Remotion bug entry to packages/bugs/api/[v].ts. Use when the user describes a bug and affected Remotion versions that should be surfaced through the bugs API.

Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.

Upgrade the caniuse-lite override in the Remotion repo. Use when asked to update caniuse-lite to the latest npm version.

Run Remotion formatting and style checks until they pass. Use when the user asks to fix formatting or run the formatting command.

Update Remotion homepage GitHub star counts. Use when asked to refresh the displayed GitHub star count and push the change to main.

Checkout a requested branch or ref in the Remotion repo, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace.

Best practices for writing Remotion animations that stay intuitive for agents and editable in Remotion Studio Visual Mode.

Walks through Remotion Studio's visual mode, node paths, override IDs, and hot reload behavior to diagnose why your Sequence isn't editable or syncing as expected.