ZenStory AI

Practical guide · 实用指南

Keep your author voice when AI continues a novel

AI 续写怎样保持我的文风，而不是记住另一本书的情节？

Source checked 2026-09-12 · 源码核对日期

Describe the dimensions of your voice, give a short sample you own or may use, and separate those choices from the current book’s facts. Oh Story’s documented workflow resolves the current request, book style and relevant active author preferences before generic writing advice; a sample alone does not establish a permanent preference. The useful result is a continuation that fits this narrator and scene—not copied phrases, mandatory short sentences or a claimed voice-similarity score.

把文风拆成表达维度，提供自己写的或获准使用的短样本，再与本书事实分开。Oh Story 的文档流程在写作前按当前要求、本书文风和相关 active 作者偏好作裁决，通用写法补缺；仅凭一段样本，不等于确认长期习惯。目标是符合当前叙述者和场景的续写，不是搬原句、强制短句，或追求“文风相似度”分数。

Oh StorySource on GitHub

Before you start · 开始之前

Steps · 操作步骤

  1. Ask what makes the sample yours Name a few useful tendencies: a long observational sentence followed by a brief exchange, understated humor, close third person, or a restrained vocabulary. Explain their function here. Do not require a semicolon, metaphor or catchphrase in every paragraph.
  2. Separate three kinds of input Sample observations are evidence to discuss, not automatically active memory. The current book’s characters, objects, secrets and events belong to its settings and tracking. An explicit enduring preference can be recorded at the narrowest intended scope: book, genre, workflow or global. A request for this passage only should simply be followed.
  3. Resolve conflicts by dimension Within safety, authorization and delivery constraints, the explicit current request outranks this book’s style, which outranks applicable author-memory preferences and generic references. Resolve viewpoint, rhythm, punctuation and other dimensions separately: keep the sample’s rhythm while using this book’s third person. Lower-priority guidance fills gaps; it does not cancel an intentional long sentence merely because a default prefers short ones. Read the current book’s full 设定/文风.md when present, rather than relying only on an old summary; an absent style file does not require a placeholder.
  4. Carry the same decision through drafting and review Oh Story’s style_resolution is a working decision for the task, not a new permanent author profile. The documented workflow passes the same decision to downstream drafting, rewriting and review so a later pass does not restore a generic style. Intentional expression still needs readable syntax, supported character knowledge and sound causality. The query script filters stored active preferences; the writing agent applies their meaning and resolves dimensions. It is not a deterministic voice-matching engine.
  5. Treat memory as an explicit scoped action Repeated corrections or inferred sample patterns remain pending until confirmed; pending items do not constrain writing. An explicit long-term request uses record and returns an Author Memory Receipt. Without that receipt, do not say it has been remembered. A book-specific exception should not erase a global habit, and a one-off request should not silently rewrite either.
  6. Revise the preference when your intention changes Use an explicit replacement for a changed rule, or ask to forget a preference so it is no longer loaded. Forgetting does not promise deletion of historical evidence. The profile, pending list and change log are derived views of _author-memory-state.json; do not edit their Markdown to simulate a successful memory update.
  1. 先说样本哪里像你 提取少数有用倾向：观察稍长、对话简短、轻微调侃、贴近人物的第三人称，或克制的用词，并说明这次为什么要它。不要要求每段必须有分号、比喻或口头禅。
  2. 把三类输入分开 从样本观察到的模式只是待讨论证据，不自动成为 active 记忆。本书人物、道具、秘密与事件归设定和追踪；明确的长期偏好按本书、题材、流程或全局等适用范围记录。“只改这一段”则只执行，不偷偷记成习惯。
  3. 按表达维度解决冲突 在安全、授权和交付约束之内，当前明确要求优先于本书文风，再到适用的作者记忆和通用方法。视角、节奏、标点分别裁决：可以借样本的节奏，仍用本书第三人称。低优先级只补缺项，不能因默认偏好短句就剪掉作者有意保留的长句。 本书有设定/文风.md 时读全文，不只用旧摘要；没有文件也不必先建占位文件。
  4. 让写作和审稿沿用同一决定 style_resolution 是本次任务的表达裁决，不是新建永久画像。文档要求把同一裁决交给后续正文、改写与审稿，避免下一轮又套回通用风格；但有意的表达仍需语句可读、角色认知有据、因果成立。 query 脚本负责筛选已存的 active 偏好，语义上的维度裁决由写作流程中的 Agent 完成，不是确定性的文风匹配引擎。
  5. 记住偏好，要明确范围和回执 重复修改或样本推断先待确认；pending 不参与正文约束。明确的长期声明通过 record 记录，并返回 Author Memory Receipt；没有回执，不能声称已记住。本书例外不应删除全局习惯，一次性要求也不应暗改两者。
  6. 意图变了，再替换或停用 长期规则改变时明确替换；不再需要时要求忘掉，使其不再加载。“忘掉”不等于删除历史证据。画像、待确认清单与变更记录是 _author-memory-state.json 的派生视图，不手改 Markdown 冒充记忆更新。

Example · 示例

Original editorial example — The Last Button (not a recorded Oh Story run)

A short sample written for this guide, from a DIFFERENT story:
“After lunch, Father turned his empty bowl halfway around, as though the other side might still hold some soup; when I offered the kettle, he left it in my hand and asked whether the mint by the window needed watering again.”
Possible observations: an extended sentence, a semicolon turn, concrete observation and mild humor. These are tentative observations, not proof of an enduring preference. Father, soup, the first-person narrator and the mint plant do not belong to the new book.

Facts fixed for The Last Button:
Third person, close to Tang He. Master Zhou puts a matching dark-green button in her palm and says the repair cannot be finished today, but will be ready tomorrow morning. Tang He holds the button against the gap on her coat and checks the color. Do not add a family history, a hidden relationship or another character’s thoughts.

A plain, shorter rendition—not an incorrect draft:
“Master Zhou put the dark-green button in Tang He’s palm. ‘Not today. Come back tomorrow morning.’ She held it against the gap on her coat. The color matched.”

One alternative after the author chooses a longer rhythm and mild humor for THIS BOOK:
“Master Zhou put the dark-green button in Tang He’s palm and said the repair would have to wait until tomorrow morning; she held it against the gap on her coat, where the color matched so exactly that it was a pity buttons could not sew themselves back on.”
Both versions preserve the same actions and deadline. The second changes cadence and commentary, not the plot. It does not transplant the sample’s bowl, mint, father or first-person viewpoint. This is one editorial option, not a measured likeness or a guarantee of consistent model output.

Copyable request for story-long-write in your configured host:
Use the authorized sample only to discuss expression, not to copy sentences or transfer its story facts. Work only on the specified passage of The Last Button; preserve the fixed actions, tomorrow-morning deadline and close-third viewpoint. For this book, I want longer observational sentences and mild humor where they help; do not add them to every paragraph. First state the applicable style decisions, then return one proposed passage without changing project or memory files. Distinguish tentative sample observations from my explicit choices. Carry the same decisions into review; do not mechanically shorten the passage.

Optional SEPARATE enduring request, only if this is really your intention:
“Remember for The Last Button: allow longer observational sentences and mild humor where they help. This is a book-specific preference, not a global rule.”
This is an example request, not a receipt. No preference has been recorded by this guide. A later ‘make this one paragraph brisk and factual’ request governs that paragraph without silently replacing the book preference.
原创编辑示例——《最后一枚纽扣》（不是 Oh Story 运行结果）

为指南写的短样本，来自另一个故事：
“午饭过后，父亲把那只空碗转了半圈，像是换个方向就能找到还没喝完的汤；我把水壶递过去，他没有接，只问窗边那盆薄荷是不是又该浇水了。”
可讨论的观察：句子较长、分号转折、具体观察、轻微调侃。这些只是候选，不证明长期习惯。父亲、汤、第一人称和薄荷都不是新书的设定。

《最后一枚纽扣》的约定事实：
第三人称，贴近唐禾。周师傅把配好的深绿纽扣放到她掌心，说今天来不及，明早可以取。唐禾把纽扣贴在外套衣襟缺口上，核对颜色。不新增身世、隐秘关系或他人的内心。

朴素短句版——不是错稿：
“周师傅把深绿纽扣放到唐禾掌心。‘今天来不及了，明早来取。’唐禾把纽扣贴到衣襟缺口上，颜色一致。”

作者为本书选择较长节奏与轻微调侃后的一种写法：
“周师傅把那枚深绿纽扣放到唐禾掌心，说今天已经赶不及，明早可以取；她低头把纽扣贴在衣襟缺口上，颜色倒是对得一丝不差，只可惜纽扣不会自己长回去。”
两版行动和期限相同，改变的是节奏与叙述语气，不是剧情。没有搬来原样本的碗、薄荷、父亲和第一人称。这只是一种编辑选择，不是相似度成绩或稳定复现的保证。

向已配置宿主中的 story-long-write 提交：
样本是我有权使用的，只讨论表达，不复制原句或移植情节。仅处理《最后一枚纽扣》的指定段落，保留上述动作、明早期限与贴近唐禾的第三人称。本书可以用较长观察句和轻微调侃，但有用时才用，不必每段都有。
先说明本次各维度的表达决定，再给一版段落建议；不改项目文件，不写作者记忆。分清样本推测和我的明确选择，审稿沿用同一决定，不机械剪短。

确实希望长期沿用时，再单独提出：
“记住：仅《最后一枚纽扣》这本书，允许有用的较长观察句与轻微调侃，不设为全局规则。”
这是示例请求，不是记忆回执；本指南没有替你记录任何偏好。以后若说“这一段写得短促、客观”，本段按新要求写，不暗改本书长期偏好。

Expected files · 预期文件

Verify the result · 验证结果与边界

Sources and version notes · 来源与版本说明