cw-onboarding

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Onboarding

初始化引导

Create the smallest useful first version of the writer's durable voice and style guides. Help them start; do not make them finish an exhaustive profile before they can write.

创建写作者持久化语气与风格指南的最小可用初始版本。帮助他们快速上手，不要要求他们在开始写作前完成一份详尽的个人档案。

Load Existing Context First

优先加载现有上下文

Read

../../references/context-contract.md

. Inspect the current workspace for maintained identity, voice, preference, and project-style files before asking questions.

If authoritative context already exists, summarize it and ask only about genuine gaps.
If the user needs a writing-home folder, resolve the target and run
```
cw-setup-project
```
first so
```
VOICE.md
```
,
```
STYLE.md
```
,
```
examples/
```
, and
```
drafts/
```
exist together.
Do not auto-trigger because either guide is sparse or because a legacy
```
TASTE.md
```
is absent.
Do not duplicate global guidance into the writing home unless a local override is needed.
Do not overwrite an existing profile without explicit approval.

读取

../../references/context-contract.md

。在提问前，先检查当前工作区中已维护的身份、语气、偏好及项目风格相关文件。

如果已经存在权威上下文，先对其进行总结，仅针对真正的空白处提问。
如果用户需要一个写作空间文件夹，先确定目标路径并运行
```
cw-setup-project
```
，以便同时生成
```
VOICE.md
```
、
```
STYLE.md
```
、
```
examples/
```
和
```
drafts/
```
目录。
不要因为指南内容稀疏或者缺少旧版
```
TASTE.md
```
就自动触发初始化。
除非需要本地覆盖，否则不要将全局指引重复复制到写作空间中。
未经明确批准，不得覆盖现有档案。

Keep The Destinations Distinct

明确各指南的分工边界

Route each rule by what it governs:

```
VOICE.md
```
answers How should the sentences sound? Put syntax, diction, and tone here, including cadence, rhythm, register, punctuation, verbal tics, sentence moves, and phrases to favor or avoid.
```
STYLE.md
```
answers What must the article do, contain, and prove? Put argument, evidence, article structure, substantive standards, audience promise, openings, endings, formats, and publication-readiness criteria here.
Optional
```
AUDIENCE.md
```
answers Who are we writing for, and what may engage them? Put reader situations, prior knowledge, wants, interests, resistance, and source evidence here. Follow a maintained shared source named by the project; do not create a local duplicate.

Use this classification test:

A rule that changes wording, sentence construction, or tone belongs in
```
VOICE.md
```
.
A rule that changes the claim, support, organization, or readiness standard of the article belongs in
```
STYLE.md
```
.
Reader knowledge belongs in the governing
```
AUDIENCE.md
```
; the writing's obligations to that reader remain in
```
STYLE.md
```
. Split mixed feedback without duplicating it across guides.

Use the writing home's

VOICE.md

and

STYLE.md

as its portable context. Use an existing global voice guide when it is already the maintained authority. Tell the user where each class of guidance will live when the destination is not already obvious.

根据每条规则的管辖范围将其归类到对应指南：

```
VOICE.md
```
回答 句子听起来应该是什么样的？ 存放句法、措辞和语气相关内容，包括节奏、韵律、语域、标点、口头习惯、句式技巧，以及推荐使用或避免的短语。
```
STYLE.md
```
回答 文章必须做什么、包含什么、证明什么？ 存放论点、论据、文章结构、实质性标准、对受众的承诺、开头、结尾、格式，以及发布就绪标准相关内容。
可选的
```
AUDIENCE.md
```
回答 我们在为谁写作，什么内容能吸引他们？ 存放读者场景、已有知识、需求、兴趣、抵触点，以及来源证据相关内容。遵循项目指定的已维护共享来源，不要创建本地重复副本。

可使用以下分类判断标准：

会改变措辞、句子结构或语气的规则，归入
```
VOICE.md
```
。
会改变文章的主张、支撑论据、组织结构或就绪标准的规则，归入
```
STYLE.md
```
。
读者相关知识归入对应的
```
AUDIENCE.md
```
；写作对读者应尽的义务仍保留在
```
STYLE.md
```
中。拆分混合的反馈内容，不要在多个指南中重复。

将写作空间的

VOICE.md

和

STYLE.md

作为其可移植上下文。如果已有全局语气指南是维护中的权威版本，则直接使用该指南。如果指南的存放位置不明确，告知用户每类指引的存放位置。

Begin Or Refresh Audience Context

初始化或更新受众上下文

When the user requests audience setup or calibration, resolve the audience source through the context contract. Use an existing shared guide when named; otherwise create

AUDIENCE.md

in the established writing home if useful. The optional starter is

defaults/project-template/AUDIENCE.md

relative to the plugin root. Missing audience context never blocks the immediate writing task or triggers onboarding by itself.

Start with known situations, knowledge, interests, and resistance. Ask only consequential gaps. Label reader evidence, positioning, explicit writer intent, and editorial hypotheses; keep source, date, and scope. Do not invent a demographic profile, assume personal stakes, or turn a publication's intended relationship into measured reader behavior. The assignment can select a narrower reader without changing the shared guide.

Make the guide legible to both the writer and the agent: begin with a short reader portrait, distinguish wants (outcomes or experiences sought) from needs (what may help the reader get there), and connect them to what the writing can offer. Include a possible hero's journey when useful: starting situation, call, obstacles, guidance, trials, and what the reader carries back. Label it as an editorial model unless supported by reader evidence; do not force a transformation story or invent motives to fill its stages. Close with concise instructions for applying the guide to a piece, with sources and uncertainties easy to find.

当用户请求设置或校准受众时，通过上下文契约确定受众来源。如果指定了现有共享指南，则直接使用；如有必要，可在已建立的写作空间中创建

AUDIENCE.md

。可选的初始模板为插件根目录下的

defaults/project-template/AUDIENCE.md

。缺少受众上下文绝不会阻碍当前写作任务，也不会自动触发初始化流程。

从已知的场景、知识、兴趣和抵触点入手，仅针对重要的空白处提问。为读者证据、定位、明确的作者意图和编辑假设添加标签；保留来源、日期和范围信息。不要虚构人口统计档案，不要假设个人利害关系，也不要将出版物的预期关系等同于已验证的读者行为。具体写作任务可以选择更细分的读者群体，无需修改共享指南。

确保指南对写作者和Agent都清晰易懂：以简短的读者画像开头，区分期望（追求的结果或体验）和需求（帮助读者实现目标的要素），并将其与写作能提供的内容相关联。如有帮助，可加入可能的英雄之旅模型：初始处境、召唤、障碍、指引、考验，以及读者最终的收获。除非有读者证据支持，否则将其标记为编辑模型；不要强行套用转变故事，也不要虚构动机来填充各个阶段。最后附上将指南应用于具体文章的简洁说明，确保来源和不确定因素易于查找。

Interview

访谈调研

Ask only what the existing context does not answer. During first-run setup, ask one to three conversational questions at a time or invite the writer to share representative samples. Useful dimensions include:

syntax, diction, tone, sentence architecture, rhythm, and recurring line-level moves;
the writer's argument standards and recurring substantive moves;
evidence requirements, article structures, openings, endings, and publication-readiness criteria;
what the writer makes, for whom, and with what reader promise;
verbal tics, structural anti-patterns, and AI tells to avoid;
workflow preferences that materially affect the project.

Ask conversationally and follow the user's energy. Six fixed questions are not a requirement.

For a quick first version, capture a few high-signal rules in each guide and leave unknowns open. If the writer arrived with an immediate task, calibrate from that work where possible instead of pausing for a separate interview.

仅提问现有上下文无法回答的问题。首次设置时，每次提出1-3个对话式问题，或邀请写作者分享代表性作品样本。有用的调研维度包括：

句法、措辞、语气、句式结构、节奏，以及反复出现的句级技巧；
写作者的论点标准和反复出现的实质性写作手法；
论据要求、文章结构、开头、结尾，以及发布就绪标准；
写作者创作的内容、目标受众，以及对读者的承诺；
需要避免的口头习惯、结构性反模式和AI痕迹；
对项目有实质性影响的工作流偏好。

采用对话式提问，跟随用户的节奏。不要求必须问六个固定问题。

如果要快速生成初始版本，只需在每个指南中收录几条高价值规则，未知内容留空即可。如果写作者有即时的写作任务，尽可能基于该作品进行校准，不要暂停任务单独进行访谈。

Calibrating A Voice Profile From Examples

基于样本校准语气档案

When the writer supplies a fresh sample set or asks to refresh

VOICE.md

, make the deliverable a sentence-level vocal score, not a writing philosophy.

First, compare the examples for repeatable line-level behavior. Capture only patterns that recur across the sample set or that the writer explicitly confirms. Separate patterns that belong to a particular publication, assignment, or subject from portable voice guidance.

The resulting

VOICE.md

should normally cover:

the overall sentence-level sound in a few concrete sentences;
cadence and sentence-length variation;
syntax and recurring sentence turns, such as accumulation, qualification, correction, release, or fragments;
diction and register, including words, constructions, and generic phrasing to avoid;
punctuation, emphasis, and paragraph-level texture only when they affect sentence sound;
humor, self-awareness, or verbal tics when they are evidenced in the samples;
practical revision instructions that help an agent align a draft without imitating the examples.

Do not put curiosity, intellectual rigor, uncertainty, point of view, reader relationship, argument, evidence, structure, or publication standards in this profile unless the instruction changes the wording, syntax, cadence, or tone of a sentence. Route article standards to

STYLE.md

or the brief, and durable reader knowledge to the resolved

AUDIENCE.md

when one is maintained.

For every material voice rule, attach either a short sourced excerpt or a concise description of the observed move. Full examples belong in

examples/

; published language is directional and non-reusable. Avoid broad labels such as “warm,” “smart,” or “authentic” unless they are translated into observable writing behavior.

当写作者提供新的样本集或要求更新

VOICE.md

时，交付成果应为句级语气特征档案，而非空泛的写作理念。

首先，对比样本中可重复的句级行为。仅收录在样本集中反复出现或得到写作者明确确认的模式。将属于特定出版物、写作任务或主题的模式，与可移植的语气指引区分开。

最终生成的

VOICE.md

通常应包含：

用几句具体的话描述整体的句级听感；
节奏和句子长度的变化规律；
句法和反复出现的句式转折，比如递进、限定、修正、释放，或是碎片化表达；
措辞和语域，包括需要避免的词汇、结构和通用表述；
仅当标点、强调和段落质感会影响句子听感时，才将其纳入；
仅当样本中有证据支撑时，才纳入幽默感、自我意识或口头习惯；
实用的修改指引，帮助Agent在不照搬样本的前提下调整草稿以贴合语气。

不要将好奇心、思维严谨性、不确定性、观点、读者关系、论点、论据、结构或发布标准纳入该档案，除非相关指引会改变句子的措辞、句法、节奏或语气。将文章标准归入

STYLE.md

或写作brief，将持久化的读者知识归入已确定的

AUDIENCE.md

（如有维护）。

对于每条重要的语气规则，附上简短的来源摘录，或对所观察到的写作手法的简洁描述。完整样本存放在

examples/

目录中；已发布的内容仅作参考，不可复用。避免使用“温暖”“聪明”“真实”之类的宽泛标签，除非能将其转化为可观察的写作行为。

Write The Profile

撰写档案

Capture only specific, evidenced preferences.
Keep syntax, diction, and tone in
```
VOICE.md
```
; keep argument, evidence, article structure, substantive standards, and publication readiness in
```
STYLE.md
```
.
Phrase guidance as actionable rules, not personality adjectives alone.
Put full exemplars in
```
examples/
```
; use short excerpts in the guides only when they clarify a rule.
Mark published examples as directional and non-reusable.
When writing from examples, make rules operational: tell the agent how a sentence gathers, turns, qualifies, lands, or sounds false.
Include a concise revision checklist for preserving the writer's sentence-level sound without copying their phrases or inventing personal detail.
Show the proposed content before changing a high-authority or shared file when the governing rules require approval.

仅收录具体的、有证据支撑的偏好。
将句法、措辞和语气存放在
```
VOICE.md
```
中；将论点、论据、文章结构、实质性标准和发布就绪标准存放在
```
STYLE.md
```
中。
将指引表述为可执行的规则，而非单纯的性格形容词。
将完整范例存放在
```
examples/
```
目录中；仅当能阐明规则时，才在指南中使用简短摘录。
将已发布的范例标记为参考性、不可复用。
基于样本撰写规则时，要让规则具备可操作性：告诉Agent句子是如何铺陈、转折、限定、收尾的，或是怎样的表达会显得不自然。
加入一份简洁的修改清单，用于在不照搬写作者措辞或虚构个人细节的前提下，保留写作者的句级语气特点。
当管理规则要求审批时，在修改高权限或共享文件前，先展示拟修改的内容。

Migrate TASTE.md

迁移TASTE.md

When a legacy

TASTE.md

exists, classify its rules into

VOICE.md

STYLE.md

, and an authorized audience guide when useful. Flag mixed or conflicting rules for judgment. Do not keep adding new guidance to

TASTE.md

, and do not delete it without explicit approval.

如果存在旧版

TASTE.md

，可根据需要将其中的规则分类到

VOICE.md

、

STYLE.md

和经授权的受众指南中。标记混合或冲突的规则以供判断。不要再向

TASTE.md

中添加新的指引，未经明确批准也不要删除该文件。

Handoff

交接确认

Confirm:

what was captured in voice, style, and audience context when requested;
where the guides and supporting examples were saved, including any shared audience source;
which gaps remain intentionally open;
how future Compound Writing skills will load the writing home.

确认以下内容：

（如受众上下文有更新）已收录的语气、风格和受众上下文内容；
指南和支持性样本的保存位置，包括所有共享受众来源；
哪些空白处是有意保留的；
未来的Compound Writing技能将如何加载该写作空间。