dexhunter/remotion · Archived

visual-mode

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.

First seen Jul 15, 2026

Installation

$ npx skills add dexhunter/remotion --skill visual-mode

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dexhunter/remotion · top by installs.

npx skills add dexhunter/remotion

Browse all from dexhunter/remotion

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Stars 1
License LICENSE.md
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,539 B
  • docs SUMMARY.md 226 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Visual Mode is a feature in Remotion Studio that allows one to visually edit Sequences.

I've made the following observations:

Fields

  • overrideId -> does keep the identity the same of a sequence, even if the file / line / column changes
  • Sequence stack -> changes on hot reload. shared by multiple sequences which have different overrideIds
  • Sequence file, line, column (symbolicated stack) -> does not change, but needs to be calculated asyn
  • nodePath -> same identity, even if line, stack and overrideId changes. async

nodePath + index is ideal way to keep track of the expanded state. that’s the end goal.

Once nodePath is mapped to overrideId, it doesn’t change otherwise component would remount and overrideId works change.

If the same stack is found already used by another sequence, we re-use the overrideId.

nodePath to symbolicated stack could theoretically change on every file change. but multiple sequences can share the same stack and then they all have the same nodePath.

We should only fetch the nodepath for every stack once

different unsymbolicated stacks could lead to the same symbolicated stack, because of fast refresh

unsymbolicated to symbolicated stack does never change because if it does, it is a different stack due to fast refresh