ketchup-video
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseKetchup video
Ketchup 视频
Follow , but show what happened in a short silent video instead of its summary and visuals. Its window starts at the last message the user wrote before , not before any earlier . Writing and rendering the video, outside the repo, is the one exception to its read-only rule. The reply is ketchup's opening sentence, the embedded video, one line naming any work left that you can do yourself, and the action items. When the video shows a call's options, call each option by the name the video gives it. If the render fails, say so in one line and give only the calls.
/ketchup/ketchup-video/ketchup按照 执行,但不要使用它的摘要和视觉素材,而是用一段简短的无声视频展示发生了什么。它的回溯窗口从用户在 之前发送的最后一条消息开始,而不是从更早的任何一个 开始。在 repo 外编写和渲染视频,是其只读规则的唯一例外。回复应包含 ketchup 的开场句、嵌入的视频、一行说明你还能自行完成的剩余工作,以及行动项。当视频展示某个 call 的选项时,按视频给出的名称逐一称呼每个选项。如果渲染失败,用一行说明,并且只给出 calls。
/ketchup/ketchup-video/ketchupSlides
幻灯片
Use the screenshots, recordings, diffs, and data the work produced, not the chat's prose about them. Before you draw, write the one sentence the user should leave with and one line per slide. Drop each slide that does not change what the user knows. Use at most 10 slides, and fewer is better. Neither note goes in the reply.
Each slide makes one point. Build the slides on one picture and change it from slide to slide, rather than cut to an unrelated one. A color or shape means the same thing on every slide. Show the work in pictures, such as how a system works, a PR stack with each PR's state, a before and after of a fix, or options side by side. Point at what changed with arrows, highlights, and motion. A slide is never a bullet list, a status list, a table, or boxes with nothing connecting them.
Keep text to the minimum. Put each label on the thing it names, in plain words a person would say, not tags like "Tests: pass". Never caption what a picture shows, and never give a fact twice, across slides or in the text under them.
Show what came of each thing the user asked for, and whether it is done, still running, failed, or not checked. Never show something done that still waits on the user. Show any bug found and fixed on the way. If a visible change has no screenshot, say so on its slide and name what changed on screen. Draw only from facts you have. Never invent a number, and never draw a screen you did not capture.
使用工作产生的截图、录屏、diff 和数据,而不是聊天中对它们的描述。在绘图前,写下用户最终应该记住的一句话,以及每张幻灯片的一行说明。删掉任何不会改变用户认知的幻灯片。最多使用 10 张幻灯片,越少越好。这两条备注都不放入回复中。
每张幻灯片只表达一个观点。所有幻灯片应基于同一张图片构建,并让图片在幻灯片之间发生变化,而不是切换到无关的图片。颜色或形状在所有幻灯片中的含义必须一致。用图片展示工作成果,例如系统如何运作、每个 PR 状态构成的 PR 栈、修复前后的对比,或并排展示的选项。用箭头、高亮和动态效果指出发生变化之处。幻灯片绝不能是项目符号列表、状态列表、表格,也不能是彼此之间没有任何连接关系的方框。
尽量减少文字。把每个标签放在它所命名的对象上,用普通人会说的平实词语,而不是“Tests: pass”之类的标签。绝不给图片已经呈现的内容添加说明文字,也绝不在幻灯片之间或幻灯片下方的文字中重复同一个事实。
展示用户提出的每项事情的结果,以及它已完成、仍在运行、失败还是尚未检查。绝不能把仍在等待用户处理的事项显示为已完成。展示过程中发现并修复的任何 bug。如果某项可见更改没有对应的截图,就在该幻灯片上说明这一点,并指出屏幕上发生的变化。只根据掌握的事实进行绘制。绝不编造数字,也绝不绘制未曾捕获的屏幕。
Render
渲染
Render one silent landscape video, such as an mp4, with motion between slides. Every frame is the slide itself, edge to edge. Make the frames from the slides, never by recording a screen. Hold each slide long enough to read its words, at least one second for each three words it adds. Words inside a screenshot do not count. Before you embed the video, look at one frame from each slide in the rendered file, and count the words it adds against its hold in that file. Fix any slide you cannot read in that time, render again, and check again.
渲染一段带幻灯片转场动效的无声横屏视频,例如 mp4。每一帧都应是幻灯片本身,并铺满画面边缘。必须根据幻灯片生成帧,绝不能通过录制屏幕来制作。让每张幻灯片保持足够长时间以便阅读新增文字;每新增三个词至少保持一秒。截图内部的文字不计入新增词数。在嵌入视频之前,查看渲染文件中每张幻灯片的一帧,并根据文件中的实际停留时间,核算该幻灯片新增的文字量。修复任何无法在规定时间内读完的幻灯片,再次渲染并重新检查。