expand

Main text expansion (expand)

Turn a chapter outline into publishable main text, controlling pacing, payoff moments, word count, and hooks.

When to use

Turn a chapter outline/detailed outline into main text
Expand or continue a chapter
Expand a one-sentence plot into a complete scene

Confirm before writing

Person：Default first person "I"(more immersive, like writing personal experience, especially Zhihu/female-oriented/short stories). Before starting,state in one sentence"By default I write in first person; tell me if you want third person"; if the user specifies third person, use third. Keep the person consistent throughout the book. (Call references/pov-guide.md）
Chapter outline/plot points: what should happen in this chapter (if not, first use outline to produce a chapter outline)
Platform + word count: single-chapter density, call references/platform-profiles.md（Fanqie long-form serialization: 2000–2200 words per chapter is optimal, Qidian 2000–3000); how far the whole book still is from the signing/distribution threshold, call references/length-standards.md
Character profile + language fingerprint: retrieve the speech_profile of characters appearing in this chapter, inject it for comparison, and ensure the characters' "voices" are consistent, not OOC, and not all sounding alike (see skills/dialogue、project-memory.md section seven)
Continuity with what came before: the hook at the end of the previous chapter should be addressed at the beginning of this chapter; for long works, also check whether the timeline/resources/injuries/combat power connect (see skills/continuity）

Writing essentials

Pacing

Start by connecting the hook: the first paragraph should respond to the previous chapter's suspense or immediately enter the scene; do not drag
Scene progression: alternate dialogue + action + inner thoughts; avoid long stretches of narration
Land the payoff: the payoff moments planned for this chapter must be written fully (call references/trope-library.md); for face-slapping, use the four beats "mockery → silence → crushing → onlookers"
End with a chapter hook: close with a chapter-end hook at the ending (call references/hook-library.md）

Text

Short sentences, fast pace: web fiction avoids long, difficult sentences; use short sentences and dialogue to drive it forward
Visual sense: use concrete details instead of abstract descriptions ("He clenched his fist, knuckles turning white" rather than "He was very angry")
Show emotion, don't shout it: avoid "I'm so heartbroken/I'm in so much pain"; use expression/action/physiological reactions/subtext to let readers feel it themselves (call references/show-emotion.md, for specialized use switch to emotion skill)
Make the satisfaction external: write out the points readers want to feel satisfied about—expressions, onlookers' reactions, the opponent's embarrassment
Avoid AI tone: do not pile up parallelism and empty lyricism; after writing, you can use deslop to check
Clean punctuation: simplified Chinese web fiction uses only conventional punctuation (。，、？！…… curly quotes ""''). Dialogue usescurly double quotes ""，do not use corner brackets 「」『』；em dash——used extremely rarely(at most once per chapter); do not scatter decorative symbols like ✦✨◆★; separate scenes with blank lines; chapter titles are plain text (see references/anti-ai-checklist.md section seven for details)
Leave a bit of a sense of losing control (human touch): Don't write too evenly, too cleanly, too smoothly—at key points give an irrational behavior, an unfinished emotion, or a passage of unresolved blank space, so it feels like an "emotional record" rather than an "instruction manual" (deep adjustment human skill / references/human-texture.md）
Sentence patterns have breathing room: Sentence lengths are uneven, short and long sentences alternate, occasionally throw in a 50+ character long sentence; use ellipses/em dashes/line breaks for pauses, don't be uniformly neat (adjust references/sentence-rhythm.md）
Can produce dual versions: When the user asks, give two drafts: a "satisfying read version (high emotion/satisfying twists)" + a "premium dark version (extreme/gray areas/leaving the knife)" (adjust references/dark-style.md); if not requested, default to a single version

Dialogue

Each character speaks differently (reflects their characterization)
Dialogue advances the plot or reveals information, no idle chatter
Leave appropriate blank space, don't explain every line
Colloquial, with subtext, avoid a written AI tone (adjust references/dialogue-library.md); to specifically polish dialogue/punch lines → use the dialogue skill

Output

Directly produce the main text (markdown), title + body
Word count close to the target
The ending comes with a chapter-end hook
After writing, briefly describe: what the chapter's satisfying points are, which hooks were planted/resolved, and the word count

Coherence

For long works, every few chapters: use review to check reader retention (hooks/satisfying points/foreshadowing), use continuity to verify whether logic/timeline/resources/identity/injuries/combat power are contradictory before and after
For important settings/character status/time progression/combat power changes, prompt the user immediately after writingupdate the file（memory), otherwise the next chapter will keep drifting

Next step

If the main text has an AI flavor → deslop(quantitative scoring to locate → aidetect); if there aren't enough satisfying points → shuangdian; to check retention → review; to check logic/timeline → continuity。