memory

Creation Archive and Memory System (memory)

Give each book a set ofpersistent memory: settings, characters, outlines, foreshadowing, inspiration, progress, and submission records are all stored in the book's folder, and are not lost across sessions.Like git, it can make version snapshots and review "where did I write up to".

When to use

• Record/save outlines, character settings, worldbuilding, to continue using next time
• Come back after a few days to continue writing: "Where did I write up to last time?"
• Check "has this foreshadowing been paid off" "what realm is the protagonist at now"
• Make version snapshots and rollbacks for a book
• Manage the progress of multiple books

Archive structure (the book's "memory")

Maintain this set of files in the book's folder (if there are none, initialize with this skill):

《书名》/
├── 00_设定.md        立项卡 + 金手指 + 世界观 + 势力库 + 战力体系（book-bible）
├── 01_人物.md        人设卡 + 当前状态 + 语言指纹 + 情绪/关系轨迹 + 弧线
├── 02_大纲.md        卷纲 / 章纲
├── 03_伏笔追踪.md     埋点 → 回收 表（编号/重要度，防烂尾命脉）
├── 04_灵感本.md       spark 速记的灵感
├── 05_进度.md        写到第几章 / 累计字数 / 下一步
├── 06_投稿记录.md     每次投稿：平台/日期/结果/拒因/改动
├── 07_时间线.md       主时间线 + 知情人名单 + 世界状态（长篇防失忆）
└── 正文/
    ├── 第001章.md
    └── ……

Short stories can use only 00/01/02;full-length works must add 07_timeline and power system, together with continuity to prevent settings from collapsing when writing to hundreds of chapters. For templates see templates/book-bible-template.md、templates/submission-log-template.md、templates/progress-template.md; for formats see references/project-memory.md。

Four functions

1. Create archive (init)

Create the above archive structure for a new book, filling in existing information from templates (calling the output of idea/outline/character ).

2. Review and continue writing (resume)

Read 05_进度.md + 02_大纲.md + 03_伏笔追踪.md + 01_人物.md，report in one sentence：

《书名》写到第 N 章（累计 X 万字）
上一章结尾钩：……（本章要回应）
待回收伏笔：……
主角当前状态：……
下一步建议：写第 N+1 章，本章大纲是……

Solves "forgot where I wrote up to after a few days".

3. Update (update)

After finishing/revising, sync the archive:

• Finished a chapter → update 05_进度.md(chapter number/word count/next step)
• New foreshadowing/paying off foreshadowing → update 03_伏笔追踪.md
• Character status changes (level-up/relationships/acquired items/injuries) → update 01_人物.md
• Emotion/relationship value changes, character arc advancement → update 01_人物.md emotional trajectory (to prevent "just broke up but laughing happily next chapter")
• Time advancement / who learned what secret / world state changes (war/destruction/faction turnover) → update 07_时间线.md
• Power changes (realm breakthrough/new powerful enemy appears) → update 00_设定.md power comparison
• New inspiration → append 04_灵感本.md

If you don't write back, "the next chapter will keep drifting"—this is the closed loop that prevents amnesia. To proactively check for contradictions before and after, use continuity; for strongly setting-driven genres, build the world first with world。

4. Version snapshots (like git)

Two methods, recommend according to the user's situation:

• Real git (recommended, can roll back and view history): in the book's folder git init, after each finalized chapter git add . && git commit -m "第N章定稿". This skill can execute it on your behalf. To return to an old version git log + git checkout。
• Lightweight snapshots (without git): copy key files into dated versions, such as 02_大纲_2026-06-05.md, retaining historical versions.

Principles

• The archive is thesingle source of truth: read the archive before writing the main text, and must update after writing, to avoid setting drift.
• 03_伏笔追踪.md is the lifeblood for preventing a bad ending, and must be checked and updated every chapter.
• Multiple books each have their own independent folder and do not interfere with each other.
• Involves private/unpublished manuscripts; a reminder has already been .gitignore excluded, so it will not be mistakenly transmitted to the public repository.

In coordination with

• spark writing the inspiration notebook,outline writing the outline,character writing characters (including language fingerprints),submission writing submission records — this skill manages the review and versioning of these archives.
• continuity reading this archive to verify logic/timeline/power-level consistency — memory is responsible for "recording", while continuity is responsible for "verifying".
• Full-book length/word-count planning → references/length-standards.md。