Back to Details

book-toc-lab

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Book TOC Lab

Book TOC Lab

Treat a useful nonfiction book as a problem-solving product for a specific reader. The table of contents is the product design, not a decorative outline. Build and test the promise, scope, recommendation loop, and TOC before drafting so the manuscript has a clear job and useful progression.
Use this skill to produce or improve a book plan that answers:
  • Who is this book for?
  • What painful or valuable problem does it help them solve?
  • What should be different for the reader after each chapter?
  • What does the book deliberately leave out?
  • Why would a satisfied reader recommend it to a specific person in a specific situation?
将实用非虚构书籍视为面向特定读者的问题解决型产品。目录是产品设计，而非装饰性大纲。在动笔前构建并测试书籍承诺、内容范围、推荐逻辑及目录，确保手稿具备明确的定位和清晰的实用进阶路径。
使用本技能生成或优化书籍规划，解答以下问题：
  • 本书面向哪些读者？
  • 它能帮助读者解决哪些棘手或有价值的问题？
  • 读者读完每一章后应获得哪些改变？
  • 本书刻意省略了哪些内容？
  • 满意的读者会在何种情境下向特定人群推荐本书？

Resource Routing

资源指引

Load only the files needed for the task:
NeedRead
Core model, DEEP, promise, scope, recommendation loop
references/core/knowledge.md
Concrete planning and validation rules
references/core/rules.md
Before/after examples for scope and TOC titles
references/core/examples.md
Quick planning and review checklist
references/core/checklist.md
Step-by-step TOC design before drafting
workflows/design-toc.md
Step-by-step TOC validation with readers
workflows/validate-toc.md
仅加载任务所需文件：
需求读取文件
核心模型、DEEP框架、书籍承诺、内容范围、推荐逻辑
references/core/knowledge.md
具体规划与验证规则
references/core/rules.md
内容范围与目录标题的前后示例
references/core/examples.md
快速规划与审核清单
references/core/checklist.md
动笔前的分步目录设计流程
workflows/design-toc.md
读者参与的分步目录验证流程
workflows/validate-toc.md

Fast Workflow

快速工作流

  1. Lock the reader promise before outlining.
  2. Define in-scope, out-of-scope, prerequisites, and depth lines.
  3. Write the recommendation story: trigger, recommender, recommended reader, and why this book is the obvious fit.
  4. Draft chapters as reader takeaways, not author topic buckets.
  5. Order chapters by reader progress: orientation, foundation, action, judgment, and integration.
  6. Pressure-test every chapter against the promise, reader outcome, missing steps, boredom risk, confusion risk, skepticism, and recommendability.
  7. Validate the TOC before drafting when practical.
  1. 在拟定大纲前锁定读者承诺。
  2. 界定内容包含范围、排除范围、前置知识及深度边界。
  3. 撰写推荐场景：触发点、推荐者、目标读者，以及本书为何是最佳选择。
  4. 以读者收获为核心撰写章节，而非以作者的主题分类为框架。
  5. 按照读者的学习进阶顺序排列章节：认知引导、基础构建、实践行动、判断提升、整合应用。
  6. 针对每一章，从书籍承诺、读者成果、缺失步骤、枯燥风险、混淆风险、读者质疑点及推荐价值等方面进行压力测试。
  7. 尽可能在动笔前验证目录。

Output Format

输出格式

When asked to create or improve a TOC, return:
  1. Book brief: reader, problem, promise, scope, out-of-scope.
  2. Recommendation story: trigger, recommender, recommended reader, why this book.
  3. Recommended TOC with chapter-level reader problems and takeaways.
  4. Reader journey notes explaining the order.
  5. Risk list: missing prerequisites, vague chapters, likely confusion, likely boredom.
  6. Validation plan: 3-7 concrete ways to test the TOC before drafting.
当要求创建或优化目录时，返回以下内容：
  1. 书籍简介：读者群体、解决的问题、核心承诺、包含范围、排除范围。
  2. 推荐场景：触发点、推荐者、目标读者、本书适配理由。
  3. 推荐目录，包含各章节对应的读者问题与核心收获。
  4. 读者学习路径说明：解释章节顺序的逻辑。
  5. 风险清单：缺失的前置知识、模糊的章节内容、可能的混淆点、可能的枯燥点。
  6. 验证计划：3-7种具体的动笔前目录测试方法。

Quality Bar

质量标准

A good TOC should feel useful even before the book exists. A reader should be able to scan it and understand what the book helps them accomplish, whether it is for them, and why the chapter sequence makes sense.
Do not optimize for literary cleverness before usefulness. Clever titles are acceptable only after the reader promise and chapter takeaways are obvious.
优质的目录在书籍尚未完成时就应具备实用性。读者只需浏览目录，就能明白本书能帮助他们达成什么目标、是否适合自己，以及章节顺序的合理性。
在确保实用性之前，不要追求文学上的巧妙。只有当读者承诺和章节核心收获清晰明确后，才可以使用巧妙的标题。