breakthrough-content-engine
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseBreakthrough Content Engine
Breakthrough Content Engine
给一个目标，出一整档内容规划。人只审一张表，其余机械推导。
这是一个 dispatcher。下面的地图告诉你每一层住在哪个 档，按需加载，不要一次全读。
references/Give it a goal and it produces a complete content plan. People review only one table; everything else is mechanically derived.
This is a dispatcher. The map below tells you which layer lives in which file. Load on demand; do not read everything at once.
references/它凭什么不一样
What makes it different
大部分内容工具的形状是「给我一个题目，我给你一篇稿」。这一套反过来：你给我一个生意目标，我先告诉你这一档该打谁、打什么、打几支，最后才写稿。
三条它跟别人不同的地方：
- 配比是推导出来的，不是抄比例。 没有任何实测研究支持任何漏斗阶段的内容篇数配比（80/20、4-1-1、70/20/10 全部是断言，其中 70/20/10 还是风险分配被误引成漏斗分配）。所以这里的数字来自你的产能、你的漏斗诊断、你的跑道，而不是来自一句口号。产能封顶，目标定形，诊断修形，格式落位。
- 人只审 seed，不审稿。 一张 8 到 20 条的 seed sheet 是唯一的人工决策点。十几二十格的内容地图从 seed 机械推出来，可再生。没有人逐格审那二十几个格子，规模要服务人的判断，不是淹没它。
- 它会拒绝。 粉丝规模不够就不出配比，改出触达获取任务单；手上没有真材料就不写稿，改出采集指令。「材料不够，先去拿材料」是一个合法的、正确的输出。
Most content tools have the shape of “Give me a topic and I’ll give you a draft.” This system reverses that: You give me a business goal, and I first tell you who this run should target, what it should cover, and how many pieces to produce. Only then do we write the copy.
Three things make it different:
- The mix is derived, not copied from a ratio. No empirical research supports any number of content pieces per funnel stage (80/20, 4-1-1, and 70/20/10 are all assertions; 70/20/10, moreover, is a risk allocation misquoted as a funnel allocation). The numbers here therefore come from your capacity, your funnel diagnosis, and your runway, not from a slogan. Capacity sets the ceiling, the goal gives it shape, diagnosis refines it, and format locks it in.
- People review the seed, not the drafts. A seed sheet of 8 to 20 entries is the only human decision point. The content map of roughly 12 to 20 slots is mechanically derived from the seed and can be regenerated. No one should review those twenty-odd slots one by one; scale should serve human judgment, not overwhelm it.
- It says no. If the audience is not large enough, it does not produce a mix; it produces a reach-and-acquisition task list instead. If there is no real material at hand, it does not write a draft; it produces collection instructions. “Not enough material—go get material” is a legitimate, correct output.
什么时候用
When to use it
- ✅ 要规划一整档内容（一个月、一次 launch、一段跑道）
- ✅ 内容一直发但没有效果，想知道是哪一段漏了
- ✅ 想知道这一档该出几支视频几篇图文，而不是凭感觉
- ❌ 只是要写一篇文案 → 不用跑整条 pipeline
- ❌ 付费投放为主 → 配比逻辑整个不同，这里只管 organic
- ❌ 还没有产品、还没有人买过 → 那是产品验证问题，不是内容问题
- ✅ You need to plan an entire content run (one month, a launch, or a stretch of runway)
- ✅ You keep publishing but get no results, and want to know which stage of the funnel is leaking
- ✅ You want to know how many videos and graphic posts this run should include instead of relying on gut feel
- ❌ You only need one piece of copy → do not run the entire pipeline
- ❌ Paid media is the primary channel → the mix logic is completely different; this engine only handles organic content
- ❌ You do not yet have a product, or no one has bought anything → that is a product-validation problem, not a content problem
四个 mode
Four modes
这个 skill 有四种进法。先判是哪一种，再往下走。
| Mode | 什么时候 | 干什么 | 载入 |
|---|---|---|---|
| Plan | 「帮我规划这个月」「这一档要发几支」 | 从目标跑到成稿的主线，收尾做改稿回流 | modes/plan.md |
| Capture | 「我捞到几条客人的话」「NEEDS-CAPTURE 那几条我补到了」 | 收真料、分 | modes/capture.md |
| Log | 门铃点名，或「记一下成绩」 | 3 / 7 / 15 天纯录入，30 秒做完，不做判断 | modes/log.md |
| Review | 「复盘一下」，或一档跑完 6 到 8 周后 | 读数据、重跑诊断与配比、出提案不出结论 | modes/review.md |
Capture 是整套引擎唯一的真证据入口。 别的地方进来的都是上下文。
This skill has four ways in. Determine which one applies before proceeding.
| Mode | When | What it does | Load |
|---|---|---|---|
| Plan | “Help me plan this month” or “How many pieces should this run include?” | The main path from objective to finished drafts, ending with a revision feedback loop | modes/plan.md |
| Capture | “I picked up a few things customers said” or “I filled in those NEEDS-CAPTURE items” | Collect real material, assign | modes/capture.md |
| Log | When the doorbell names a task, or “Record the results” | Data entry only at 3 / 7 / 15 days, completed in 30 seconds, with no judgment | modes/log.md |
| Review | “Run a review,” or 6 to 8 weeks after a content run ends | Read the data, rerun the diagnosis and mix, and produce proposals rather than conclusions | modes/review.md |
Capture is the engine’s only entry point for real evidence. Everything entering from elsewhere is context.
有 second-brain vault 的话
If you have a second-brain vault
看得到 就是有。有的话开场先读 references/_vault.md：扫生意翼拿品牌上下文、读覆盖层（用户自己校出来的数字优先于出厂值）、知道东西该长在哪里。
99_Meta/structure-doctrine.md🛑 每个 mode 的第一个动作都是认路（ §1.5，整节跑完）：一道 glob 找 这本地址簿，路径全部从它拿；拿到之后接着跑同一节的门铃接线检查。⛔ 不分第一次还是第一百次，⛔ 不准凭记忆猜路径：生意翼与品牌的夹名是用户自己取的，猜不到。
_vault.mdcontent-engine-paths.md⚠️ 扫回来的是上下文，不是证据。 八柱地基与品牌策略报告读起来像证据、连引号都像，但实测一份 100KB 的已锁策略跑出 0 条 顾客 barrier。所以扫 vault 的第一个动作是引号出处扫描，未标注一律按构造处理。
confirmed没有 vault 一样跑，照 问那六件事。⛔ vault 是加分，不是前提。
00-intake.mdIf you can see , you have one. If you do, begin by reading references/_vault.md: scan the Business Wing for brand context, read the overlay (numbers calibrated by the user take precedence over factory defaults), and understand where things should live.
99_Meta/structure-doctrine.md🛑 The first action in every mode is wayfinding ( §1.5, run the entire section): use one glob operation to find the address book and take every path from it; once you have it, continue with the doorbell wiring check in the same section. ⛔ Whether this is the first time or the hundredth time, ⛔ do not guess paths from memory: the names of the Business Wing and brand folders are chosen by the user, so they cannot be guessed.
_vault.mdcontent-engine-paths.md⚠️ What comes back from the scan is context, not evidence. The Eight-Pillar Foundation and the brand strategy report may read like evidence—even the quotation marks make them look that way—but testing a locked 100KB strategy produced 0 customer barriers. Therefore, the first action after scanning the vault is a quotation-provenance scan; anything unmarked is treated as constructed.
confirmedThe engine works without a vault too. Ask the six questions in as usual. ⛔ A vault is a bonus, not a prerequisite.
00-intake.md门铃接线（认路时做，⛔ 不是安装时）
Doorbell wiring (during wayfinding, ⛔ not at installation)
用户如果有产品生成的 command-base skill，引擎会去改他那一份已经装好的（不是产品的 template，template 只影响以后的新装），让门铃认得内容到期这件事。
⛔ 这件事不发生在安装那一刻。 是套件管理器，它不执行 skill 里的任何一句话；而且装的那一刻没有人知道这个用户的宅在哪。⇒ 触发点是每个 mode 开场认完路那一步（ §1.5 的「认完路还有一步」），⛔ 不是 §8：§8 只在地址簿不存在时跑，地址簿已经存在的用户永远等不到它。
npx skills add_vault.md_vault.md⚠️ 产品端的门铃教条：铃只响一次，而且由铃自己点名什么到期了，不丢一道选择题给主人（产品 的「One doorbell, two files」讲的就是这件事）。所以不新增第二个铃，只是把「哪几篇到 3 / 7 / 15 天了」写进现有门铃读得到的地方，铃照响一次，多点名一件事。
modes/maintenance.md⛔ 改的是 Claude Code 实际载入的那一份（）；vault 里那一份在 copy 安装上只是副本，改了不会报错也不会生效。改完 grep 读回确认。⛔ 不要写进门铃区块本身，那一块产品升版会整块覆盖。
~/.claude/skills/<slug>-command-base/SKILL.md找哪一支、插在哪、插什么、重跑怎么不会插两次、接不上怎么记，五件事全部住 §1.5 与 §9，⛔ 别凭这一段的记忆办事。
_vault.mdIf the user has a product-generated command-base skill, the engine will modify the copy the user has already installed (not the product’s template—the template only affects future installs) so that the doorbell recognizes when content is due.
⛔ This does not happen at installation. is a suite manager; it does not execute any instruction inside the skill, and at the moment of installation nobody knows where the user’s home directory is. ⇒ The trigger is the wayfinding step at the start of every mode ( §1.5, “There is one more step after wayfinding”), ⛔ not §8: §8 runs only when the address book does not exist, so users who already have one would never reach it.
npx skills add_vault.md_vault.md⚠️ Product-side doorbell doctrine: The bell rings only once, and the bell itself names what is due, without throwing a multiple-choice question back to the owner (the product’s , “One doorbell, two files,” says exactly this). Therefore, do not add a second bell; simply write which pieces have reached 3 / 7 / 15 days somewhere the existing doorbell can read it. The bell still rings once and now names one additional item.
modes/maintenance.md⛔ Modify the copy Claude Code actually loads (). In a copy-based installation, the copy in the vault is merely a duplicate; editing it will raise no error but will have no effect. After editing, use grep to read it back and confirm the change. ⛔ Do not write into the doorbell block itself; a product upgrade will overwrite that entire block.
~/.claude/skills/<slug>-command-base/SKILL.mdWhich branch to use, where to insert it, what to insert, how to rerun without inserting it twice, and how to record a failed connection—all five are documented in §1.5 and §9. ⛔ Do not act based on memory of this section.
_vault.md跑的时候按顺序过这几层
Follow these layers in order while running
| 层 | 做什么 | 谁做 | 档 |
|---|---|---|---|
| L0 | 收 objective、期限、产能、平台与粉丝规模 | 问 | |
| L0.5 | 规模闸：规模不够就不出配比 | 闸 | |
| L1 | 漏斗诊断，出 stage-pressure profile | 引擎建议 | |
| L2 | 主轴建议，2 到 3 张卡 | 人挑（决策点 1） | |
| L3 | 配比：各阶段各格式几支、上几个平台 | 引擎建议，人可改数 | |
| L4 | Seed sheet | 人审（决策点 2，唯一一次） | |
| L5 | 内容地图，机械推导 | 引擎 | |
| L6 | 挑一格写稿 | 引擎 | |
| Layer | What it does | Who does it | File |
|---|---|---|---|
| L0 | Collect the objective, deadline, capacity, platforms, and audience size | Ask | |
| L0.5 | Scale gate: if the audience is not large enough, do not produce a mix | Gate | |
| L1 | Funnel diagnosis; produce a stage-pressure profile | Engine suggests | |
| L2 | Mainline recommendations; 2 to 3 cards | Human chooses (decision point 1) | |
| L3 | Mix: how many pieces per stage and format, and which platforms | Engine suggests; human may change the numbers | |
| L4 | Seed sheet | Human reviews (decision point 2, the only review) | |
| L5 | Content map, mechanically derived | Engine | |
| L6 | Select one slot and draft the copy | Engine | |
按需加载
Load on demand
| 用户要什么 | 读哪个 |
|---|---|
| 开始一档新规划 / 「帮我规划这个月」 | |
| 「我的内容为什么没人看」/ 诊断卡在哪一段 | |
| 定主轴 / 「我该讲什么角度」/ reframe | |
| 「这一档要出几支」/ 配比 / 上哪个平台 | |
| 挑内容类型 / 「有什么内容可以发」 | |
| 出 seed sheet / 审 seed | |
| 推内容地图 / 内容之间怎么串 | |
| 写一篇 / 一篇怎么长 | |
| 某个平台怎么发 | |
| 想标题 / 开场句 / 视频钩 | |
| 稿子读起来像 AI / 出稿前检查 | |
| 「我没有素材可以写」 | |
| 一次跑一整档 / 批量 | |
| 有 vault / 覆盖值 / 东西该长在哪 | |
| 要改一条规则 / 想知道某条为什么这样裁 | |
| 这个用户自己校出来的数字与学到的东西 | vault 的 |
| What the user wants | What to read |
|---|---|
| Start a new content plan / “Help me plan this month” | |
| “Why isn’t my content getting views?” / diagnose where the funnel is blocked | |
| Set the mainline / “What angle should I take?” / reframe | |
| “How many pieces should this run include?” / mix / which platforms | |
| Select a content type / “What can I post?” | |
| Produce a seed sheet / review the seed | |
| Derive the content map / how the content pieces connect | |
| Write one piece / how one piece should be structured | |
| How to publish on a specific platform | |
| Want a title / opening line / video hook | |
| The copy reads like AI / pre-publication check | |
| “I have no material to write from” | |
| Run an entire content plan at once / batch processing | |
| Have a vault / override values / where things should live | |
| Change a rule / find out why a rule was decided that way | |
| Numbers and lessons the user has calibrated themselves | The vault’s |
几条贯穿全场的规矩
Rules that apply throughout
这几条在很多档里会重复出现，因为它们真的到处适用：
- 遮品牌名测试。 把品牌名盖掉，如果这条内容随便哪个同行都能发，它就失败了。一看就知道是你，才算成功。
- 免费老师陷阱。 知识很廉价，AI 随便生成；观点才值钱。干货类内容最容易踩，每一条都必须带你自己的方法和立场。
- 深 ≠ 独特。 往下挖情绪、挖身份，挖到最后往往挖到一个人人适用的普适真相。那是最高级的同质化，不是洞察。差异化来自 reframe（你的视角），不是来自挖得更深。
- Awareness 里一 pitch，三个阶段塌成一个。 认知阶段的内容里出现产品，读者直接划走。这条没有例外。
- 只准真实稀缺，不准制造紧迫。 在错的阶段用制造出来的急迫感，是分类错误，不是风格选择。
- 真实记忆有废料，编造的记忆没有。 一篇稿子里如果每一个细节都刚好在替论点服务，一个多余的都没有，那多半是编的。而那个多余的细节必须跟承重细节同源，否则随手编一个无关细节就能过关，这条规则就白写了。
These rules appear in many files because they genuinely apply everywhere:
- Brand-name masking test. Cover the brand name. If any competitor could publish the piece, it has failed. It succeeds only if it is immediately recognizable as yours.
- The free-teacher trap. Knowledge is cheap, and AI can generate it on demand; an opinion is valuable. How-to content is especially prone to this trap. Every piece must carry your own method and position.
- Deep ≠ unique. Dig into emotion or identity, and you will often end up with a universal truth that applies to everyone. That is the highest form of homogenization, not insight. Differentiation comes from a reframe (your perspective), not from digging deeper.
- One pitch in Awareness collapses all three stages. If a product appears in awareness-stage content, readers will swipe away immediately. There are no exceptions.
- Only genuine scarcity, never manufactured urgency. At the wrong stage, manufactured urgency is a category error, not a style choice.
- Real memories contain incidental material; fabricated memories do not. If every detail in a draft happens to serve the argument and not one detail is superfluous, it is probably fabricated. That superfluous detail must also come from the same source as the load-bearing details; otherwise, any random irrelevant detail could pass and the rule would be pointless.
一句话
In one sentence
内容是慢功夫。先有真材料，再有角度，再有内容。 这套工具能做的是让每一步都有依据，不能替你去把顾客说过的那句话捡回来。
Content is slow work. Get real material first, then find an angle, then create the content. What this toolkit can do is ground every step; it cannot retrieve the sentence a customer actually said for you.