Skip to content

🎥 Make videos programmatically with React

Skills: Shorten connected composition guidance

Jonny Burger5f5fef77256b
diff --git a/packages/skills/skills/remotion-interactivity/SKILL.md b/packages/skills/skills/remotion-interactivity/SKILL.md
index ef33e0912a..b52bf707de 100644
--- a/packages/skills/skills/remotion-interactivity/SKILL.md
+++ b/packages/skills/skills/remotion-interactivity/SKILL.md
@@ -141,11 +141,8 @@ animation as standalone compositions. Studio calls these **connected
compositions**: they can be opened in their own timeline while sharing the same
component implementation with the parent video.
-The component must work independently: define required styles such as
-`fontFamily` inside it and load its fonts without relying on the parent mounting.
-Do not depend on inherited parent styles, parent-only context providers, or
-parent mount side effects. Pass configurable values as explicit props with
-matching registration defaults. See
+Define required styles and load fonts inside the component so it works without
+its parent. See
[parent independence](../remotion-markup/connected-compositions.md#make-the-component-independent-of-its-parent).
Register the same exported component reference that the parent renders. For the
diff --git a/packages/skills/skills/remotion-markup/SKILL.md b/packages/skills/skills/remotion-markup/SKILL.md
index e091047ce9..315e6dbfb0 100644
--- a/packages/skills/skills/remotion-markup/SKILL.md
+++ b/packages/skills/skills/remotion-markup/SKILL.md
@@ -305,9 +305,8 @@ When a scene or group of layers deserves its own editable timeline, follow [conn
For a Studio request such as `Pre-compose Ambient glow (src/BarChart.tsx:134)`, find the selected sequence markup at the given location. Make a connected composition, following [connected-compositions.md](connected-compositions.md): extract the markup into a named component, preferably make it interactive with `Interactive.withSchema({wrapInSequence: true})`, and register the same exported component reference with a unique `<Composition>` in the root. Render the interactive component directly with its timing props, or as the only child of a sequence when that wrapper has a purpose. If the selected node is already a sequence, keep its props and extract its children. The registration needs dimensions, fps, duration, and `defaultProps` equivalent to its parent use. A component extraction without a registered composition does not complete a pre-compose request.
-Preserve required inherited styles, including `fontFamily`, inside the extracted
-component. Make its font loading and other dependencies independent of the
-parent, following [parent independence](connected-compositions.md#make-the-component-independent-of-its-parent).
+Carry inherited styles such as `fontFamily` and font loading into the extracted
+component; see [parent independence](connected-compositions.md#make-the-component-independent-of-its-parent).
## Voiceover
diff --git a/packages/skills/skills/remotion-markup/connected-compositions.md b/packages/skills/skills/remotion-markup/connected-compositions.md
index 9079e77969..bc6b8af910 100644
--- a/packages/skills/skills/remotion-markup/connected-compositions.md
+++ b/packages/skills/skills/remotion-markup/connected-compositions.md
@@ -16,26 +16,14 @@ Use connected composition when a section has its own layers or timing, will be r
## Make the component independent of its parent
-A connected composition must work when opened on its own. Its parent is not
-mounted in that view, so do not rely on inherited parent styles, context
-providers, or side effects that run only when the parent mounts.
-
-Set required inherited styles, such as `fontFamily`, `fontWeight`, `color`, and
-`lineHeight`, on the component's own root or text elements. For example, a
-parent's `<AbsoluteFill style={{fontFamily}}>...</AbsoluteFill>` does not supply
-the font when the child composition is opened separately.
-Load custom fonts in the component's module or a shared font module it imports;
-setting `fontFamily` alone does not load a font. See [Google fonts](google-fonts.md)
-and [local fonts](local-fonts.md).
-
-If appearance or data should vary per instance, pass it through explicit props
-and provide matching `defaultProps` on the standalone registration. When
-extracting existing markup, carry over the inherited styles and dependencies
-that it needs to preserve its appearance.
-
-Verify the connected composition by opening it directly in a fresh Studio
-preview before opening the parent. Check that its fonts and appearance match
-its intended parent use without depending on the parent having mounted first.
+The parent is not mounted when a connected composition opens on its own.
+Define required styles such as `fontFamily` inside the component, and avoid
+parent-only context providers or mount side effects. Load custom fonts in its
+module or a shared module it imports; see [Google fonts](google-fonts.md) and
+[local fonts](local-fonts.md).
+
+When extracting markup, carry over these dependencies. Verify its appearance
+by opening it directly in a fresh Studio preview before opening the parent.
## Example