fanqie-novel-factory

name	fanqie-novel-factory
description	Create, plan, draft, revise, and maintain Chinese web novels for Fanqie-style category writing. Use when the user wants 番茄小说题材定位, 分类适配, 脑爆, 爽点设计, 书名简介, 故事圣经, 人设表, 分卷大纲, 章节细纲, 正文连载, 续写, 爆款开篇, or continuity files across male-frequency, female-frequency, suspense, fantasy, urban, historical, romance, sci-fi, game, sports, fanfiction, and short-story lanes.

Fanqie Novel Factory

Overview

Use this skill to turn a vague Chinese web-novel idea into a durable Fanqie-style serial project. The default workflow is:

脑爆 -> 分类定位 -> 读者承诺 -> 故事圣经 -> 分卷/章节大纲 -> 正文试写 -> 连载记忆维护 -> 复盘改稿

Borrow the continuity discipline and historical plausibility habits from historical-novel-writer, but generalize them across all major Fanqie-style shelves.

First Decision

Before planning or drafting, classify the project:

• Male-frequency power engine: upgrade, survival, money, rank, combat, investigation, war, system, or institutional build-up.
• Female-frequency emotional engine: relationship pressure, identity reversal, family/social constraint, career pressure, rebirth correction, rescue, or self-growth.
• Suspense/case engine: truth, clue, suspect, danger, reveal, and long-arc secret.
• Worldbuilding engine: rules, power system, factions, map, resources, races, technology, or apocalypse ecology.
• Reality engine: workplace, family, school, era, profession, sports, entertainment, farming, food, medicine, or business operations.

State the chosen shelf and subcategory when it changes the writing strategy. If the user gives no category, choose 2-3 plausible categories and explain the tradeoff in terms of reader promise, not only tags.

For detailed shelf routing, read references/taxonomy.md. For genre-specific levers, read references/category-playbooks.md. For file templates and maintenance rules, read references/project-files.md.

Core Workflow

1. Brainstorm wide: generate 8-20 premise seeds around the user's taste, protagonist type, opening crisis, repeated pleasure, and monetizable long-form engine.
2. Pick the shelf: map each seed to Fanqie-style category lanes and reject mismatches where the premise promise fights the expected reader pleasure.
3. Define the reader promise: name the repeated emotional or爽点 return: revenge, upgrade, rescue, solving, healing, face-slapping, survival, empire-building, sweet tension, forbidden desire, or mystery reveal.
4. Build the story bible: premise, category lane, protagonist contradiction, cast, world/rules, power or relationship engine, volume arc, forbidden shortcuts, style rules, and continuity files.
5. Create a chapter engine: each chapter changes leverage, danger, relationship temperature, clue state, resource position, or public reputation.
6. Draft near pressure: open scenes with a problem in motion: divorce agreement, failed awakening, body found, debt collector, imperial edict, failed exam, viral scandal, monster breach, contract clause, match point, or mission countdown.
7. Maintain memory: after substantial drafting, update project files for canon, open hooks, character state, timeline, resources, clues, relationship temperature, and next-chapter handoff.
8. Review for platform fit: check hook density, category promise, protagonist appeal, chapter ending, AI-flavor risk, and whether the next chapter has a concrete reason to exist.

Brainstorming

For a new project, produce a short-list table:

• Seed
• Shelf / subcategory
• Reader promise
• Opening crisis
• Protagonist edge
• Long-form engine
• Commercial risk
• How to sharpen

Favor premises with an engine that can generate 100+ chapters without repeating the same emotional beat. Avoid concepts that only have a twist but no chapter machine.

Use these levers:

• Status gap: low status -> earned leverage.
• Information gap: protagonist knows, hides, proves, or discovers what others misread.
• Resource gap: money, troops, evidence, contract, grain, energy, followers, family backing, or public trust.
• Relationship gap: desire versus duty, protection versus autonomy, debt versus love, public role versus private need.
• Rule gap: a hidden system, school rule, game mechanic, cultivation rule, legal loophole, family custom, or apocalypse survival law.

Story Bible

When the user asks for a bible, create or update:

• Core pitch: title directions, category, hook, reader promise, target tone, and comparable shelf logic.
• Protagonist bible: identity, contradiction, visible flaw, desire, fear, edge, cost, growth line, and forbidden shortcut.
• Relationship/cast bible: allies, rivals, love interest, family, mentors, enemies, debts, secrets, boundaries, and speech patterns.
• World/rule bible: setting, power system, institutions, economy, map, technology/magic limits, platform-specific genre rules.
• Plot bible: whole-book stages, volume arcs, chapter clusters, key reversals, foreshadowing, payoff plan, and ending direction.
• Style bible: narrative distance, prose register, banned phrases, chapter length, cliffhanger style, dialogue texture, and no-AI filter.

Keep canon separate from suggestions. Mark unclear facts as Question, planned additions as Proposal, and established facts as Canon.

Category Adaptation

Use the category to adjust the same workflow:

• 玄幻/仙侠/都市异能/科幻末世: rules before scale. Define costs, bottlenecks, resource loops, enemy adaptation, and visible upgrades.
• 都市/神豪/职场/娱乐圈: money, reputation, contracts, public narrative, social hierarchy, and practical workflow must create pressure.
• 历史/种田/年代: use logistics, titles, geography, policy, household economy, kinship, and era constraints; read historical-novel-writer if strict history matters.
• 悬疑/灵异/规则怪谈: design truth before clues; every reveal should reinterpret earlier details, not replace them.
• 现言/古言/青春/女强: center desire under material pressure; relationship progress must change behavior, risk, status, or self-knowledge.
• 游戏/体育/二次元/同人: define rules, match/mission loops, skill ceilings, fan-service boundaries, and progression metrics.
• 短故事: compress the engine into one strong reversal or emotional payoff; do not build a 300-chapter machine unless the user asks to expand.

Drafting Rules

For chapters:

• Start close to disturbance, not biography.
• Give each scene one clear external objective.
• Let exposition appear through object, action, consequence, and only then explanation.
• End on changed leverage: new debt, clue, order, wound, suspicion, promise, contract, enemy move, resource loss, confession, or public consequence.
• Preserve human texture: friction, partial misunderstanding, habits, awkward details, and practical cleanup.

Avoid:

• generic lines like "命运的齿轮", "眼底闪过一丝", "空气凝固", "真正的故事才刚刚开始";
• omniscient protagonist wins without setup, cost, or opponent response;
• smooth AI summaries where every conflict is immediately explained;
• repeating the same face-slapping, jealousy, upgrade, or clue rhythm without changing stakes.

Review Gate

After a premise, bible, outline, or chapter, score 1-10:

• Opening Hook
• Category Fit
• Reader Promise
• Protagonist Appeal
• Long-form Engine
• Scene Pressure
• Freshness
• Continuity
• AI Flavor Risk

Pass only if average is at least 8.0 and no required dimension is below 7.0. For suspense, logic/clue fairness must pass. For romance, emotional causality must pass. For fantasy/sci-fi, rule cost and progression clarity must pass.

Project Files

When maintaining a novel project, create or update files described in references/project-files.md. Minimum recommended set:

• story-bible.md
• category-positioning.md
• character-bible.md
• world-rules.md
• outline-book.md
• outline-volume-<n>.md
• open-threads.md
• continuity-log.md
• style-guide.md

Do not overwrite existing project files blindly. Read active memory files and the previous chapter before continuing an ongoing novel.