studio-loop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Studio improvement loop

Studio 改进循环

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.
负责 Studio 体验:确保其快速、响应灵敏且可靠。持续制作一个结合 NLE 编辑与动态图形的真实 YouTube 视频,借助该工作流发现并修复问题。每次实现变更都要遵循 studio-dev。
Source start Inspector 字段是有意移除的;不要重新引入它。

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.
  • 恢复现有的 worktree、分支/PR 或 stack、本地视频项目、正在运行的 Studio、浏览器会话和交接说明。沿用该项目,不要每轮都启动新的演示项目。保留无关变更和本地 QA 素材;除非用户要求,否则不要提交视频项目或导出文件。
  • 根据需要检查 Git 状态和设置说明,但在分析其实现之前先使用 Studio。只有在 worktree 和 URL 明确已知时才复用服务器。否则,从
    packages/example
    启动 Studio,运行
    bunx remotion studio --no-open
    并使用其输出的 URL,不要假定端口 3000 属于当前 checkout。必要时构建或安装依赖。
  • 不要要求用户解锁 Mac。 使用现有的可用浏览器会话;如果无法访问桌面或浏览器 UI,则为本地 Studio 启动全新的无头 Playwright 浏览器。该工作流不依赖 Mac 已解锁。将浏览器工具与产品变更分开。
  • 通过点击、键盘输入、拖放、文件上传和截图操作真实 UI。对于状态读取和受支持的操作,使用实际注册的 WebMCP 工具;在适当情况下直接编辑项目。不要用源码检查或模拟行为替代 UI 验证。如果浏览器执行失败,应诊断无头环境并报告剩余的验证缺口;不要将自动化失败视为 Studio 缺陷。如果 UI 验证仍受阻,让受影响的工作保持 draft 状态并报告缺口,不要声称检查点已验证。继续推进不依赖该验证的独立工作。

Work in a loop

在循环中工作

  1. Continue an actual editing task. Prioritize common workflows: import and preview media, arrange/trim/split clips, edit text and transforms, add motion graphics and audio, scrub/play, undo/redo, save/reload, then render and review the exported video. Vary the next task based on what has already been covered.
  2. When an issue appears, capture a reproducible interaction and the expected result before inspecting the relevant implementation. Capture a relevant performance baseline before changing code. Look for slow feedback, missing optimistic paths, flicker, confusing copy/errors, layout mistakes, failed codemods, races, and unnecessary work. Check the persisted source and visible result rather than assuming a successful request means a correct edit.
  3. Fix the observed problem. Internal refactors are allowed, but keep the signatures of public APIs with non-experimental documentation stable. Follow Studio's existing design, optimistic/history paths, CSS reset, iframe hover handling, and mode capabilities. Code-editable actions already provide agentic access; do not add redundant WebMCP wrappers. Document any new tools or changed tool contracts as required by studio-dev.
  4. Repeat the original interaction in the rebuilt UI. Verify immediate feedback, persistence/HMR, relevant failure/navigation races, and undo/redo. Cover the applicable Studio modes, using a real Browser Studio iframe for changes that depend on embedding. Recheck neighboring common actions affected by the fix.
  5. Repeat the performance measurement with a comparable project, viewport, interaction, and playback state. Verify playback actually started; avoid concurrent builds/renders during measurements. Follow studio-perf and use react-scan when render/commit work is relevant. Resolve regressions, and report measurement limits rather than claiming broad coverage.
  6. Run affected existing checks and the verification required by pr. Follow writing-tests: do not add repository test cases unless explicitly requested. Temporary reproduction and profiling scripts may be kept outside the repository.
  7. Commit and push verified production changes to the active PR, keeping its title and description current. Keep using that PR across iterations until the user asks for a checkpoint or a different PR. Return to making the video and repeat; a successful fix or a progress report is not a request to stop the loop.
Delegate independent reproduction, review, or bounded implementation work when useful. Give each implementation owner separate files, and coordinate builds and browser sessions so they do not invalidate another measurement or edit.
  1. 继续一项真实的编辑任务。优先处理常见工作流:导入和预览媒体、排列、修剪或拆分片段、编辑文本和变换属性、添加动态图形和音频、拖动播放头或播放、撤销或重做、保存或重新加载,然后渲染并审查导出的视频。根据已经覆盖的内容调整下一项任务。
  2. 发现问题时,在检查相关实现之前,先记录可复现的交互操作和预期结果。修改代码前,记录相关的性能基线。留意反馈迟缓、缺少乐观更新路径、闪烁、令人困惑的文案或错误、布局错误、codemod 执行失败、竞态和不必要的工作。检查持久化后的源状态和可见结果,不要假定请求成功就意味着编辑正确。
  3. 修复观察到的问题。可以进行内部重构,但对于已有非实验性文档的公开 API,应保持其签名稳定。遵循 Studio 现有的设计、乐观更新与历史路径、CSS reset、iframe hover 处理和各模式的功能边界。可通过代码编辑的操作已经提供 agentic 访问能力;不要添加冗余的 WebMCP 包装器。按 studio-dev 的要求记录任何新工具或变更后的工具契约。
  4. 在重新构建的 UI 中重复原始交互。验证即时反馈、持久化/HMR、相关的失败或导航竞态以及撤销或重做。覆盖适用的 Studio 模式;对于依赖嵌入的变更,使用真实的 Browser Studio iframe。重新检查受修复影响的相邻常用操作。
  5. 使用可比的项目、视口、交互和播放状态,重复性能测量。验证播放确实已经启动;测量期间避免并发构建或渲染。遵循 studio-perf,并在涉及渲染或 commit 工作时使用 react-scan。解决回归问题,并报告测量限制,不要声称已获得广泛覆盖。
  6. 运行受影响的现有检查,以及 pr 要求的验证。遵循 writing-tests:除非明确要求,否则不要向仓库添加测试用例。临时复现和性能分析脚本可以保留在仓库之外。
  7. 将经过验证的生产代码变更提交并推送到当前 PR,保持其标题和描述及时更新。除非用户要求设置检查点或切换到其他 PR,否则持续使用该 PR。回到视频制作并重复循环;成功修复或进度报告并不代表要停止循环。
在适合时,将独立的复现、审查或有边界的实现工作委派出去。为每个实现负责人分配不同文件,并协调构建和浏览器会话,避免相互破坏测量或编辑。

Checkpoints and review

检查点与审查

Treat “checkpoint”, “let me review this PR”, or “stack the next batch” as a request to hand off a stable review boundary and continue working, unless the user also asks to pause or stop.
  1. Finish the current bounded fix and its verification. Do not expand the batch. Preserve unfinished or unrelated work for the next layer instead of including partial changes in the checkpoint. Stage only the intended production hunks, inspect the staged diff, and preserve excluded hunks even within the same file. Local QA dirt is not a reason to discard the project or delay the checkpoint.
  2. Commit/push the batch, update its PR description with behavior, validation, performance results and known limits, and mark the PR ready for review with
    gh pr ready
    if it is a draft. Share the PR link and exact checkpoint commit. Report pending/failing CI honestly; do not call it green before checks finish.
  3. Freeze that PR's scope for review. Follow gh-stack to adopt an existing branch if needed and create the next layer before making further changes. Base the new layer on the checkpoint branch so its PR shows only subsequent work. Open a draft PR when the next layer has verified changes, and keep that batch in the same PR until the next checkpoint. Without force-push authorization, publish with normal
    git push
    ,
    gh pr create
    /
    edit
    , and
    gh stack link
    using PR numbers; do not invoke stack commands that force-push.
  4. Continue the same video and improvement loop on the new layer while the user reviews the checkpoint. Do not keep appending unrelated progress to the PR under review. If review feedback changes a lower layer, apply it to its owning branch and update dependent layers using the stack workflow, preserving published history unless rewriting it was explicitly authorized.
  5. When the user merges a parent, verify its actual GitHub state and continue in the existing child PR. Preserve worktree changes before changing its base.
    gh stack sync
    rebases and pushes, and stack push/submit may force-push; do not use them to rewrite a published child without explicit authorization. The history-preserving path is to fetch and merge the updated trunk into the child, push normally, retarget its PR, and unstack/rebuild tracking for the remaining layers as needed. Check the resulting base and diff contain only remaining work, including after a squash merge. Do not merge PRs or force-push without explicit authorization.
A status question alone does not request a checkpoint. Answer it briefly and continue. A pause/stop request ends the active loop; record where to resume. Do not create a scheduled or background automation unless the user requests one.
将“checkpoint”、“让我审查这个 PR”或“堆叠下一批”视为移交一个稳定的审查边界并继续工作的请求,除非用户同时要求暂停或停止。
  1. 完成当前有边界的修复及其验证。不要扩大本批范围。将未完成或无关工作留给下一层,而不是将部分变更纳入检查点。只暂存预期的生产代码变更,检查暂存差异;即使在同一文件内,也要保留被排除的变更。本地 QA 残留变更不是丢弃项目或延迟检查点的理由。
  2. 提交并推送该批变更,用行为、验证结果、性能结果和已知限制更新其 PR 描述;如果该 PR 是 draft,则使用
    gh pr ready
    将其标记为可审查。分享 PR 链接和确切的检查点 commit。如实报告待处理或失败的 CI;检查完成前不要称其为 green。
  3. 冻结该 PR 的范围以供审查。遵循 gh-stack,在需要时沿用现有分支,并在进一步更改前创建下一层。以检查点分支作为新层的基础,使其 PR 只显示后续工作。当下一层包含已验证的变更时创建 draft PR,并将该批内容保留在同一 PR 中,直到下一个检查点。没有 force-push 授权时,使用普通的
    git push
    、
    gh pr create
    /
    edit
    和带 PR 编号的
    gh stack link
    发布变更;不要调用会 force-push 的 stack 命令。
  4. 用户审查检查点期间,在新层上继续同一个视频和改进循环。不要继续向正在审查的 PR 添加无关进展。如果审查意见需要修改较低层,则将其应用到对应的分支,并使用 stack 工作流更新依赖层;除非明确授权重写,否则保留已发布的历史。
  5. 用户合并父级 PR 时,核验其实际 GitHub 状态,并在现有子 PR 中继续工作。更改基线前保留 worktree 变更。
    gh stack sync
    会 rebase 并 push,而 stack push/submit 可能 force-push;未经明确授权,不要使用它们重写已发布的子 PR。保留历史的路径是:fetch 并将更新后的 trunk 合并到子分支,正常 push,重新设定其 PR 的目标分支,并按需 unstack/rebuild 剩余层的跟踪关系。检查最终基线和差异只包含剩余工作,包括 squash merge 之后的情况。未经明确授权,不要合并 PR 或 force-push。
仅询问状态并不表示要求创建检查点。简短回答后继续。暂停或停止请求会结束当前循环;记录恢复位置。除非用户要求,不要创建定时或后台自动化。

Keep continuity

保持连续性

Maintain a small local handoff outside the PR with the project and asset paths, worktree/branch/stack and PR links, checkpoint heads, server URL and launch command, browser connection details, reproduction steps, baseline/after evidence, tests, exports, known limits, and next useful editing task. Keep credentials and complete render request/environment payloads out of logs and handoffs. Resume from this record after context changes instead of rediscovering or repeating completed work.
在 PR 之外维护一份精简的本地交接记录,包含项目和素材路径、worktree/分支/stack 和 PR 链接、检查点 head、服务器 URL 和启动命令、浏览器连接详情、复现步骤、基线与改进后证据、测试、导出文件、已知限制,以及下一项有用的编辑任务。不要在日志和交接记录中保留凭据或完整的渲染请求/环境 payload。上下文变化后从该记录恢复,不要重新发现或重复已完成的工作。