series-continuity

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Series Continuity

系列连续性

Overview

概述

Plan and maintain sequels, prequels, and companion books as linked Story Skills projects. Each book stays a standalone project with its own

story.md

, characters, world, chapters, and continuity files. Books point at each other through

story.md

frontmatter, and

story series

checks the canon they share.

```
series
```
- kebab-case series id shared by every book, such as
```
the-ember-cycle
```
```
series-title
```
- optional retail series name, such as
```
The Ember Cycle
```
, that the metadata sheet prints in place of the id
```
book-number
```
- publication order (1, 2, 3...);
```
0
```
for a prequel published later, a decimal such as
```
1.5
```
for a between-books novella
```
follows
```
- paths to books set earlier in the story's chronology
```
precedes
```
- paths to books set later in the story's chronology

Chronology and publication order are separate. A prequel written after the first book has

book-number: 2

and lists

../book-one

under

precedes

This skill owns the book-level layer: linked books and the canon they share. The within-serial installment layer — how serial or episodic installments are structured — is covered by the

genre-craft

skill's serial/episodic structure reference.

Links are relative paths from the book root, and every link needs a matching backlink: if book two lists

../book-one

under

follows

, book one must list

../book-two

under

precedes

. Keep sibling books in the same parent folder so the paths stay short and portable.

将续集、前传和伴随作品作为相互关联的 Story Skills 项目进行规划和维护。每本书仍是独立项目，拥有各自的

story.md

、角色、世界观、章节和连续性文件。各本书通过

story.md

的 frontmatter 相互指向，

story series

会检查它们共享的正典。

```
series
```
- 由每本书共享的 kebab-case 系列 ID，例如
```
the-ember-cycle
```
```
series-title
```
- 可选的零售系列名称，例如
```
The Ember Cycle
```
；元数据表会显示该名称，而不是 ID
```
book-number
```
- 出版顺序（1、2、3……）；
```
0
```
表示后来出版的前传，
```
1.5
```
这样的十进制数表示两本书之间的中篇小说
```
follows
```
- 指向故事时间线上设定于更早时期的书籍路径
```
precedes
```
- 指向故事时间线上设定于更晚时期的书籍路径

故事时间线与出版顺序相互独立。一部在第一本书之后创作的前传，其

book-number: 2

，并在

precedes

下列出

../book-one

。

此 skill 负责书籍层级：相互关联的书籍及其共享的正典。系列内各期（serial/episodic installment）的结构层——连载或分集形式如何组织——由

genre-craft

skill 的 serial/episodic 结构参考文档涵盖。

链接使用相对于书籍根目录的路径，并且每个链接都需要对应的反向链接：如果第二本书在

follows

下列出

../book-one

，第一本书就必须在

precedes

下列出

../book-two

。应将同系列书籍放在同一父文件夹中，以保持路径简短且便于迁移。

When to Use

使用场景

Starting a sequel, prequel, interquel, or companion book to an existing project
Carrying characters, locations, systems, factions, artifacts, or glossary terms into another book
Revising a book that other books in the series depend on
Keeping a series bible, or planning and pitching a series of several books (see
```
references/series-bible.md
```
)
NOT for a single standalone book (use
```
story-init
```
), for within-book continuity (use
```
revision-continuity
```
), or for the query letter, pitch, or synopsis of a single book (use
```
submission
```
). A series pitch stays here: the series overview and the series line in book one's query (see
```
references/series-bible.md
```
)

为现有项目开始创作续集、前传、中间篇或伴随作品
将角色、地点、体系、派系、物品或术语表条目延续到另一本书
修订系列中其他书籍所依赖的一本书
维护系列圣经，或规划、推介由数本书组成的系列（参见
```
references/series-bible.md
```
）
不适用于单本独立作品（使用
```
story-init
```
）、单本书内部的连续性维护（使用
```
revision-continuity
```
），也不适用于单本书的 query letter、推介或梗概（使用
```
submission
```
）。系列推介仍属于此 skill：包括系列概览，以及第一本书 query 中的系列条目（参见
```
references/series-bible.md
```
）

Starting a Linked Book

开始创建关联书籍

Read the existing book first:

story.md

characters/_index.md

worldbuilding/_index.md

plot/timeline.md

continuity/state.md

, open files in

continuity/questions/

and

continuity/promises/

, and the final chapters.

Ask the user for:
- Title and synopsis
- Relationship: sequel (set after), prequel (set before), or companion (set alongside, with no chronology link)
- How much time passes between the books
- Which characters and places return
Create the project with the CLI, run from the folder that contains the existing book:

shell

undefined

首先阅读现有书籍：

story.md

、

characters/_index.md

、

worldbuilding/_index.md

、

plot/timeline.md

、

continuity/state.md

、

continuity/questions/

和

continuity/promises/

中仍开放的文件，以及最后几章。

向用户询问：
- 标题和梗概
- 关系类型：续集（发生在之后）、前传（发生在之前）或伴随作品（同时发生，不建立时间线关联）
- 两本书之间相隔多长时间
- 哪些角色和地点会再次出现
使用 CLI 创建项目，并从包含现有书籍的文件夹中运行：

shell

undefined

Sequel: set after book one

续集：发生在第一本书之后

story init '{Title}' --follows '{existing-book-dir}' --synopsis '{synopsis}'

Prequel: set before book one

前传：发生在第一本书之前

story init '{Title}' --precedes '{existing-book-dir}' --synopsis '{synopsis}'

Companion: set alongside book one, with no chronology link

伴随作品：与第一本书同时发生，不建立时间线关联

story init '{Title}' --series '{series-id}' --synopsis '{synopsis}'


The title and synopsis are the user's own words, and a folder name can hold spaces, so wrap each value in single quotes. Never paste a value into double quotes, where `$(...)`, backticks, and `"` still take effect. A single quote inside a value depends on the shell: write it as `'\''` in a POSIX shell (bash, zsh, sh, Git Bash) and as `''` in PowerShell. Never run the command in cmd.exe, which has no single quotes and runs `&` inside a value; use PowerShell or a POSIX shell.

Run `init` from the folder that contains the existing book, never from inside it: `init` refuses a new book inside another project, and a linked book outside the new book's parent folder. It also refuses a `--series` that differs from the linked book's, and a `--book-number` already used in the series. `init` checks that the linked path is a story project, writes the relative link, adds the backlink (and the new book's `series`, when the existing book has none) to the existing book's `story.md`, and inherits `series`, `genre`, `sub-genre`, `pov`, and `tense`, plus `series-title`, `author` or `authors`, and `language` when the linked book sets them. When any book in the linked series has a `book-number`, it sets `book-number` to one more than the highest whole number used anywhere in the series, so publication numbers never collide. A normal `story init` book has none, so a series with no numbered books leaves the new book unnumbered. Pass `--book-number` (or write the field on both `story.md` files) in that case. Pass `--series`, `--genre`, `--pov`, or `--tense` to override the inherited values.

If the existing book has no `series` yet, pass `--series {series-id}`: `init` also writes that `series` into the existing book's `story.md`. Add matching `book-number` values to both `story.md` files yourself.

A companion has no `follows` or `precedes` link. So `init` inherits nothing from book one, and it writes nothing to book one's `story.md`. Pass `--genre`, `--pov`, and `--tense` to match book one. Use the same `--series` id as book one. Set `series` in book one by hand if it has none. Set `book-number` by hand: pass `--book-number` to the companion's `init`, or write the field in each `story.md`. `story series` does not see an unlinked companion, so compare its canon by hand (see `references/series-bible.md`).

If the CLI is not available, add the fields to both `story.md` files by hand.

4. Add a `## Series Notes` section to the new `story.md` body. Record where the book sits in the chronology, the time gap, and the canon facts it must not contradict. `references/series-bible.md` covers what to put in it.

story init '{Title}' --series '{series-id}' --synopsis '{synopsis}'


标题和梗概应使用用户自己的原话。文件夹名称可以包含空格，因此每个值都应使用单引号包裹。绝不要把值粘贴到双引号中，因为 `$(...)`、反引号和双引号仍会生效。值中的单引号如何处理取决于 shell：在 POSIX shell（bash、zsh、sh、Git Bash）中写作 `'\''`，在 PowerShell 中写作 `''`。绝不要在 cmd.exe 中运行该命令，因为它不支持单引号，而且会执行值中的 `&`；请使用 PowerShell 或 POSIX shell。

始终从包含现有书籍的文件夹运行 `init`，绝不要在其内部运行。`init` 会拒绝在另一个项目内创建新书，也会拒绝将关联书放在新书父文件夹之外。它还会拒绝使用与关联书不同的 `--series`，以及使用系列中已经存在的 `--book-number`。`init` 会检查关联路径是否为 story 项目，写入相对链接并添加反向链接；如果现有书没有 `series`，它还会把新书的 `series` 写入现有书的 `story.md`。它还会继承 `series`、`genre`、`sub-genre`、`pov` 和 `tense`，以及关联书已设置的 `series-title`、`author` 或 `authors` 和 `language`。当关联系列中的任何一本书具有 `book-number` 时，它会将 `book-number` 设为整个系列中已使用的最大整数加一，因此出版编号不会冲突。普通的 `story init` 书籍没有该字段，所以没有任何编号书籍的系列会让新书保持未编号。在这种情况下，请传入 `--book-number`，或在两个 `story.md` 文件中写入该字段。传入 `--series`、`--genre`、`--pov` 或 `--tense` 可以覆盖继承的值。

如果现有书尚无 `series`，请传入 `--series {series-id}`：`init` 也会把该 `series` 写入现有书的 `story.md`。请自行在两个 `story.md` 文件中添加相互匹配的 `book-number` 值。

伴随作品没有 `follows` 或 `precedes` 链接。因此，`init` 不会从第一本书继承任何内容，也不会向第一本书的 `story.md` 写入任何内容。请传入 `--genre`、`--pov` 和 `--tense`，使其与第一本书一致。使用与第一本书相同的 `--series` ID。如果第一本书没有 `series`，请手动设置。`book-number` 也需手动设置：将其传给伴随作品的 `init`，或写入每个 `story.md`。`story series` 无法识别未链接的伴随作品，因此需要手动比较两者的正典（参见 `references/series-bible.md`）。

如果 CLI 不可用，请手动向两个 `story.md` 文件添加相应字段。

4. 在新书的 `story.md` 正文中添加 `## Series Notes` 部分。记录本书在故事时间线中的位置、时间间隔，以及不得与其矛盾的正典事实。`references/series-bible.md` 介绍了应记录的内容。

Carrying Canon Across Books

在书籍之间迁移正典

Only carry entities the new book actually uses. For each one, copy the file from the other book and then adjust it:

Keep the filename id identical.
```
story series
```
matches entities across books by id. A renamed file is a new entity to the checker.
```
story rename
```
warns when the id is also defined in a linked book; rename it there too, or keep the old id.
Keep
name
identical. Put new titles or epithets in
```
aliases
```
, such as
```
General Maren
```
in a prequel for
```
Lord Maren
```
. A different
```
name
```
produces a warning, and so does a different
```
pronunciation
```
.
Set state for this book's starting point, not the source book's ending.
- Sequel: start from the earlier book's final
```
status
```
  , relationships, ownership, and knowledge.
- Prequel: start from the earlier situation, and write the later book's facts as fixed endpoints in a
```
## Series Canon
```
  section.
Remove book-local references.
```
died-in
```
, the
```
from
```
of each
```
progressions
```
entry, and every other chapter id point at chapters in the source book. Set the frontmatter to the state the character starts this book in, and drop the source book's
```
progressions
```
. For a character who died before this book begins, by
```
died-in
```
or by a status progression, keep
```
status: deceased
```
, remove
```
died-in
```
, and list them only in
```
mentions
```
:
```
story continuity
```
warns when one appears in a chapter or scene cast. If they come back in this book, add a status progression to
```
alive
```
from that chapter;
```
story series
```
then allows them on the page from there.
Prune or carry every link. Relationships,
```
locations
```
,
```
notable-characters
```
, faction
```
members
```
, and artifact
```
owner
```
/
```
location
```
must point at entities that exist in this book, with backlinks. Either carry the linked entity too, or remove the reference.
Do not copy chapters, scenes, arcs, questions, promises, or
```
continuity/state.md
```
. Rebuild them for the new book:
- Unresolved questions or promises the new book continues become new files in its
```
continuity/
```
  folders.
- Events from the other book become
```
Backstory Events
```
  rows in
```
plot/timeline.md
```
  (sequel) or
```
Series Canon
```
  notes (prequel).
- ```
continuity/state.md
```
  starts at
```
current-chapter: 0
```
  with the carried character and object state. Carried knowledge goes in
```
knowledge-state
```
  without
```
learned-in
```
  , because the character already knew it when the book began.
- An artifact destroyed or lost in an earlier book keeps its
```
object-state
```
  entry with
```
status: destroyed
```
  (or
```
lost
```
  ) and no
```
since
```
  : that marks it gone before this story, so
```
story continuity
```
  errors on any scene whose
```
state-changes
```
  use it while still allowing
```
mentions
```
  .

只迁移新书实际使用的实体。对于每个实体，先从另一本书复制文件，然后进行调整：

保持文件名中的 id 完全一致。
```
story series
```
通过 id 匹配不同书籍中的实体。对检查器而言，重命名后的文件会被视为新实体。如果
```
story rename
```
警告该 id 也定义在关联书中，应同时在那里重命名，或保留旧 id。
保持
name
完全一致。将新的头衔或称谓放入
```
aliases
```
，例如在前传中用
```
General Maren
```
表示
```
Lord Maren
```
。不同的
```
name
```
会产生警告，不同的
```
pronunciation
```
也会产生警告。
根据本书的起点设置状态，而不是来源书的结局。
- 续集：从较早书籍最终的状态、关系、所有权和知识开始。
- 前传：从较早的情况开始，并在
```
## Series Canon
```
  部分将后续书籍的事实写为固定终点。
移除仅与来源书有关的引用。
```
died-in
```
、每个
```
progressions
```
条目的
```
from
```
以及其他所有章节 id 都指向来源书中的章节。将 frontmatter 设置为角色开始本书时的状态，并删除来源书的
```
progressions
```
。对于在本书开始前已通过
```
died-in
```
或状态进展死亡的角色，保留
```
status: deceased
```
，删除
```
died-in
```
，并且只在
```
mentions
```
中列出他们：如果
```
story continuity
```
发现他们出现在某章或场景出场名单中，就会发出警告。如果他们在本书中回归，请添加一条从该章节起状态转为
```
alive
```
的状态进展记录；此后，
```
story series
```
会允许他们实际出场。
修剪或迁移所有链接。 关系、
```
locations
```
、
```
notable-characters
```
、派系的
```
members
```
，以及物品的
```
owner
```
/
```
location
```
必须指向本书中存在的实体，并带有反向链接。应同时迁移关联实体，或删除相应引用。
不要复制章节、场景、情节弧、问题、承诺或
```
continuity/state.md
```
。应针对新书重新构建这些内容：
- 新书继续推进的未解决问题或承诺，在其
```
continuity/
```
  文件夹中创建新文件。
- 另一本书中的事件，在续集中成为
```
plot/timeline.md
```
  的 Backstory Events 条目，在前传中成为 Series Canon 注释。
- ```
continuity/state.md
```
  从
```
current-chapter: 0
```
  开始，并记录迁移后的角色和物品状态。迁移的知识放入
```
knowledge-state
```
  ，但不包含
```
learned-in
```
  ，因为角色在本书开始时已经知道这些内容。
- 在较早书籍中已经毁坏或遗失的物品，应保留其
```
object-state
```
  条目，设置
```
status: destroyed
```
  或
```
status: lost
```
  ，并且不设置
```
since
```
  。这表示该物品在本故事开始前就已消失，因此当场景的
```
state-changes
```
  使用它时，
```
story continuity
```
  会报错，但仍允许通过
```
mentions
```
  提及它。

Fact Ids

Fact ID

Give series-relevant knowledge a stable

fact

id in

continuity/state.md

, and use the same id in every book:

yaml

knowledge-state:
  - character: kael-voss
    knows: The gallery tunnel reaches the Whisper Gate
    fact: whisper-gate-route
    learned-in: chapter-04

Fact ids are kebab-case, and each character lists a given fact only once per book.
```
story continuity
```
checks both rules.
Add
```
learned-in
```
only in the book where the character discovers the fact on the page. In later books, carry the entry without
```
learned-in
```
. Do not put that rule in an inline comment: a command that rewrites the entry drops the comment.
Reuse the exact id in every book. The checker matches the character id plus the fact id, never the
```
knows
```
text.
Give ids to the reveals, secrets, and discoveries a later or earlier book depends on. Everyday knowledge does not need one.

After carrying entities, run in the new book:

shell

story reindex .
story wordcount . --write
story check .
story series .

在

continuity/state.md

中为与系列相关的知识分配稳定的

fact

id，并在每本书中使用同一个 id：

yaml

knowledge-state:
  - character: kael-voss
    knows: The gallery tunnel reaches the Whisper Gate
    fact: whisper-gate-route
    learned-in: chapter-04

Fact id 使用 kebab-case 格式，并且每个角色在每本书中只能列出某个给定 fact 一次。
```
story continuity
```
会检查这两项规则。
仅在角色于正文中发现该 fact 的书籍中添加
```
learned-in
```
。在后续书籍中，迁移该条目但不保留
```
learned-in
```
。不要把这条规则写在行内注释中，因为重写条目的命令会删除注释。
在所有书籍中复用完全相同的 id。检查器根据角色 id 与 fact id 进行匹配，而不会匹配
```
knows
```
文本。
应为后续或前序书籍所依赖的真相、秘密和发现分配 id。日常知识不需要 id。

迁移实体后，在新书中运行：

shell

story reindex .
story wordcount . --write
story check .
story series .

What

story series

Checks

story series

检查的内容

story series [path]

follows

follows

and

precedes

to every linked sibling book, orders the books by chronology, lists the canon they share, and reports deaths, casts, learned facts, and destroyed artifacts that contradict an earlier book, and names or pronunciations that drift from it. Errors exit 1. Fix each one in the book that breaks canon (in a prequel, the later book is canon), move a dead character's flashbacks and memories to

mentions

, and ask the user before changing an earlier book. Treat warnings as prompts to check the named files.

story series --help

describes the command and, when

story-maintenance

is installed, the series section of

../story-maintenance/references/continuity-checks.md

lists every error and warning and the order rules.

story links .

also checks the book's own series links: each path exists, has a matching backlink, and uses the same

series

id.

The checker cannot judge knowledge without fact ids, or ages, dates, travel time, or tone. Check those by reading both books' timelines and

Series Canon

notes.

story series [path]

会沿

follows

和

precedes

访问所有关联的同系列书籍，按故事时间线排序，列出它们共享的正典，并报告与较早书籍相矛盾的角色死亡、出场情况、已学事实和已毁物品，以及发生偏移的名称或发音。错误会导致退出码为 1。请在破坏正典的那本书中修复每个问题；对于前传，后续书籍才是正典。将已故角色的闪回和回忆改为放入

mentions

，并在更改较早书籍前征求用户同意。将警告视为检查相关文件的提示。

story series --help

会说明该命令；安装

story-maintenance

后，

../story-maintenance/references/continuity-checks.md

的 series 部分会列出每一种错误、警告及排序规则。

story links .

还会检查本书自身的系列链接：每个路径都存在、都有匹配的反向链接，并且使用相同的

series

id。

如果没有 fact id，检查器无法判断知识状态；它也无法判断年龄、日期、旅行时间或语气。请通过阅读两本书的时间线和 Series Canon 注释来检查这些内容。

Writing Against Canon

根据正典创作

Sequels: before drafting, reread the earlier book's final chapters,
```
continuity/state.md
```
, and every unresolved question or promise. Decide with the user which threads the new book picks up.
Threads left for the next book: a promise, question, or clue that pays off in a later book stays open in this one.
```
story continuity
```
warns about a planted promise or clue while drafting (the Chekhov gap:
```
promise-unpaid
```
or
```
clue-unpaid
```
) and about an open question once twelve drafted chapters follow its
```
introduced
```
chapter (
```
question-unanswered
```
). It errors once
```
story.md
```
is
```
complete
```
(
```
is still planted
```
,
```
is still open
```
). Record each deliberate one in this book's
```
continuity/exemptions.md
```
(the finding's
```
code
```
and
```
file
```
, such as
```
code: promise-unpaid
```
and
```
file: continuity/promises/the-sealed-letter.md
```
, or
```
code: question-unanswered
```
and
```
file: continuity/questions/who-kept-the-key.md
```
, plus a
```
reason
```
naming the book that pays it off; once
```
story.md
```
is
```
complete
```
the code is
```
complete-with-open-promise
```
or
```
complete-with-open-question
```
and the file
```
story.md
```
, so add a
```
pattern
```
naming the promise or question file) rather than marking it
```
paid-off
```
,
```
resolved
```
, or
```
dropped
```
, and add the matching file to the later book's
```
continuity/
```
folders.
Prequels: the later book is canon. Every fixed endpoint must still be reachable by the end of the prequel. Do not mark a character
```
deceased
```
who is alive in a later book. Do not give a character knowledge that the later book shows them learning for the first time. Before drafting, list the later book's
```
fact
```
ids that have
```
learned-in
```
, and keep those facts out of the prequel's knowledge.
Revising an earlier book after later books exist: run
```
story series .
```
before and after the revision. Update the later books'
```
Series Notes
```
and carried entity files when canon changes.

续集： 起草前，重新阅读较早书籍的最后几章、
```
continuity/state.md
```
，以及每个未解决的问题或承诺。与用户决定新书承接哪些情节线。
留给下一本书的情节线： 如果一个承诺、问题或线索将在后续书籍中兑现，它必须在本书中保持开放。起草期间，
```
story continuity
```
会警告尚未兑现的伏笔或线索（契诃夫式空缺：
```
promise-unpaid
```
或
```
clue-unpaid
```
）；当一个开放问题的
```
introduced
```
章节之后又写了十二章时，它也会发出警告（
```
question-unanswered
```
）。当
```
story.md
```
标记为
```
complete
```
后，它会报错（
```
is still planted
```
、
```
is still open
```
）。应将每个有意保留的项目记录在本书的
```
continuity/exemptions.md
```
中，包括检查结果的
```
code
```
和
```
file
```
，例如
```
code: promise-unpaid
```
和
```
file: continuity/promises/the-sealed-letter.md
```
，或
```
code: question-unanswered
```
和
```
file: continuity/questions/who-kept-the-key.md
```
，并添加一个指明兑现该内容的书籍的
```
reason
```
；当
```
story.md
```
为
```
complete
```
时，
```
code
```
应为
```
complete-with-open-promise
```
或
```
complete-with-open-question
```
，
```
file
```
应为
```
story.md
```
，并添加一个指明承诺或问题文件的
```
pattern
```
。不要将其标记为
```
paid-off
```
、
```
resolved
```
或
```
dropped
```
，并应将匹配的文件添加到后续书籍的
```
continuity/
```
文件夹中。
前传： 后续书籍是正典。每个固定终点在序章结束前都必须仍然能够到达。不要将一个在后续书籍中仍然存活的角色标记为
```
deceased
```
。不要赋予角色后续书籍显示其首次学到的知识。起草前，应列出后续书籍中带有
```
learned-in
```
的
```
fact
```
id，并将这些事实排除在前传角色的知识之外。
在后续书籍已经存在时修订较早书籍： 修订前后都要运行
```
story series .
```
。正典发生变化时，更新后续书籍的 Series Notes 和迁移的实体文件。

Maintenance

维护

After any change to series links or carried entities, run the checks in each affected book:

shell

story reindex .
story wordcount . --write
story check .
story series .

story

is not installed, use the bundled fallback

node ../story-maintenance/scripts/story.js

with the same arguments. Use

node <checkout>/bin/story.js

instead only when the user names a Story Skills repository checkout or you are working in one. Write the script as an absolute path (resolve the fallback relative to this skill folder) and run it from the folder you would run

story

from, so

and other relative paths keep their meaning. Use Node, not Bun or a package script: Bun would load that folder's

bunfig.toml

(which can run code) and

.env

, and a package script runs from the checkout's root.

更改系列链接或迁移实体后，应在每个受影响的书籍中运行以下检查：

shell

story reindex .
story wordcount . --write
story check .
story series .

如果未安装

story

，请使用内置的回退脚本

node ../story-maintenance/scripts/story.js

，并传入相同参数。只有当用户指定了 Story Skills 仓库检出目录，或者你正在该目录中工作时，才应改用

node <checkout>/bin/story.js

。脚本路径应写为绝对路径（相对于此 skill 文件夹解析回退路径），并从原本运行

story

的文件夹中执行，这样

和其他相对路径才能保持原有含义。请使用 Node，不要使用 Bun 或 package script：Bun 会加载该文件夹中的

bunfig.toml

（其中可以运行代码）和

.env

，而 package script 会从检出目录的根目录运行。

Conventions

约定

One project folder per book, with books side by side in a shared parent folder
```
series
```
ids are kebab-case and identical in every book
Entity ids and
```
name
```
values stay stable across books; variants go in
```
aliases
```
Chronology goes in
```
follows
```
/
```
precedes
```
, publication order in
```
book-number
```
Every link needs a matching backlink in the other book

每本书使用一个项目文件夹，同系列书籍并排放在共享的父文件夹中
```
series
```
id 使用 kebab-case 格式，并在所有书籍中保持一致
实体 id 和
```
name
```
值在不同书籍间保持稳定；变体放入
```
aliases
```
故事时间线记录在
```
follows
```
/
```
precedes
```
中，出版顺序记录在
```
book-number
```
中
每个链接都需要另一本书中的匹配反向链接

Reference Files

参考文件

references/series-bible.md
- Where each part of a series bible lives across the linked books, writing
```
Series Notes
```
, keeping canon current, planning a multi-book series, and pitching one (query line and
```
submission/series-pitch.md
```
template)

references/series-bible.md
- 系列圣经的各部分如何分布在关联书籍中，如何编写 Series Notes、保持正典同步、规划多书系列，以及如何进行推介（query 条目和
```
submission/series-pitch.md
```
模板）

Shared Conventions

共享约定

Every story skill follows the shared conventions in

../story-maintenance/references/conventions.md

, resolved relative to this skill folder. Read it before creating, renaming, or linking story files. If that file is missing because this skill was installed without

story-maintenance

, the essentials are: kebab-case ids and filenames, YAML frontmatter on every story-project file,

_index.md

registry tables that

story reindex

rebuilds (never edit them by hand), bidirectional links between entities,

characters

for who is on the page and

mentions

for who is only referred to,

status: deceased

plus

died-in: chapter-{NN}

for deaths, and no project-local generator or build scripts (run only the installed or bundled Story CLI).

每个 story skill 都遵循

../story-maintenance/references/conventions.md

中的共享约定，该路径相对于此 skill 文件夹解析。在创建、重命名或关联 story 文件前，应先阅读该文件。如果安装此 skill 时未同时安装

story-maintenance

，导致该文件不存在，则需要了解以下要点：id 和文件名使用 kebab-case 格式；每个 story 项目文件都包含 YAML frontmatter；

_index.md

注册表表由

story reindex

重建（绝不要手动编辑）；实体之间使用双向链接；

characters

用于实际出场的角色，

mentions

用于仅被提及的角色；死亡记录使用

status: deceased

，并搭配

died-in: chapter-{NN}

；项目中不得包含本地生成器或构建脚本（只能运行已安装或内置的 Story CLI）。

series-continuity

Original

Translation

Series Continuity

系列连续性

Overview

概述

When to Use

使用场景

Starting a Linked Book

开始创建关联书籍

Sequel: set after book one

续集：发生在第一本书之后

Prequel: set before book one

前传：发生在第一本书之前

Companion: set alongside book one, with no chronology link

伴随作品：与第一本书同时发生，不建立时间线关联

Carrying Canon Across Books

在书籍之间迁移正典

Fact Ids

Fact ID

What
`story series`
Checks

`story series`
检查的内容

Writing Against Canon

根据正典创作

Maintenance

维护

Conventions

约定

Reference Files

参考文件

Shared Conventions

共享约定