Claude Fable 5.1 提示指南：16 条提示词建议 一份 Agent 运行时迁移清单

{
  "thinking": {
    "type": "adaptive",
    "display": "updates"
  },
  "betas": [
    "thinking-display-updates-2026-08-18"
  ]
}

English
Before starting, state in one sentence what you are about to do. During longer tasks, give brief updates on what you just found and what you are doing. End with a self-contained recap covering the findings, the work actually completed, and anything still outstanding.

Only you can see the full output of this command; the user interface shows at most a few lines. Put anything the user needs to read in your reply.

中文
开始工作前，用一句话说明你将要做什么。执行较长任务时，用简短更新说明刚刚发现了什么、正在做什么。结束时给出一份可以独立阅读的简要复盘，包括发现、实际完成的工作和仍需处理的事项。

这条命令的完整输出只有你能看到，用户界面最多显示其中几行。凡是用户需要阅读的信息，都必须写进你的回复。

English
First list privately what information you need next. Then request every independent item in this turn, leaving only genuinely dependent requests for a later turn.

中文
先在内部列出下一步需要取得的信息；然后在这一轮中一次性请求所有互不依赖的项目。只有确实依赖前一个结果的请求才留到下一轮。

{
  "role": "system",
  "content": "Batch independent calls.",
  "clear_at": "next_user_message"
}

English
Remove all mannered prose. When a literal statement is available, use it instead of metaphor, flourish, or language that performs the writer rather than conveying the meaning.

中文
删除所有矫饰性表达。能直接说明时就直接说明，不要用隐喻、漂亮话或写作者姿态替代准确含义。

English
Use lists, headings, or tables when the content has multiple parallel aspects, steps, or exact comparisons and the structure improves clarity. Use plain paragraphs for ordinary conversation, and follow explicit requests for minimal formatting.

中文
当内容包含多个并列方面、步骤或精确比较时，使用列表、标题或表格提高可读性。普通对话保持自然段；用户明确要求极简格式时，遵从该要求。

English
<example>
<user>Retrieve Source A and Source B on the same event and compare them.</user>
<response>State the facts both sources confirm in your own words, then compare what each emphasizes. Keep at most one necessary short phrase verbatim and mark it with quotation marks; paraphrase everything else.</response>
<rationale>The answer is organized around agreement and difference rather than walking through each article. Source views are reported indirectly, and the only verbatim phrase is clearly marked.</rationale>
</example>

中文
<example>
<user>检索来源 A 和来源 B 对同一事件的报道，并比较两者。</user>
<response>先用自己的话说明两者共同确认的事实，再比较各自强调的角度。只保留一个确有必要的短语原文，并明确加引号；其余内容全部转述。</response>
<rationale>回答按共同点与差异组织，没有逐篇复述；来源观点使用间接引语，唯一的原文短语有明确引号。</rationale>
</example>

English
You are operating autonomously. The user is not watching in real time and cannot answer repeated confirmations during execution. Proceed with every reversible step already authorized by the request and consistent with its intent. Stop only for destructive actions or genuine scope changes that require the user's decision.

Before ending, inspect your final paragraph. If it is still a plan, a question, a list of next steps, or a promise of unfinished work, keep using tools and complete the in-scope work. End only when the task is complete or blocked on information only the user can provide.

中文
你在自主执行任务。用户不会实时守在电脑前，不能回答执行途中的重复确认。凡是原请求已经授权、符合原意且可逆的步骤，直接执行；只有破坏性操作或必须由用户决定的真实范围变化才停下询问。

结束前检查最后一段：如果它仍是计划、问题、下一步清单，或承诺尚未完成的工作，就继续使用工具把范围内的工作做完。只有任务完成，或确实缺少只有用户才能提供的信息时，才结束本轮。

English
Create a summary that a new context window can use to continue the work. Preserve completely: (1) obstacles and how they were resolved; (2) approaches proposed, tried, or rejected and why; (3) the user's explicit preferences, constraints, decisions, and boundaries, keeping their wording where possible; (4) the exact current state and completed scope; (5) unresolved, promised, or required next work; and (6) hard-to-reconstruct details such as names, numbers, dates, exact wording, links, and code identifiers.

Prefer completeness over brevity for these items. Compress the assistant's explanations and reasoning to their conclusions and produced results.

中文
请生成一份可供新上下文继续执行的摘要。必须完整保留：
1. 已遇到的阻碍及处理结果；
2. 提出、尝试或否决过的方案及原因；
3. 用户明确提出或确定的偏好、限制、决定与边界，尽量保留原话；
4. 当前具体进展和已经完成的范围；
5. 仍未解决、已经承诺或下一步必须处理的事项；
6. 难以重建的精确细节，包括名称、数值、日期、原句、链接和代码标识符。

上述内容宁可写长也不要遗漏；助手自己的解释和推理只保留最终结论与产出。

English
Implement only the behavior explicitly required by this task. If you find an unrelated pre-existing bug, performance concern, cleanup opportunity, or extension, do not change it here; report it as a follow-up. Use the interpretation most directly supported by the request and surrounding code instead of implementing every possible reading.

Use scratch scripts and quick checks as needed, but do not automatically commit them as permanent tests. Add focused tests only when the task asks for them or the repository already keeps tests for this kind of change, sized like neighboring tests. Implement every requested behavior completely.

中文
只实现本任务明确要求的行为。如果发现与本任务无关的旧 Bug、性能问题、清理机会或功能扩展，不要在本次修改中处理；在最终总结中列为后续建议。采用最符合请求文字和现有代码的解释，不要同时为其他可能解释也构建一套实现。

可以使用临时脚本和快速检查验证工作，但不要自动把它们提交为永久测试。只有任务明确要求，或仓库已经为同类改动保留测试时，才按相邻测试文件的规模增加聚焦测试。必须完整实现请求中的全部行为。

English
When a query centers on a name you do not confidently recognize, or on a fast-moving area such as AI models, developer tools, prices, or current status, search before answering. Include the name exactly as the user wrote it in at least one query. Partial familiarity is not a reason to skip verification.

中文
当问题围绕你不能确信认识的名称，或来自数月内就可能变化的领域，例如 AI 模型、开发工具、价格和当前状态时，先检索再回答。至少一次搜索必须包含用户输入的名称原文。对名称有部分印象不是跳过搜索的理由。

English
Avoid: Does this program compile and run without errors?
Prefer: Are there any bugs in this program? Identify their locations and causes.

中文
不推荐：这段程序能否无错误地编译运行？
推荐：这段程序是否存在 Bug？请指出位置和原因。

English
Minimize the tokens used to edit files when doing so does not affect the result. Prefer surgical, targeted edits for small changes. Rewrite the whole file only when it is short or most of its contents must change.

中文
在不影响最终结果的前提下，尽量减少编辑文件所需的 token。小范围改动优先采用外科手术式的局部修改；只有文件很短或大部分内容都需要变化时，才重写整份文件。

English
Reasoning, drafting, and the final reply all count toward a total limit of about [max_tokens] tokens in this turn. Use reasoning to analyze inputs, verify dependencies, settle the structure, and resolve difficult decisions. Write the complete article, code, or table only once in the final reply. Do not draft the full deliverable in reasoning and then repeat it in the answer.

中文
本轮 reasoning、草稿和最终回复共同计入约 [max_tokens] token 的总上限。请在 reasoning 中分析输入、核对依据、确定结构并解决困难决策；完整文章、代码或表格只在最终回复中写一次。不要先在 reasoning 中全文起草，再在回复中重复一遍。