写作片段
- 作者仓库星标 0
- 作者更新于 2026年8月24日 14:19
- 作者仓库 skills
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @mattpocock · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
<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 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.
## File format
```markdown
# 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.
## 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, so 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>
章节与文件索引
按说明文件中的顺序排列。
什么是片段
文件格式
写作节奏
文件/命令 -> \n---\n
内容校验值 -> 1616133c75b4
writing-fragments 是写作的「前 0 阶段」:跑一场无情的 grilling session,把对话两边浮现的 fragment 一条接一条 append 到一份 markdown 文件——不立大纲、不分阶段、不强求结构,那些都明确是 out of scope。
设计思路
作者借用小说家日记的模型:多年无组织的 noticings,将来被矿掘出来当原料。fragments 就是 noticings——是作者读得懂的小段,但不要求对冷读者自洽,标准是「这是不是一段好写作?」而非「这是不是一个完整论点?」。
什么是 fragment
文件格式
头部一个 H1 working title(可改),其下 fragment 用
---分隔,body 里不放 heading、不打 tag、不强制顺序——只按写下来的顺序排。工作流
① 没传 path 就问一次记下;② 第一次写时只放 H1 working title;③ 从用户第一句话起就开始捕捉 fragment(包括最初的 prompt 本身也算);④ session 中默默 append——不每次问要不要 append;用户在编辑这份文件,你写之前必须 re-read保留他改过的部分。
关键纪律
适合的场景
writing-shape或writing-beats用作原料grill-with-docs/grill-with-architecture)配合做 deep dive不适合
writing-shape或writing-beats配套
writing-shape/writing-beats(fragment 之后两条不同长成方式)、writing-skills(写作语调)、grill-with-docs(grilling 的另一种走法)、ubiquitous-language(fragment 里术语锚定)。