writing-fragments

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<what-to-do>
This is pure explore: widen the space of what could be written without committing to structure — committing is exploit, a separate skill's job. Run a grilling session that produces fragments, interviewing the user relentlessly about whatever they want to write about. Imposing phases, outlines, or article structure is out of scope here.
As fragments emerge from either side of the conversation, append them to a single markdown file.
If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.
Capture fragments from the very first thing the user says, including the initial prompt.
On first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.
</what-to-do> <supporting-info>
<what-to-do>
这纯粹是探索阶段:拓宽可写作内容的范围,无需承诺构建结构——构建结构属于“开发阶段”,是另一项技能的工作。开展一场“深挖式”对话,产出各种片段,持续询问用户关于他们想要写作的任何内容。在此阶段,强加阶段划分、大纲或文章结构均超出工作范围。
当对话双方产出片段时,将其追加到同一个markdown文件中。
如果用户未提供文件路径,询问一次保存位置,之后在整个会话中记住该路径。
从用户所说的第一件事(包括初始提示)开始捕捉片段。
首次写入时,在顶部添加一个仅包含暂定标题的一级标题(后续可修改),无其他内容——无元数据、无目录、无日期。
</what-to-do> <supporting-info>

What is a fragment

什么是片段

A fragment is any piece of text that might survive into the final article. It must be readable by the author — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is "is this a piece of good writing?", not "is this a self-contained argument?"
Fragments are deliberately heterogeneous. Examples of what could be a fragment:
  • A sharp sentence you'd want to deploy somewhere but don't yet know where.
  • A claim with a one-line justification.
  • A vignette: a thing that happened, a code snippet, a scenario, an analogy.
  • A half-thought: "something about how X feels like Y, work this out later."
  • A quote, a piece of dialogue, an overheard line.
  • A list of related observations that hang together by feel.
  • A complaint, a confession, a punchline.
  • A leading word — a compact metaphor or coinage the whole piece can hang on (one term that names the idea, the way tracer bullets or fog of war names a whole pattern).
Of these, the leading word is the most valuable fragment to land. It is load-bearing: name the right one in explore and it shapes the structure, the transitions, and the title later — paying dividends through the entire exploit phase. When the conversation circles a recurring idea, push to coin a word for it.
The novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.
片段是任何可能保留到最终文章中的文本内容。它必须能被作者理解——作者能明白其含义——但无需定义术语,也无需让陌生读者能理解。判断标准是“这是不是一段好文字?”,而非“这是不是一个自洽的论点?”
片段刻意保持多样性。以下是片段的示例:
  • 一句你想用到某处但暂未确定位置的犀利语句。
  • 带有一行理由支撑的主张。
  • 一个小场景:发生过的一件事、一段代码片段、一个情景、一个类比。
  • 一个半成型的想法:“关于X为何像Y的一些思考,之后再梳理清楚。”
  • 一句引语、一段对话、一句无意中听到的话。
  • 一组凭感觉关联在一起的观察结果。
  • 一句抱怨、一段自白、一个笑点。
  • 核心关键词——一个凝练的隐喻或新造词,可作为整篇文章的核心(就像“示踪弹”或“战争迷雾”这类术语可以概括一整套模式)。
其中,核心关键词是最有价值的片段。它具有支撑作用:在探索阶段确定合适的关键词,会在后续的开发阶段影响文章结构、过渡和标题——为整个开发阶段带来持续收益。当对话围绕某个反复出现的观点展开时,推动用户为其创造一个专属词汇。
小说家的日记是范本:多年无结构的观察记录,之后会被挖掘作为创作素材。片段就是这类观察记录。

File format

文件格式

markdown
undefined
markdown
undefined

Working title

Working title

A first fragment lives here.
It can be multiple paragraphs. It can include lists, code, quotes — whatever shape the fragment naturally takes.

A second fragment.

A quoted line that the user wants to keep around.
A reaction to it.

  • A cluster of related observations
  • That hang together by feel
  • And want to be near each other

Fragments are separated by a horizontal rule (`\n---\n`). No headings inside the body. No tags. No order beyond the order they were added.
A first fragment lives here.
It can be multiple paragraphs. It can include lists, code, quotes — whatever shape the fragment naturally takes.

A second fragment.

A quoted line that the user wants to keep around.
A reaction to it.

  • A cluster of related observations
  • That hang together by feel
  • And want to be near each other

片段之间用水平分隔线(`\n---\n`)分隔。正文内无标题,无标签,仅按添加顺序排列。

Writing rhythm

写作节奏

Append silently. Don't ask permission for each fragment. Mention what you added in passing ("adding that"), but don't interrupt the conversation with save dialogs.
Before every write: re-read the file from disk. The user may have edited, reordered, or deleted fragments between turns — preserve their changes. Never overwrite the file; only append (or, if the user asks, edit a specific fragment in place).
The user can say "cut the last one", "rewrite that one sharper", "merge those two" at any time. Treat those as first-class instructions.
</supporting-info>
静默追加片段。无需为每个片段询问许可。可以顺带提及“已添加该片段”,但不要用保存对话框打断对话。
每次写入前:重新读取磁盘中的文件。用户可能在对话间隙编辑、重新排序或删除了片段——保留这些修改。切勿覆盖文件;仅追加内容(或在用户要求时,原地编辑特定片段)。
用户可随时提出“删除最后一个片段”、“把那段改得更犀利”、“合并那两个片段”等要求。将这些视为优先级最高的指令。
</supporting-info>