content-engine

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

content-engine: their voice, their facts, real craft

content-engine：创始人的口吻、真实事实、专业创作

Content fails two ways for founders: it sounds like everyone else, or it claims things the business cannot back. This engine runs on three inputs before any writing happens: the voice file, the vault, and distilled craft mechanics. What comes out sounds like the founder and survives fact-checking, or it does not ship.

  the content ask
        |
  [ voice ]     wiki/business/voice.md: register, moves, the never-list
        |
  [ facts ]     the vault: real lessons, real numbers, the positioning
        |
  [ craft ]     distilled mechanics: hooks, arcs, list growth, repurposing
        |
  [ check ]     voice drift? invented claims? then it ships

Before any step, read

${CLAUDE_SKILL_DIR}/../../CONVENTIONS.md

. This resolves from the installed skill directory to the plugin's shared contract, independent of the founder's working folder. Its receipts, filing, and dedupe rules govern this workflow.

对于创始人来说，内容失败通常有两种情况：要么听起来和其他人的内容千篇一律，要么声称企业无法兑现的内容。在开始创作之前，本系统需要三个输入项：Voice 文件、Vault（事实库），以及提炼后的创作技巧。最终产出的内容必须听起来像创始人本人的风格，并且能通过事实核查，否则不得发布。

  the content ask
        |
  [ voice ]     wiki/business/voice.md: register, moves, the never-list
        |
  [ facts ]     the vault: real lessons, real numbers, the positioning
        |
  [ craft ]     distilled mechanics: hooks, arcs, list growth, repurposing
        |
  [ check ]     voice drift? invented claims? then it ships

在执行任何步骤之前，请阅读

${CLAUDE_SKILL_DIR}/../../CONVENTIONS.md

。该文件从已安装的技能目录解析至插件的共享协议，与创始人的工作文件夹无关。其归档、存储和去重规则将指导本工作流。

Step 0: Load the three inputs

步骤0：加载三个输入项

Run the shared contract's Universal preflight. A Fresh, Partial, or Wrong-folder result routes to

/co-founder:co-founder-setup

(re-sync for Partial) and stops without drafting or filing.

The voice file (
```
wiki/business/voice.md
```
): register, words and moves, the never-list, the approved samples. Missing: stop and route to setup (or its re-sync) to create it, because writing without it produces the generic ghostwriter this skill exists to prevent.
The vault: the positioning and glossary from the charter, relevant learnings and research dossiers, the vision's direction. Content is generated FROM these canonical facts, never from generic knowledge about the founder's industry.
The channel scope from the charter (chosen at setup). This skill's v1 craft block covers writing/X/newsletter. A legacy charter scoped to another channel routes to setup re-sync to choose an installed writing format, then stops. Additional channel choices become valid only when their mechanics packs are installed; generic video advice from a writing skill is the exact slop this collection refuses to ship.

Done when: voice, facts, and scope are loaded, or setup owns the named repair.

执行共享协议中的通用预检流程。如果结果为“未完成（Fresh）”“部分完成（Partial）”或“错误文件夹（Wrong-folder）”，则跳转至

/co-founder:co-founder-setup

（部分完成时重新同步），并停止草拟或归档操作。

Voice 文件 (
```
wiki/business/voice.md
```
)：包含语域、措辞与行文风格、禁用列表、已核准的示例内容。如果缺失：停止流程并跳转至设置环节（或重新同步）以创建该文件，因为没有它生成的内容会变成本技能旨在避免的通用代笔风格。
Vault（事实库）：包含章程中的定位与术语表、相关经验与研究档案、愿景方向。内容必须基于这些标准事实生成，绝不能基于创始人所在行业的通用知识。
章程中指定的渠道范围（设置阶段选定）。本技能的v1创作模块涵盖写作/X/新闻通讯。如果旧版章程指定了其他渠道，则跳转至设置重新同步环节以选择已安装的写作格式，然后停止流程。只有当对应渠道的创作技巧包已安装时，该渠道选项才有效；本技能集坚决拒绝输出基于写作技能的通用视频建议这类低质量内容。

完成标志：已加载Voice文件、事实库和渠道范围，或已跳转至设置环节进行修复。

Step 1: Scope the piece

步骤1：明确内容定位

One question at a time, recommended answer attached: what is this piece FOR (the job: grow the list, warm the audience, sell the offer, bank authority), who exactly reads it, and what single idea carries it. A piece with two jobs gets split. Content serving an active initiative links to it; recurring content runs against whatever cadence is on record in the vault or the active initiative, and where none exists, one scoping question sets it.

Done when: job, reader, and the one idea are stated in a line each.

Before drafting the first version, apply the shared parameter gate to every number, story detail, outcome, and behavioral assertion the piece wants. Ask the founder for the exact claim or leave it out and record an unverified hypothesis in Claim checks. Plausible copy is not shown first and confirmed afterward.

Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or citing a receipt for it.

每次提出一个问题，并附上推荐答案：本次内容的目的是什么（目标：增长订阅列表、预热受众、推广产品、积累权威）、目标受众是谁、核心观点是什么。如果一个内容有两个目标，则拆分内容。服务于当前项目的内容需关联该项目；周期性内容需按照Vault或当前项目记录的节奏生成，如果没有记录节奏，则通过一个定位问题确定。

完成标志：分别用一句话明确内容目标、受众和核心观点。

在草拟第一版内容之前，对内容中涉及的所有数字、故事细节、成果和行为断言应用共享参数校验。向创始人确认确切的表述，否则将其移除并在“断言核查”中记录未验证的假设。绝不能先展示看似合理的内容再事后确认。

先询问再断言：在散文中提及数量、时长、样本量、日期或因果动机之前，必须先向创始人确认或引用相关凭证。

Step 2: Write with the craft block

步骤2：运用创作模块进行写作

STOP. Read

references/content-heuristics.md

now: hooks, structure and arcs, list growth, email mechanics, and repurposing moves, each with its trap. They are distilled from operators who publish at scale, and they are the difference between craft and vibes.

The writing rules that outrank everything in the craft block:

Voice first. Every line passes the voice file: its register, its moves, nothing from its never-list. The approved samples are the calibration set; when a draft would not sit naturally beside them, the draft is wrong.
Facts from the vault, receipts on claims. A number, a result, or a story about this business traces to a vault file; a claim about the outside world traces to checked research. A public call-to-action that recommends a consequential business move clears both receipt legs or stays out of the public body and is recorded in the draft's
```
Parked recommendations
```
section as
```
PARKED: internal receipt missing
```
or
```
PARKED: external receipt missing
```
, with the recall/research action. It never vanishes silently. Inventing a statistic for a founder's public post is the worst possible version of slop: it ships under THEIR name. No receipt: the claim comes out or gets researched.
Admission before prose. Run the shared durable claim admission gate before a claim enters either the draft or its receipts section. Reopen the source, quote the exact supporting line, and verify subject plus unit: a client count cannot become a personal-post count or proof of a client outcome. Recompute derived claims from named inputs. Founder recollections stay
```
Founder-stated: unverified
```
until checked; do not turn them into confident hooks first.
Biographical claims are receipt-only. Never assert a first-person fact about the founder: a duration ("for years", "two years"), a count ("four hundred posts"), a history ("I have always"), or a habit, unless those exact words appear verbatim in a
```
raw/
```
file or the live transcript. A client count is not a personal-post count; a metric is not a biography. If the vault does not contain the founder's own statement of the fact, the line comes out or is asked; the model never infers a biographical detail and then finds a receipt for the inference. This is the single bug that shipped the worst harm in three consecutive rounds, and it is a hard rule.
The glossary holds. Content uses the founder's canonical terms; drift gets flagged and fixed before the draft lands, in whichever direction (the draft or the glossary) was wrong.

Done when: a draft exists that passes voice, receipts, and glossary in your own read.

暂停。立即阅读

references/content-heuristics.md

：其中包含钩子、结构与叙事弧、订阅列表增长、邮件创作技巧、内容复用方法，以及每种方法的陷阱。这些内容均提炼自大规模发布内容的运营者经验，是专业创作与随意创作的区别所在。

创作模块中优先级最高的写作规则：

口吻优先。每一行内容都必须符合Voice文件的要求：语域、行文风格，不得包含禁用列表中的内容。已核准的示例是校准标准；如果草稿无法自然融入示例内容，则草稿不合格。
事实来自Vault，断言需有凭证。涉及企业的数字、成果或故事必须追溯至Vault中的文件；涉及外部世界的断言必须追溯至已核查的研究。如果公开呼吁建议了重要的商业举措，则必须同时满足内部和外部凭证要求，否则不得放入公开内容主体，而是记录在草稿的“搁置建议”部分，标注为“搁置：缺失内部凭证”或“搁置：缺失外部凭证”，并记录召回/研究动作。绝不能悄然删除该内容。为创始人的公开帖子编造统计数据是最糟糕的低质量内容：它会以创始人的名义发布。无凭证的断言：要么移除，要么进行研究核实。
先核准再创作。在断言进入草稿或凭证部分之前，执行共享的持久断言核准流程。重新查看来源，引用确切的支持语句，并验证主体和单位：客户数量不能变成个人帖子数量，也不能作为客户成果的证明。根据指定输入重新计算推导得出的断言。创始人的回忆需标记为“创始人表述：未验证”，直到核查通过；绝不能先将其转化为自信的钩子内容。
个人传记类断言仅接受凭证验证。绝不能断言关于创始人的第一人称事实：时长（“多年来”“两年”）、数量（“四百篇帖子”）、历史（“我一直”）或习惯，除非这些确切表述出现在
```
raw/
```
文件或实时转录文本中。客户数量不是个人帖子数量；指标不是传记内容。如果Vault中没有创始人本人对该事实的表述，则要么移除该行内容，要么向创始人询问；模型绝不能先推断传记细节，再为该推断寻找凭证。这是连续三轮迭代中造成最严重问题的单一漏洞，属于硬性规则。
严格遵循术语表。内容需使用创始人的标准术语；在草稿提交前需标记并修正术语偏差，无论是修改草稿还是术语表。

完成标志：生成符合口吻、凭证和术语表要求的草稿。

Step 3: The drift check, out loud

步骤3：口吻偏差核查（口头说明）

Before delivering, state the check results in one line each: voice (which sample it sits beside), claims (each receipt named), glossary (clean or what was fixed). A draft failing any check gets rewritten before the founder sees it, not annotated.

Done when: the founder receives a draft plus the three check lines, never a bare wall of text.

在交付草稿之前，用一句话分别说明核查结果：口吻（与哪个示例风格一致）、断言（每个断言对应的凭证名称）、术语表（无偏差或已修正的内容）。任何未通过核查的草稿都需重新撰写后再提交给创始人，不得仅附加注释。

完成标志：创始人收到草稿及三条核查说明，而非单纯的文本内容。

Step 4: File and close the loop

步骤4：归档并闭环

The filing is deterministic. Run the shared dedupe rule first (search

index.md

hub/business.md

wiki/business/content/

), then write the piece to

wiki/business/content/<date>-<slug>.md

. Frontmatter is the base five plus

type: content

content_state: draft

channel

published_at: null

, and the serving initiative path or null. Move to

approved

only on the founder's explicit approval; move to

published

and set

published_at

only when the founder confirms publication. A draft is never a canonical business fact. List it in

index.md

under Content, link

hub/business.md

, and append the one row:

## [date] content | <piece>

. A piece serving an initiative also gets a dated pointer in that initiative's Log; the draft text stays in its canonical file.

For approval or publication, capture the founder's exact words in an immutable

raw/inbox/session-receipt-<date>-<slug>.md

. Approved content adds

approval_receipt: <path>#<exact words>

; published content also adds

publication_receipt: <path>#<exact words>

. A phrase edit does not count as whole-draft approval. These

content_state: approved|published

transitions are T1 consent surfaces (shared contract, Immutable consent receipts): with no founder yes captured, the state stays

draft

. Published content cannot contain

[unverified]

; graph-audit blocks the transition if it does.

Every lifecycle change runs the linked-state transaction: update the index/hub summary, the serving initiative's publication step, any publication metric, and voice-sample eligibility. A founder-confirmed publication cannot remain

draft

; a draft cannot be counted as shipped.

Repurposing candidates get named while the piece is fresh (per the craft block's moves): the one thing the founder approves can become several. Publishing and scheduling stay with the founder: this environment writes drafts, the founder ships them.

归档流程是确定性的。首先执行共享的去重规则（搜索

index.md

、

hub/business.md

、

wiki/business/content/

），然后将内容写入

wiki/business/content/<date>-<slug>.md

。前置元数据包含基础五项加上

type: content

、

content_state: draft

、

channel

、

published_at: null

，以及服务的项目路径（若无则为null）。只有在创始人明确批准后，才能将状态改为

approved

；只有在创始人确认发布后，才能将状态改为

published

并设置

published_at

。草稿永远不能作为企业的标准事实。在

index.md

的“内容”部分列出该草稿，链接至

hub/business.md

，并添加一行：

## [date] content | <piece>

。服务于某个项目的内容还需在该项目的日志中添加日期指针；草稿文本保留在其标准文件中。

对于批准或发布操作，需将创始人的确切表述记录在不可更改的

raw/inbox/session-receipt-<date>-<slug>.md

文件中。已批准的内容需添加

approval_receipt: <path>#<exact words>

；已发布的内容还需添加

publication_receipt: <path>#<exact words>

。仅修改个别短语不算批准整个草稿。这些

content_state: approved|published

状态转换属于T1同意界面（共享协议，不可更改的同意凭证）：如果未记录创始人的同意，状态将保持为

draft

。已发布的内容不能包含

[unverified]

；如果包含，图谱审计（graph-audit）将阻止状态转换。

每次生命周期变更都需执行关联状态事务：更新索引/中心摘要、服务项目的发布步骤、任何发布指标，以及口吻示例的资格。创始人确认发布的内容不能保持

draft

状态；草稿不能被算作已发布内容。

在内容新鲜时确定可复用的方向（根据创作模块的方法）：创始人批准的一项内容可以衍生出多项内容。发布和排期由创始人负责：本环境仅负责草拟草稿，由创始人发布。

Mandatory filing gate

强制归档校验

Run
```
scripts/graph-audit
```
on the complete content artifact and every other touched durable file.
Fix every violation and rerun it. The draft, lifecycle projections, and content event remain incomplete until it exits zero.

Done when: the draft is filed with explicit lifecycle state, logged once, and its repurposing path is named.

对完整的内容工件和所有其他修改过的持久文件运行
```
scripts/graph-audit
```
。
修复所有违规问题并重新运行。只有当脚本返回零（无违规）时，草稿、生命周期预测和内容事件才算完成。

完成标志：草稿已按明确的生命周期状态归档，已记录一次，且已确定其复用路径。