Back to Details

re0

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
Refresh the target artifact as if it were the first clean version.
将目标工件刷新为仿佛是首次生成的干净v0版本。

Goal

目标

The result must be lighter, more current, and more accurate than the input. It should not read like a changelog, cleanup note, or patch over an older draft.
结果必须比输入更简洁、更贴合当前情况且更准确。它不应看起来像是变更日志、清理说明，或是对旧草稿的补丁。

Workflow

工作流程

  1. Identify the target artifact from the user's request or the active context.
  2. Read the target artifact end to end before editing.
  3. Check nearby artifacts that must stay aligned with it.
  4. Remove scaffolding residue, stale deltas, duplicated process noise, deprecated information, and over-specific history.
  5. Fold durable lessons into the place they should have lived from the start.
  6. Rewrite instead of appending when appending would preserve noise.
  7. Preserve the artifact's useful voice and structure; simplify everything else.
  8. Smooth prose noise: fold a parenthetical that interrupts a sentence or list into its own clause or cut it, keep a word or point repeated within reach of itself only once, and unwind padding that adds length but not meaning.
  9. Smooth source noise: unwrap a hard line break that splits a sentence mid-flow so each paragraph or list item lives on one source line, matching how sibling artifacts format theirs; make a plain-text pointer to a named section or file followable, a link where the medium supports one; leave code, tables, and quoted material as formatted.
  10. Re-read the result and cut again.
  1. 从用户请求或当前上下文确定目标工件。
  2. 在编辑前完整通读目标工件。
  3. 检查必须与目标工件保持一致的周边工件。
  4. 移除脚手架残留、过时的增量内容、重复的流程冗余信息、已废弃的内容以及过于具体的历史细节。
  5. 将经过验证的有效经验整合到原本就应该放置的位置。
  6. 若追加内容会保留冗余信息，则选择重写而非追加。
  7. 保留工件中有用的语气和结构；简化其他所有内容。
  8. 优化文本冗余：将打断句子或列表的插入语整合为独立分句或直接删除，同一范围内重复的词汇或要点仅保留一次，删除无意义的冗余修饰。
  9. 优化源文件格式冗余：修正中途拆分句子的硬换行，使每个段落或列表项位于单独的源文件行中，与同类工件的格式保持一致；将指向指定章节或文件的纯文本指针转换为可访问的形式，在支持的媒介中使用链接；保留代码、表格和引用内容的原有格式。
  10. 重新通读结果并再次精简。

Rules

规则

  • A pass that finds nothing to genuinely improve changes nothing.
  • Prefer editing existing sections over adding new ones.
  • Convert "what changed" into "what is true now".
  • Keep only details that improve future execution, accuracy, or recall.
  • Do not leave old/new traces unless the artifact is explicitly a changelog.
  • Fix machine-clear residue; surface judgment calls — never auto-resolve an ambiguity or "fix" a deliberate look-alike.
  • Repair from the source of truth — the canonical or sibling artifact, not the damaged surface — and mutate with edit-safety: assert the target exists (report a MISS, never a silent no-op), edit unicode-safe (
    PYTHONUTF8=1
    ), replace positional targets per occurrence rather than by blanket sweep, and script large structural moves.
  • Do not create extra files unless the user asks.
  • 若未发现真正需要改进的内容，则不做任何修改。
  • 优先编辑现有章节，而非添加新章节。
  • 将“已变更内容”转换为“当前真实内容”。
  • 仅保留有助于未来执行、准确性或记忆的细节。
  • 除非工件明确是变更日志，否则不得留下新旧内容的痕迹。
  • 修正机器可识别的残留问题；提出需要主观判断的问题——切勿自动解决歧义或“修正”故意设计的相似内容。
  • 从真实来源（标准工件或同类工件）进行修复，而非基于受损的表面内容；同时确保编辑安全：确认目标工件存在（报告缺失，切勿静默无操作），支持Unicode安全编辑（
    PYTHONUTF8=1
    ），按出现位置逐个替换目标内容而非全局替换，通过脚本执行大型结构调整。
  • 除非用户要求，否则不得创建额外文件。

Verification

验证

The result reads as a clean v0 to fresh eyes — no trace of the older draft, no sign it was patched rather than rewritten. If unsure, re-read it cold, as a stranger with no prior context would. Report what noise was removed and what durable truth was kept.
结果在新读者眼中应呈现为干净的v0版本——无旧草稿痕迹，无补丁修复的迹象。若不确定，请以无前置上下文的陌生人视角重新通读。报告已移除的冗余内容和保留的有效信息。