mcpField
S
studio-mode

studio-mode

github.com/remotion-devDevelopment68.6k188 installsUpdated today
Repository

About studio-mode

studio-mode documents the four operating modes of Remotion Studio and their capabilities. It guides developers in showing or disabling Studio actions according to server and environment availability.

Key features

  1. 01Describes four Studio modes
  2. 02Lists mode-specific capabilities
  3. 03Guidance for action availability

Use cases

  1. 01Adding a Studio action
  2. 02Adapting controls for read-only Studio
  3. 03Checking browser Studio limitations

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/remotion-dev/remotion --skill studio-mode

After installing, type/studio-modein Claude Code to confirm it loaded.

Details

From the project README

Studio Modes

Remotion Studio operates in four modes:

  1. Regular interactive Studio: Started with npx remotion studio. A Studio server is attached and the Studio is fully interactive. It can render server-side, use "Open in" actions, execute codemods, install packages, and perform other server-backed actions.
  2. Regular Studio with the preview server detached: previewServerConnected is false. The Studio is effectively read-only, although client-side rendering remains available.
  3. Read-only Studio: A deployed Studio with no server attached. Hide or disable actions that require a server. GitHub is the only supported "Open in" action.
  4. Browser Studio: Deployed at remotion.new and backed by a virtual file system that is hidden from the user. It cannot use "Open in" actions, but it can install dependencies and execute codemods.

When adding or changing a Studio action, determine which modes support it and hide or disable it everywhere else.

Comments

Markdown supported