MCPInstall

remotion-dev

Official106 skills · 3M installs · 4 repositories

  1. 1

    Router for all Remotion skills

  2. 2

    Export a Remotion video

  3. 3

    Create a new Remotion video

  4. 4

    Transcribing, displaying and animating captions

  5. 5

    Content, animation and effects best practices

  6. 6

    Structure Remotion markup for interactivity

  7. 7

    Build an app with Remotion

  8. 8

    Search Remotion documentation

  9. 9

    Upgrade Remotion, and related packages

  10. 10

    Interacting with Mediabunny

  11. 11

    Remotion Map animation knowledge

  12. 12

    Preview a Remotion video

  13. 13

    Multimedia handling with the Mediabunny library

  14. 14

    Add explicitly requested web renderer tests or update existing ones for implementation changes.

  15. 15

    Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.

  16. 16

    Generate a report about a video

  17. 17

    Add a new sound effect to @remotion/sfx

  18. 18

    Add an interactive demo to the Remotion documentation. Use when creating a new component for docs pages.

  19. 19

    Add a new expert to the Remotion experts page

  20. 20

    Open a pull request for the current feature

  21. 21

    Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing

  22. 22

    Review or correct a Remotion pull request title

  23. 23

    Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, formatting, and builds.

  24. 24

    Guidance for working on Remotion Studio Visual Mode, sequence identity, node paths, symbolicated stacks, override IDs, and hot reload behavior. Use when implementing or debugging visual editing of Sequences.

  25. 25

    The version of Remotion we are working on.

  26. 26

    Add a new Remotion CLI or config option by creating an AnyRemotionOption, registering CLI parsing, wiring config setters, and updating documentation. Use when adding or converting command-line flags or Remotion options.

  27. 27

    Add a new package to the Remotion monorepo, including package scaffolding, monorepo registration, documentation, build scripts, and release checklist updates. Use when creating a new @remotion package.

  28. 28

    Open a pull request for the current feature

  29. 29

    Update AvailableFrom in a PR to the next Remotion patch version (main + 0.0.1).

  30. 30

    Create, edit, or comment on Remotion GitHub issues.

  31. 31

    Resolve CI failures, merge conflicts, or local branch changes to get a PR ready

  32. 32

    Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.

  33. 33

    Track Remotion CI flakes in issue

  34. 34

    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.

  35. 35

    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.

  36. 36

    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.

  37. 37

    Release a new Remotion version

  38. 38

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

  39. 39

    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.

  40. 40

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

  41. 41

    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.

  42. 42

    Checkout a requested branch or ref in the Remotion repo, rename the current task to the associated PR title when running in Codex, then install dependencies and build. Use when the user asks to checkout a ref and prepare the workspace.

  43. 43

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

  44. 44

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

  45. 45

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

  46. 46

    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.

  47. 47

    Set up a Codex monitor for Vercel deployments and preview URLs. Use when the user invokes /vercel or $vercel, asks Codex to watch or monitor a Vercel deployment, waits for a Vercel preview or PR preview to become ready, or wants to be notified with both the deployment URL and preview URL once Vercel is READY.

  48. 48

    Use when rendering or replacing Remotion homepage creator strip videos, especially transparent Chrome WebM and Safari MP4 assets copied into both promo-pages and docs.

  49. 49
  50. 50