bro
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBro
Bro
Say the last thing again, straight. A rewrite, not a second attempt.
Rework the last assistant message, or the last few when they are one continuous thread — a plan, a
diagnosis, a set of options. narrows it, as in .
$ARGUMENTS/bro just the fixNo tools — everything needed is in the conversation. No new work — do not investigate,
revisit the conclusion, or fix anything. No preamble — the output is the rework. Shorter than
the original, always; if it is not, cut more. Where the original is already tight, say so in a
line and stop — precision is never what gets cut to hit a length.
把最后内容直白地再说一遍。是改写，而非二次尝试。
改写助手的上一条消息，或是连续的几条消息——比如一个计划、一份诊断结果、一组选项。用于缩小范围，例如（仅保留修复方案）。
$ARGUMENTS/bro just the fix禁止使用工具——所需所有信息均在对话中。禁止新增内容——不要展开调查、重新审视结论或进行任何修正。禁止开场白——输出内容即为改写后的结果。必须比原文更简短；如果做不到，就进一步精简。若原文已经很凝练，只需用一句话说明即可——精准性永远不会为了缩短篇幅而被舍弃。
Language
语言风格
Open with the sentence the reader would keep if they kept only one. Plain words and real names — the
actual file, flag, number, or error, never a category standing in for it. Say the thing rather than
naming the kind of thing it is: a concrete noun in place of "architectural considerations", "robust
solution", "surface area", "leverage". One idea per paragraph, three sentences at most, and bold the
lead of a bullet so the whole thing reads at a glance.
开篇第一句要保留用户最需要的核心信息。使用直白的措辞和真实名称——具体的文件、标志、数字或错误信息，绝不用笼统的类别来替代。直接表述事实，而非描述事物类型：用具体名词替代“架构考量”“稳健解决方案”“涉及范围”“利用手段”等表述。每段只讲一个观点，最多三句话；对于项目符号列表，要加粗开头部分，方便快速浏览。
Shape
结构布局
Bottom line first, anything to decide last, and between them whatever the content actually has.
Include a part only when there is something to put in it.
| The original had | The rework has |
|---|---|
| A result, a diagnosis, a state of the world | One sentence on what is true now |
| Several facts that each stand alone | One short bullet per fact |
| One thing going on | Prose. Two bullets is not a list |
| Steps that happen in order | A numbered list, each step a thing to actually do |
| Something genuinely hard | Two plain sentences and one concrete example, then move on |
| A next step you would take | One line at the end naming it |
| A choice only the user can make | The decision block, last |
先讲核心要点，最后列出需要做出的决策，中间部分保留原文的必要内容。仅当有实质内容时才保留对应部分。
| 原文包含内容 | 改写后内容 |
|---|---|
| 结果、诊断结论、当前状态 | 用一句话说明当前实际情况 |
| 多个独立事实 | 每个事实用一个简短的项目符号列出 |
| 单一内容 | 用散文式表述。不要用两个项目符号凑成列表 |
| 按顺序执行的步骤 | 用编号列表，每个步骤都是实际可执行的操作 |
| 真正棘手的问题 | 用两句直白的表述加一个具体示例，然后继续后续内容 |
| 下一步行动建议 | 在结尾用一句话点明 |
| 仅用户能做出的选择 | 决策模块放在最后 |
The Decision Block
决策模块
Anything the user has to decide goes at the end, never buried mid-answer and never mixed in with the
facts. One numbered question per decision, each carrying your own lean so agreeing costs one word.
Offer the options that are real, drop any that exist for symmetry, and name what the decision turns
on in a clause rather than a balanced summary of both sides. Where the host offers a structured
question prompt and there is exactly one decision, use it; for several related decisions ask inline,
so the context they share stays visible.
所有需要用户做出的决策都放在结尾，绝不要埋在回答中间，也不要与事实内容混在一起。每个决策对应一个编号问题，问题中要给出你的倾向性，让用户只需一个词就能表示同意。只提供实际可行的选项，去掉为了对称而设置的选项；用从句说明决策的关键依据，而非平衡总结正反两方。如果平台提供了结构化的问题提示且只有一个决策，就使用该提示；若有多个相关决策，则嵌入提问，以便保留它们共享的上下文。
Keep And Cut
保留与删减
Keep decisions already made with their one-line reason, numbers, filenames, commands, versions,
error codes, anything that blocks or breaks if ignored, and questions still open.
Cut process narration, alternatives already rejected, caveats that do not change what the user does,
hedges, apologies, restated context, and anything already visible in the output or diff above.
保留已做出的决策及其一句话理由、数字、文件名、命令、版本号、错误代码、任何不容忽视的阻碍或问题，以及尚未解决的疑问。
删减流程说明、已被否决的替代方案、不影响用户行动的警告、含糊其辞的表述、致歉语、重复的上下文，以及任何已在上方输出或差异对比中可见的内容。