wtf
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesewtf
wtf
The user did not follow something. Explain it the way you would to a smart colleague who was not in the room.
Done: the user can say what the source means and what, if anything, they need to decide or do, without going back to the source.
用户没看懂某内容。请用你向不在场的聪明同事解释的方式来讲解。
完成标准： 用户无需回看原文，就能说清来源内容的含义，以及（若有的话）他们需要决定或执行的事项。
What to explain
解释对象
The text the user passed with the invocation decides the target:
- Nothing passed: your most recent message.
- A file path or a link: read it, then explain it.
- A pasted passage: that passage.
- A short pointer such as "the migration part" or "step 3": only that part of the conversation.
If the target is still unclear, ask one short question instead of guessing.
用户调用时附带的文本决定了解释目标：
- 未附带任何内容：解释你最近的一条消息。
- 文件路径或链接：先读取内容，再进行解释。
- 粘贴的段落：解释该段落。
- 简短指向（例如“迁移部分”或“第3步”）：仅解释对话中的对应部分。
如果目标仍不明确，不要猜测，只需提一个简短的问题。
How to explain
解释方式
- Open with the point in one or two sentences: what this says and why the user should care. Write no preamble and no apology for the earlier wording.
- Then say what it means for them: what happened, what state things are in, and anything they need to decide or do.
- Explain the source; do not rewrite it. The explanation is shorter than the source because it leaves out whatever the user does not need in order to understand it or act on it. Do not walk a document section by section.
- Use everyday words. When a technical term matters, keep it and say what it means once, in passing. Keep the exact file names, commands, and values the user will need to use.
- Keep everything that changes what the user would do: failures, caveats, open questions, and requests. The explanation must not sound more positive or more certain than the source.
- Add no claims the source does not make. If the source is vague or contradicts itself, say so. If re-reading your own message shows it was wrong, say that and correct it.
- Plain does not mean childish. Do not force analogies, cheerlead, or talk down.
- 开头用一两句话点明核心：内容讲了什么，以及用户为什么需要关注。不要写开场白，也不要为之前的措辞道歉。
- 接着说明对用户的意义：发生了什么、当前状态如何，以及他们需要决定或执行的任何事项。
- 是解释原文，而非重写原文。解释要比原文简短，省略用户理解或行动不需要的内容。不要逐节逐段地通读讲解文档。
- 使用日常用语。如果涉及重要的技术术语，保留术语并顺便解释一次含义。保留用户需要用到的准确文件名、命令和数值。
- 保留所有会影响用户行动的内容：故障、注意事项、待解决问题和需求。解释的语气不能比原文更积极或更肯定。
- 不要添加原文没有的主张。如果原文含糊不清或自相矛盾，直接说明。如果重读你自己的消息后发现内容有误，说明情况并纠正。
- 通俗易懂不代表幼稚化。不要强行使用类比、刻意打气或居高临下的语气。