Tomato Web Novel Creation Master

Problem

Creating Tomato-style web novel chapters is easy to handle by feel, but hard to keep consistent: each chapter needs 2200-2800 words, dialogue balance, a strong opening, and an ending hook; foreshadowing can be missed across chapters; AI-sounding phrases, tell-heavy narration, and platform-sensitive terms often appear late.

How the skill works

Tomato Web Novel Creation Master turns the writing project into files and CLI steps:
- Project setup: generates confirmation archives, chapter TODOs, a three-act outline, and a foreshadowing table
- Pacing control: follows a 3-chapter emotion loop, climax distribution, and a pool of 10 hook templates
- 9-dimension QC: scores word count, AI-flavor terms, dialogue ratio, paragraph length, opening conflict, ending suspense, golden lines, and sensitive words
- Foreshadowing tracking: stores structured F IDs, planted chapters, payoff chapters, and cross-chapter status; warns when items remain unrecovered for a long time
- Review and export: produces a 5-chapter quality trend and foreshadowing stats, then cleans chapter templates and exports TXT / MD

Boundaries

It is better suited to Chinese Tomato-style chapters with short-drama pacing, not general long-form novels or automatic publishing. Sensitive-word checks are coarse filters, and the QC score is rule-based, so authors still need to verify facts, copyright, and final quality.