Update to Remotion

{
  "description": "Structure Remotion markup for interactivity",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 320
    },
    {
      "relative_path": "assets/remotion-icon.svg",
      "size_in_bytes": 1303
    },
    {
      "relative_path": "inline-effects.md",
      "size_in_bytes": 993
    }
  ],
  "name": "remotion-interactivity",
  "skill_md_contents": "---\nname: remotion-interactivity\ndescription: Structure Remotion markup for interactivity\nversion: 4.0.534\n---\n\nBy writing Remotion markup in a specific way, the Remotion Studio is able to recognize the structure of the code and makes it interactive:\n\n- Allowing items to be selected by clicking on them\n- Allowing drag+drop, resizing and rotation\n- Editing the CSS styles\n- Making keyframes and easing values editable\n\nIf the markup is too complex for the Studio to make it interactive, then the values become grayed out.\n\n## Prefer interactive components with their own timelines\n\nUse `Interactive.withSchema({wrapInSequence: true})` for custom scenes, cards,\ntitles, and other visual components whose props should be editable per instance.\nExpose meaningful content and appearance controls in an `InteractivitySchema`.\nKeep decorative implementation details inside the component.\n\nThe component must accept `style` and forward it to one visual root. Keep a\nshared root when transforms, cropping, or opacity should affect all its layers.\nFlatten redundant inner wrappers when their styles can move onto an existing\nelement without changing layout or animation.\n\n```tsx title=\"LowerThird.tsx\"\nimport type React from 'react';\nimport {Interactive, type InteractivitySchema} from 'remotion';\n\ntype LowerThirdProps = {\n  readonly children: string;\n  readonly accentColor: string;\n  readonly style?: React.CSSProperties;\n};\n\nconst LowerThirdInner: React.FC<LowerThirdProps> = ({\n  children,\n  accentColor,\n  style,\n}) => {\n  return (\n    <Interactive.Div\n      style={{\n        position: 'absolute',\n        left: 80,\n        bottom: 80,\n        display: 'flex',\n        alignItems: 'center',\n        gap: 20,\n        backgroundColor: 'white',\n        borderRadius: 16,\n        padding: '20px 32px',\n        color: 'black',\n        fontFamily: 'Helvetica, Arial, sans-serif',\n        fontSize: 48,\n        fontWeight: 600,\n        ...style,\n      }}\n    >\n      <div\n        style={{\n          width: 8,\n          alignSelf: 'stretch',\n          borderRadius: 4,\n          backgroundColor: accentColor,\n        }}\n      />\n      {children}\n    </Interactive.Div>\n  );\n};\n\nconst lowerThirdSchema = {\n  children: {type: 'text-content', default: '', description: 'Text'},\n  accentColor: {\n    type: 'color',\n    default: '#0b84f3',\n    description: 'Accent color',\n  },\n} as const satisfies InteractivitySchema;\n\nexport const LowerThird = Interactive.withSchema({\n  Component: LowerThirdInner,\n  componentName: '<LowerThird>',\n  schema: lowerThirdSchema,\n  wrapInSequence: true,\n});\n```\n\nForwarding the injected `style` inside the component is required; keep editable\nstyles inline at the component's call site.\n\n### Choose schema fields\n\nEach key in the schema is a prop that Studio can read and edit at the call site.\nProps that are not in the schema still work, but are not editable in Studio.\nKeys may use dot notation, such as `style.color`.\n\n| Type                                                                         | Use for                                                      | Keyframable   |\n| ---------------------------------------------------------------------------- | ------------------------------------------------------------ | ------------- |\n| `text-content`                                                               | Text, such as a title                                        | No            |\n| `number`                                                                     | Numbers, with optional `min`, `max`, `step`, `integer`       | Yes           |\n| `boolean`                                                                    | On/off switches                                              | Yes (hold)    |\n| `color`                                                                      | CSS color strings                                            | Yes           |\n| `enum`                                                                       | A choice between `variants`, each with its own nested schema | Opt-in (hold) |\n| `array`                                                                      | Lists of numbers, colors, enums and more                     | No            |\n| `asset`                                                                      | Media sources, with optional `assetType`                     | No            |\n| `font-family`                                                                | CSS font family                                              | No            |\n| `font-weight`                                                                | Font weight                                                  | Yes           |\n| `translate`, `scale`, `rotation-css`, `rotation-degrees`, `transform-origin` | Transforms                                                   | Yes           |\n| `uv-coordinate`                                                              | A normalized `[x, y]` point on the element                   | Yes           |\n| `svg-path`                                                                   | SVG path data                                                | Yes           |\n| `remotion-captions`                                                          | `Caption[]` data                                             | No            |\n| `hidden`                                                                     | A value kept out of the controls                             | —             |\n\nEvery field needs a `default` and should have a `description`, which Studio shows as the label.\nSet `keyframable: false` to show a static control.\n\nExpose content and per-instance appearance, such as the text and an accent color.\nDo not add fields for `style.translate`, `style.scale`, `style.rotate`, `style.transformOrigin` and `style.opacity`: `wrapInSequence: true` already adds them.\n\nTo make CSS properties of the root editable per instance, spread the built-in schema fragments:\n\n```tsx\nconst cardSchema = {\n  ...Interactive.textSchema, // style.color, style.fontSize, style.fontWeight, ...\n  ...Interactive.backgroundSchema, // style.backgroundColor\n  ...Interactive.borderRadiusSchema, // style.borderRadius, ...\n} as const satisfies InteractivitySchema;\n```\n\nAlso available: `Interactive.borderSchema`, and `Interactive.captionsSchema` for components that accept captions.\nSee [`InteractivitySchema`](https://www.remotion.dev/docs/interactivity-schema) for all options.\n\n### Register reusable components as connected compositions\n\nRegister substantial scenes and reusable components with their own layers or\nanimation as standalone compositions. Studio calls these **connected\ncompositions**: they can be opened in their own timeline while sharing the same\ncomponent implementation with the parent video.\n\nDefine required styles and load fonts inside the component so it works without\nits parent. See\nparent independence.\n\nRegister the same exported component reference that the parent renders. For the\nexample above, use `component={LowerThird}`, not `LowerThirdInner` or an inline wrapper.\nWith `wrapInSequence: true`, no extra `<Sequence>` is needed for the connection.\n\n```tsx title=\"Root.tsx\"\nimport {Composition} from 'remotion';\nimport {LowerThird} from './LowerThird';\n\nexport const RemotionRoot = () => (\n  <Composition\n    id=\"LowerThird\"\n    component={LowerThird}\n    width={1280}\n    height={720}\n    fps={30}\n    durationInFrames={30}\n    defaultProps={{\n      children: 'Jane Doe, Product Designer',\n      accentColor: '#0b84f3',\n    }}\n  />\n);\n```\n\nChoose a unique ID, representative inline defaults, and dimensions, fps, and\nduration suitable for previewing the component. Registration defaults do not\nautomatically copy props from a parent instance. See\nconnected compositions for\nregistration and extraction details.\n\n### Put timing directly on the component\n\nAvoid a separate `<Sequence>` around one component that already accepts timing\nprops. Built-in interactive components and custom components made with\n`wrapInSequence: true` can receive `name`, `from`, `durationInFrames`,\n`trimBefore`, `playbackRate`, and `premountFor` directly.\n\n```tsx\n<LowerThird\n  name=\"Lower third\"\n  from={30}\n  durationInFrames={90}\n  accentColor=\"#0b84f3\"\n>\n  Jane Doe, Product Designer\n</LowerThird>\n```\n\nWhen removing a redundant sequence, move its timing and name to the child.\nPreserve any existing child timing; do not overwrite or double-apply offsets.\nA `useCurrentFrame()` call inside the component reads its local frame, while a\nstyle expression at the call site still uses the caller's frame. Preserve that\ndistinction when moving animation styles.\n\nKeep a `<Sequence>` when it provides shared timing for multiple siblings,\noverrides dimensions for `useVideoConfig()`, or wraps a component that does not\nhandle timing. Keep `<Series.Sequence>` for consecutive layout and\n`<TransitionSeries.Sequence>` for transitions; direct `from` props do not\nreplace those behaviors.\n\n## Give every independently editable item its own JSX node\n\nThe Studio edits the JSX source node that created an item. If multiple runtime\nitems come from the same JSX node, they share one source-editing target.\n\nFor every composition registration, clip, scene, layer or sequence that should\nbe editable on its own, write a separate JSX node and keep its editable props\non that node. This applies to `<Composition>`, `<Still>`, built-in media\ncomponents, `<Sequence>`, `<Series.Sequence>`, `<TransitionSeries.Sequence>`\nand custom components.\n\nFor example, author an editable timeline like this:\n\n```tsx title=\"Separate source nodes\"\n<Series>\n  <Series.Sequence name=\"Introduction\" durationInFrames={90}>\n    <Introduction />\n  </Series.Sequence>\n  <Series.Sequence name=\"Demo\" durationInFrames={150}>\n    <Demo />\n  </Series.Sequence>\n</Series>\n```\n\nA `.map()` or another programmatic loop would create multiple runtime items\nfrom one JSX source node. That is appropriate for repeated output that is\nintentionally controlled as one template, such as visualization bars or\nparticles. It is not appropriate when the instances need independent IDs or\nnames, props, metadata, timing, ordering, deletion or duplication in the\nStudio.\n\n## Make an HTML element interactive using `Interactive`\n\nEvery HTML and SVG element (except `<Img>`, it already is interactive) such as `<div>` can be turned interactive using `Interactive`:\n\n```tsx title=\"Interactive elements\"\n<Interactive.Div\n  name=\"Greeting card\"\n  style={{fontSize: 80, padding: 24}}\n>\n  Hello\n</Interactive.Div>\n```\n\nThis allows styles and keyframes to be set in the Studio. Be sensible, if a component has many elements, the timeline might get messy.\n\n## Prefer inline text\n\nIf text is fixed and only used once, write it directly inside the interactive element instead of extracting it into a constant.\n\n```tsx title=\"Inline text\"\n// 👍 Fixed copy stays editable\n<Interactive.Div name=\"Title\">\n  Remotion Best Practices\n</Interactive.Div>\n```\n\nUse a prop or variable only when the text is dynamic or reused.\n\n## Give interactive elements a descriptive name\n\nAdd a `name` prop to elements to make them easily identifyable.\nAvoid computed names, hardcode them.\n\n```tsx title=\"Interactive names\"\n<>\n  <Interactive.Div name=\"Hero title\" style={{fontSize: 80}}>\n    Launch day\n  </Interactive.Div>\n  <Img name=\"Avatar\" src=\"https://remotion.media/image.jpeg\" />\n  <Video name=\"Background\" src=\"https://remotion.media/video.mp4\" />\n  <Interactive.Div name=\"Title\">\n    Launch day\n  </Interactive.Div>\n</>\n```\n\n## Keep all CSS styles inline\n\nThe best way is to just pass a plain object to `style` - no referring to constants, no object spreading, no math.\n\n```tsx title=\"Interactive example\"\n<Interactive.Div\n  style={{\n    fontSize: 80,\n    color: 'red',\n  }}\n>\n  Hello World!\n</Interactive.Div>\n```\n\n```tsx title=\"❌ Bad for interactivity\"\nconst baseStyle = useMemo(() => {\n  return {\n    fontSize: 12 // ❌ Non-inline styles are not supported\n  }\n}, []);\n\n<Interactive.Div\n  style={{\n    ...baseStyle, // ❌ Spreading is not supported\n    color: RED, // ❌ Referring to constants is not supported\n    scale: frame * 10 // ❌ Math is not supported\n  }}\n>\n  Hello World!\n</Interactive.Div>\n```\n\n## Animate using `interpolate()`\n\nWrite animations as inline `interpolate()` calls on the property that changes.  \nThe output range, easing, extrapolation and `output` property should use hardcoded values.\n\nThe input range may additionally use `durationInFrames`, `fps`, `width` and `height` destructured directly from `useVideoConfig()`. Bare identifiers such as `durationInFrames`, multiplication with a number such as `2 * fps` or `fps * 2`, and subtraction of a number such as `durationInFrames - 1` are supported.\n\n```tsx title=\"Inline values\"\nconst {fps, durationInFrames} = useVideoConfig();\n\n// 👍 Inline values can be standardized and keyframed\n<Interactive.Div\n  name=\"Product card\"\n  style={{\n    color: 'white',\n    fontSize: 80,\n    scale: interpolate(frame, [0, fps], [0, 1], {\n      easing: Easing.spring({damping: 200}),\n      output: 'perceptual-scale',\n      extrapolateLeft: 'clamp',\n      extrapolateRight: 'clamp'\n    }),\n    rotate: interpolate(frame, [0, 1 * fps], ['0deg', '20deg'], {\n      easing: Easing.spring({damping: 200}),\n      extrapolateLeft: 'clamp',\n      extrapolateRight: 'clamp'\n    }),\n    translate: interpolate(\n      frame,\n      [durationInFrames - 30, durationInFrames],\n      ['0px 0px', '0px 120px'],\n      {\n        easing: Easing.spring({damping: 200}),\n        output: 'perceptual-scale',\n        extrapolateLeft: 'clamp',\n        extrapolateRight: 'clamp'\n      }\n    ),\n  }}\n/>\n```\n\n```tsx title=\"❌ Bad interactivity\"\nconst translateY = interpolate(frame, [0, 30], [0, 120]); // ❌ Math should be directly in the markup\n\n<Interactive.Div\n  name=\"Product card\"\n  style={{\n    translate: translateY, // ❌ Only inline interpolate() calls are supported,\n    rotate: interpolate(frame, [start, start + 10], [0, Math.PI]), // ❌ Cannot use math with arbitrary variables, cannot use constants\n    scale: interpolate(anyVariable, [0, 30], [0, 1]) // ❌ Can only interpret the `frame` variable.\n  }}\n/>\n```\n\n## Keep SVG paths editable with `Interactive.Path`\n\nUse `<Interactive.Path>` from `remotion` instead of `<path>` inside an SVG to make the path visually editable.\n\nInstall `@remotion/paths` for path interpolation and Studio path keyframes:\n\n```sh\nbunx remotion add @remotion/paths\n```\n\nIf the geometry is meant to be static, put the path string directly in the `d` prop. Do not extract it into a constant.\n\n```tsx title=\"Editable static path\"\nimport {Interactive} from 'remotion';\n\n<Interactive.Svg width={300} height={300} viewBox=\"0 0 300 300\">\n  <Interactive.Path\n    name=\"Triangle\"\n    d=\"M 40 40 L 260 40 L 150 260 Z\"\n    fill=\"#0b84f3\"\n  />\n</Interactive.Svg>\n```\n\n### Morph paths using inline `interpolatePaths()`\n\nUse `interpolatePaths()` from `@remotion/paths` directly in `d`.  \nIt accepts a frame, an input range, an equally sized array of path strings, and options for easing, extrapolation, and posterization.\nKeep the output paths, ranges, and options inline, following the same input-range rules as `interpolate()` above.  \nDo not use `interpolatePath()` API or extract the interpolated result into a variable when the path keyframes should remain editable in Studio.\n\n```tsx title=\"Editable path keyframes\"\nimport {interpolatePaths} from '@remotion/paths';\nimport {Easing, Interactive, useCurrentFrame} from 'remotion';\n\nexport const MorphingPath = () => {\n  const frame = useCurrentFrame();\n\n  return (\n    <Interactive.Svg width={300} height={300} viewBox=\"0 0 300 300\">\n      <Interactive.Path\n        name=\"Morphing triangle\"\n        d={interpolatePaths(\n          frame,\n          [0, 30, 60],\n          [\n            'M 40 40 L 260 40 L 150 260 Z',\n            'M 40 150 L 150 40 L 260 150 Z',\n            'M 40 260 L 150 40 L 260 260 Z',\n          ],\n          {\n            easing: Easing.bezier(0.42, 0, 0.58, 1),\n            extrapolateLeft: 'clamp',\n            extrapolateRight: 'clamp',\n          },\n        )}\n        fill=\"#0b84f3\"\n      />\n    </Interactive.Svg>\n  );\n};\n```\n\nStudio can edit the path at the current frame, add or move keyframes, and adjust their easing.  \nUse `strokeDasharray` and `strokeDashoffset` to evolve paths.\n\n## Use `scale`, `translate`, `rotate` CSS properties\n\nAvoid the `transform` CSS property.  \nIf possible, use `scale`, `rotate` and `translate` instead because only they are interactively editable.\n\n## Keep composition metadata inline\n\nWhen scaffolding a composition, use a JSX string literal for `id`, keep `width`, `height`, `fps`, `durationInFrames` and `defaultProps` inline and make no type assertions.\n\nThe Props editor can save visual edits back to your code when `defaultProps` is an inline object literal on `<Composition>` or `<Still>`.\n\n```tsx\n// 👍 Static values are in <Composition>, dynamic values are in calculateMetadata()\nconst calculateMetadata = useMemo(async () => {\n  const dimensions = await getDimensions(); // just an example\n  return {width: dimensions.width, height: dimensions.height};\n});\n\n<Composition\n  id=\"my-video\"\n  component={MyComponent}\n  durationInFrames={150}\n  fps={30}\n  calculateMetadata={calculateMetadata}\n  defaultProps={{title: 'Hello', color: '#0b84ff'}}\n/>\n```\n\n```tsx title=\"Negative examples\"\nconst defaultProps = {title: 'Hello', color: '#0b84ff'}; // ❌ Don't extract defaultProps, must be inline\nconst calculateMetadata = useMemo(() => {\n  // ❌ Unnecessary because no calculation is being done,\n  return {durationInFrames: 150, fps: 30, width: 1920, height: 1080};\n});\n\n<Composition\n  id=\"my-video\"\n  component={MyComponent}\n  calculateMetadata={calculateMetadata}\n  defaultProps={{\n    title: 'Hello',\n  } as Props} // ❌ Don't have type assertions, instead type MyComponent correctly\n/>\n```\n\nUse only `calculateMetadata()` for the part of the metadata that is dynamic.\n\n## Effects should be inline too\n\nKeep effect arrays and parameters inline so their shape and keyframes remain editable. See [Inline effects](./inline-effects.md) for examples.\n\n## Making your own component interactive\n\nTo make a custom userland component interactive, use:\n[Make a component interactive](https://www.remotion.dev/docs/studio/make-component-interactive.md)\n\n## Video editing\n\nIf a Remotion component mainly consists of video and audio clips, see Video editing for best practices on how to structure Remotion markup so the clips are interactively editable in the timeline.\n"
}