visual-mode
/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.
- Author
- remotion-dev ↗
- Repository
- remotion ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Fields
- Browser Studio route tracking
SKILL.md preview
--- name: visual-mode description: 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. --- 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 ## Browser Studio route tracking Whenever adding a new Studio API route, also add it to the Browser Studio parity checklist in [issue #9807](https://github.com/remotion-dev/remotion/issues/9807). Do this in the same change, even if the route is intentionally server-only; place it in either the required Browser Studio operations or the explicitly unsupported routes.
Versions
The database has no other skills named visual-mode.
Database snapshot: 13.11.2026 · package version 2c59fabccf46 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100maui-hot-reload-diagnostics
Diagnose and troubleshoot .NET MAUI Hot Reload issues (C# Hot Reload, XAML Hot Reload, Blazor Hybrid). Covers all UI approaches (XAML, MauiReactor, C# Markup, Blazor Hybrid), Visual Studio, VS Code, environment variables, encoding requirements, and MetadataUpdateHandler. USE… - 87remotion-studio-zh
Open or preview Remotion Studio in Chinese alongside the official Remotion plugin. Apply when creating a project that will be previewed, starting an existing Studio, or reopening Studio after a Remotion upgrade. Not needed for render-only commands. - 100interactivity-best-practices
Best practices for writing Remotion animations that stay intuitive for coding agents and remain editable in Remotion Studio Visual Mode — keeping values literal and inline where the Studio can find them, rather than hidden behind indirection. Use when writing or refactoring a… - 100studio
Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally. - 100remotion
Best practices for Remotion video creation in React — compositions, sequences, animation, timing, and rendering. Use when building, reviewing, or debugging Remotion videos. - 100bun-hot-reloading
Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.