Agent skill · remotion-dev
studio-loop
Continuously improve Remotion Studio by making a video, reproducing real UX and performance issues, fixing them, and verifying the result. Use for ongoing Studio dogfooding and maintenance, including checkpoints that hand one PR over for review while work continues in a stacked PR.
What it needs
About 5k tokens when loaded.
What this skill does
Studio improvement loop Own the Studio experience: make it quick, responsive, and reliable. Continue making a real YouTube video combining NLE editing and motion graphics, using that workflow to discover and fix problems. Apply studio-dev to every implementation change. The Source start Inspector field was intentionally removed; do not reintroduce it. Resume the project and browser Recover the existing worktree, branch/PR or stack, local video project, running Studio, browser session, and handoff notes. Continue that project instead of starting another demo each iteration. Preserve unrelated changes and local QA assets; do not commit the video project or exports unless requested. Inspect Git state and setup instructions as needed, but use Studio before analyzing its implementation. Reuse a server only when its worktree and URL are known. Otherwise start Studio from packages/example with bunx remotion studio --no-open and use the URL it prints, rather than assuming port 3000 belongs to this checkout. Build/install dependencies if needed. Do not ask the user to unlock the Mac. Use an existing usable browser session, or launch a fresh headless Playwright browser for local Studio when desktop/browser UI access is unavailable. This workflow does not depend on the Mac being unlocked. Keep browser tooling separate from product changes. Exercise the real UI through clicks, keyboard input, drag/drop, file upload, and screenshots. Use actual registered WebMCP tools for state/readback and supported actions, and direct project edits where appropriate. Do not replace the UI pass with source inspection or mocked behavior. If browser execution fails, diagnose the headless setup and report any remaining verification gap; do not treat an automation failure as a Studio bug. If UI verification remains blocked, keep affected work in draft and report the gap instead of claiming a verified checkpoint. Continue independent work that does not depend on it. Work in a loop 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/studio-loop