novel-lessons-20260725

Documents web novel writing lessons and platform rules for Fanqie serialized fiction.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/cwjdong-design/novel --skill novel-lessons-20260725-cwjdong-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: novel-lessons-20260725
Source: https://github.com/cwjdong-design/novel/tree/main/novel-lessons-20260725
Command: npx skills add https://github.com/cwjdong-design/novel --skill novel-lessons-20260725-cwjdong-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web novel authors on the Fanqie platform repeatedly lose readers due to slow pacing, missing payoff moments, and AI-generated chapters that invent unauthorized place names, numbers, and system panel formats. This Skill consolidates hard-won lessons into enforceable writing rules. ## Core Features & Use Cases - Platform Pacing Rules: Codifies reader-retention requirements such as payoff within 3 chapters, at least 3 satisfying moments per chapter, and strong hooks at ad-break chapters 3/6/9. - AI Dispatch Guardrails: Defines chapter-by-chapter dispatch, file-based parameter passing, and output scanning rules to prevent Claude opus from inventing names, numbers, or panel formats. - System-Panel Discipline: Specifies allowed bracket-style static data panels versus forbidden game-like borders and dynamic indicators, plus data-to-action closure rules. - Use Case: When drafting a new chapter of a system-flow web novel, consult these lessons to verify pacing, panel formatting, and dispatch strategy before and after generation. ## Quick Start Review the lessons in this skill before drafting the next chapter to check pacing, system panel format, and dispatch rules.

Frequently Asked Questions about novel-lessons-20260725

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep readers from dropping my web novel in early chapters?

Deliver a satisfying payoff within the first 3 chapters and include at least 3 payoff moments per chapter. End chapters 3, 6, and 9 with strong hooks such as information cutoffs or countdowns to survive ad-break drop-off.

How to dispatch Claude Code for multi-chapter novel writing?

Dispatch one chapter per claude -p call and never batch multiple chapters, since opus typically outputs only the first chapter. Pass content via files rather than inline arguments, and save output directly to disk.

What system panel format is allowed in system-flow web novels?

Use bracket-style static data fields only, with fixed fields defined in the book configuration. Forbidden elements include box-drawing borders, dynamic percentage changes, cycle states, and payback period estimates.

Why does AI-generated novel text invent fake place names and numbers?

The model's memory resets each conversation, so ironclad rules must be re-injected every dispatch. Always scan opus output automatically before human review to catch invented locations, ages, and system functions.

When should new system data dimensions appear in a story?

Introduce a new data dimension every 2-3 chapters, and each one must trigger an immediate protagonist action forming a closed loop. At least 85 percent of data popups across the book must drive action rather than passive reflection.