writing-fragments

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

<what-to-do>

Run a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope.

As fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved.

If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.

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.

The novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.

写作片段是任何可能保留到最终文章中的文本内容。它必须能被作者理解——作者清楚其含义即可——无需明确定义术语，也无需让陌生读者能看懂。判断标准是“这是否是一段优质的写作内容？”，而非“这是否是一个自洽的论点？”

写作片段刻意保持多样性。以下是写作片段的示例：

你想在某处使用但暂未确定位置的犀利语句。
附带一行理由的论点。
小场景：发生过的一件事、一段代码片段、一个场景、一个类比。
半成型想法：“关于X为何像Y的一些思考，之后再完善。”
引用、一段对话、无意中听到的话语。
一组因感觉相关而关联在一起的观察结果。
抱怨、自白、笑点。

小说家的日记是这类素材的典范：多年来无结构的观察记录，之后会被挖掘用作创作的原始素材。写作片段就是这类观察记录。

How the session feels

会话的氛围

Like a grilling session, with fragments as a by-product. The shape:

Start by asking what the user is circling around. Let them ramble.
Catch fragments from their words. When they say something quotable, capture it verbatim or slightly sharpened.
Generate candidate fragments back at them. Try things on. Offer two or three versions of the same idea and let them pick or reject.
When something lands, append it. When it doesn't, drop it.
Press for more. Excavate. "You said X — say it three different ways." "What's the version of that you wouldn't say in public?" "What's the example that made you believe this in the first place?"
Push on quality. The article will only be as good as its fragments. If a fragment is mushy, propose a sharper rewrite before appending.

Blue-sky generously, but apply pressure to deepen and tighten. Do not rush to outline. Do not group. Do not propose a structure. If the user starts asking about structure, redirect: "We're still mining. Structure comes later."

如同一场访谈式交流，写作片段是会话的副产品。流程如下：

首先询问用户正在构思的主题，让他们自由畅谈。
从他们的话语中捕捉写作片段。当他们说出值得引用的内容时，直接记录原文或稍作润色。
向用户提供候选写作片段。尝试不同表述，针对同一想法提供两到三个版本，让用户选择或拒绝。
当某个片段获得认可时，将其添加到文档中。若未被认可，则舍弃。
追问更多内容，深入挖掘。“你提到了X——用三种不同方式表述一下。”“如果是不会公开说的版本，会是什么样？”“是什么例子让你最初相信这个观点的？”
注重质量。文章的质量取决于其片段的质量。如果某个片段表述模糊，在添加前先提出更犀利的改写版本。

大胆畅想，但要施压以深化和精简内容。不要急于制定大纲，不要对片段进行分组，不要提出结构框架。如果用户开始询问结构相关问题，要引导他们回到当前任务：“我们仍在挖掘素材阶段，结构搭建是之后的事。”

File format

文件格式

markdown

undefined

markdown

undefined

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.

静默添加片段。无需为每个片段询问许可。可顺带提及你添加了什么（“正在添加这段内容”），但不要用保存提示打断对话。

每次写入前：从磁盘重新读取文件。用户可能在对话间隙编辑、重新排序或删除了某些片段——要保留这些更改。切勿覆盖文件；仅可添加内容（或在用户要求时，编辑指定的某个片段）。

用户可随时提出“删除最后一段”“把那段改得更犀利些”“把那两段合并”等要求。将这些视为优先级最高的指令。

Out of scope

不在范围内的事项

Outlines, section plans, paragraph structure, transitions.
Deciding the article's thesis, argument, or audience.
Producing prose that reads as finished writing.
Linking fragments together with connective tissue.

If the user is ready for any of that, the session is over and a different tool takes over. Do not name or recommend that tool — just stop.

</supporting-info>

大纲、章节规划、段落结构、过渡语句。
确定文章的主旨、论点或受众。
生成看起来已完成的散文内容。
用衔接内容将片段串联起来。

如果用户准备好进行上述任何一项工作，本次会话即结束，需使用其他工具。无需指明或推荐该工具——只需停止当前会话即可。

</supporting-info>