Writing Craft and Style Guide
Responsible for providing authors and other writing skills with actionable narrative techniques, chapter playbooks, genre-blend approaches, and guiding the creation or calibration of a per-book bible/style-guide.md.
When to Use / When Not to Use
When to use:
- Stuck on a specific paragraph and need actionable techniques for scene, pacing, dialogue, information delivery, dual-line structure, atmosphere, or specific chapter types (preparation, action, loot/trade, rulebook).
- Designing a blended-genre narrative voice (e.g., using a rational system's language to describe a fantasy system), or researching common tropes and pitfalls for a specific genre.
- Drafting initial
bible/style-guide.mdfor a new book, or reverse-engineering an author's personal style from 2–3 existing chapters to solidify a team-wide voice. - Receiving a cross-reference from
fiction-chapter,fiction-review, orfiction-plannerthat requires reading a specific technique document or genre pack.
When not to use (delegate to sibling skills; if a downstream skill is absent, only deliver the products of this step, a to-do list, and unchecked items—do not overstep):
- To complete a full new chapter drafting loop, write a chapter outline, perform a full structural rewrite, or back-write after a chapter: delegate to
fiction-chapter(if not installed, only deliver technique adjustments and chapter to-do items, noting that the full drafting and back-writing loop was not executed). - To run hard-rule machine checks, remove AI-isms, delete test content, or perform cross-chapter review on a full chapter or external copy: delegate to
fiction-review(if not installed, deliver a style checklist and note that the machine check script and cross-chapter review were not run). - For book title/blurb, golden three chapters (opening hook), full-volume or volume outline, hook grading, or daily update scheduling: delegate to
fiction-planner(if not installed, only provide within-chapter pacing techniques and note that overall book/volume scheduling was not done). - To maintain foreshadowing, sub-plots, character files, timelines, item lists, or handle compatibility between frozen text and setting conflicts: delegate to
fiction-continuity(if not installed, list the master writing entry points that need updating, but do not modify other master writing entry points). - To initialize a project skeleton from scratch, import old drafts, or add newly published chapters to the frozen list: delegate to
fiction-init(if not installed, may independently assist in draftingbible/style-guide.mdand list missing skeleton to-dos; for updating the frozen list, instruct the author to update.fiction/config.json'sfrozen.rangesand runlint.mjs --freezein two steps—this skill does not execute those actions).
Before Starting
Before starting, read the three files under the author's project root (directory structure and master writing entry points are defined in SB §2, SB §5):
AGENTS.md: Focus on## 本书口径(Book-specific profile: protagonist profile, POV discipline, book-specific forbidden zones and rules)..fiction/config.json: Focus onbook.genres(genre pack IDs enabled for this book) andlint.*(banned terms, desensitization rules).bible/sources.md: Confirm the master writing entry point forstyle_guide(default isbible/style-guide.md). Ifbible/style-guide.mdalready exists, read it as well.
Before writing or modifying any machine-readable file, first open the corresponding excerpt file (this skill's is references/formats/project.md), and write according to its format and boundaries—do not rely on memory. If the project configuration file does not exist, prompt the author that they can first run fiction-init to set up the project skeleton, and simultaneously explain "Project configuration not found. The following suggestions are based on general default conventions."
Priority of conventions (see SB §3): Project AGENTS.md "Book-specific profile" > bible/style-guide.md > Genre pack > This skill's general defaults. If a conflict is detected, defer to the higher-priority convention—do not override unilaterally.
Core Principles
All techniques revolve around five underlying principles, avoiding verbose embellishment or mechanical formulas:
- Restraint: Precise details are more powerful than flowery descriptions. A specific wear mark on an object, a pause in a hand gesture—these carry more weight than an entire paragraph of abstract sentiment.
- Contrast: Use the ordinary, everyday to highlight the extraordinary or abnormal. Ground the mundane world—the daily grind and boundary sense of ordinary people—first, so that when an anomaly appears, its impact is fully felt.
- Leaving Space: Don't explain everything for the reader. If the action and facts already convey the meaning, do not add an author's summary at the end of the paragraph. Let the reader connect the dots themselves.
- Authenticity: Character reactions should follow real human nature, not plot convenience. An ordinary person encountering the supernatural or a crisis for the first time will often react with doubt, avoidance, or self-preservation, not immediate heroism.
- Structural Cycle: Large-scale arcs (entering a new map, a new dungeon, starting a new volume) need a stable progression skeleton. This creates reader expectations like "learn the threshold → enter the operation → encounter trouble → take the rewards," rather than writing a scattered travelogue or a series of game quests.
Process
Choose Mode A or Mode B based on the current task. This skill does not carry execution scripts; all text judgments and convention confirmations are done collaboratively between the model and the author.
Mode A: On-demand Technique Consultation or Targeted Rewriting
- Define the writing problem: First identify which layer the issue falls into—scene imagery, pacing tension, dialogue quality, information delivery, atmosphere/suspense, specific chapter type, or genre voice.
- Read only the hit reference documents: Read 1–2 corresponding
references/*.mdfiles according to the routing table at the end of this document. If.fiction/config.json'sbook.genreshas values, simultaneously read the correspondingreferences/genres/<genre>.mdfiles. Do not load all unrelated documents. - Align with the book's conventions: Cross-reference the general rules in the reference documents with the
AGENTS.md"Book-specific profile" andbible/style-guide.md. Filter out defaults that contradict this book's conventions (e.g., if the book deliberately uses first-person or high-density wry humor, follow the book's conventions). - Output an actionable plan: Provide specific revision methods (e.g., compress which paragraph, break which summary sentence, rearrange a scene in which steps) or targeted demonstration excerpts.
- Frozen chapters are read-only facts (see SB §3): For frozen chapters, only perform technique analysis and issue reports. Never rewrite, add sentences, or overwrite.
- Follow
fiction-continuity's conflict priority (see SB §3): Only write setting rulings that the author has explicitly confirmed in this process and that have no conflicts intobible/canon.md. Unconfirmed or conflicting items are passed tofiction-continuity. - Non-frozen chapters: When a change would alter established settings or overwrite the author's existing text, stop and ask the author first. Full structural rewrites should be handed back to
fiction-chapter.
Mode B: Build or Calibrate bible/style-guide.md
- Determine the starting method: Ask or confirm whether the author has at least 2–3 satisfactory sample chapters. If sample chapters exist, take the "reverse-engineering" path. If the author hasn't started writing yet, take the "Q&A co-define" path.
- Read templates and methods: Read references/style-guide-template.md and assets/style-guide.template.md. Confirm the seven core dimensions (sentence length/pacing, signature punctuation, single-sentence paragraphs, dialogue habits, humor dosage, forbidden expressions, author-selected sample segments) as well as narrative perspective and the prohibition list.
- Generate a style draft:
- Reverse-engineering path: Read the author's specified sample chapters (read only—do not modify the original chapters). Analyze sentence length distribution, high-frequency punctuation, paragraph line count, dialogue density, description material, and emotional writing style. Extract 2–4 benchmark sample segments for the author to review and record their sample chapter paths (
chapters/{vol}/{ch}/v{n}.md). Compile into a draft. - Q&A co-define path: Ask a concise round of questions based on the seven dimensions. Turn the author's preferences into specific, judgeable rules (e.g., "Continuous dialogue does not exceed 3 sentences" "Exclamation marks are limited per the author's cap"). Avoid vague adjectives.
- Reverse-engineering path: Read the author's specified sample chapters (read only—do not modify the original chapters). Analyze sentence length distribution, high-frequency punctuation, paragraph line count, dialogue density, description material, and emotional writing style. Extract 2–4 benchmark sample segments for the author to review and record their sample chapter paths (
- Get author approval: Present the draft along with two types of pending synchronization suggestions to the author for confirmation:
- Literal banned words and desensitization lists → Suggest writing into
.fiction/config.json'slint.banned_terms/lint.desensitize.*(default levelblock, reports as blocking). - Custom sentence patterns or regular expressions → Suggest writing into
.fiction/lint-patterns.txtusing valid section headers (e.g.,[summary:suggest],[custom:block:all]—blockreports as blocking,suggestreports as a suggestion; syntax is found infiction-review's (orfiction-chapter's orfiction-init's) accompanyinglint.mjs --help; if none are installed, verify manually). Do not overwrite the existingbible/style-guide.mdbefore confirmation.
- Literal banned words and desensitization lists → Suggest writing into
- Write and handover: After confirmation, write to
bible/style-guide.md(and ensure thestyle_guideregistration inbible/sources.mdis consistent, see SB §5). Write the confirmed benchmark sample chapter paths intobible/style-guide.md. Simultaneously remind the author to register them in the projectAGENTS.md"Book-specific profile" so thatfiction-reviewcan reference them during voice calibration. Sentence rhythm, white space, and voice alignment still rely on review reading and author validation.
Checks
- This consultation's referenced techniques and suggestions do not violate the project
AGENTS.md"Book-specific profile" or the existingbible/style-guide.md[model] - The writing advice or revision plan is grounded in specific operations (e.g., five elements, insert action every three lines, four-step rulebook method), not vague platitudes
[model] - When creating or updating
bible/style-guide.md, all seven style dimensions are written as enforceable judgment criteria and do not contain fabricated sample segments from other authors[model] - The sample segments, forbidden expressions, and core style conventions in
bible/style-guide.mdhave been personally confirmed by the author[author] - The writing method for literal banned words (
config.jsonlint.banned_terms) versus regex/sentence patterns (lint-patterns.txtvalid section headers) is clearly distinguished, and marked withblock/suggestlevels[author] - The confirmed benchmark sample chapter paths are recorded in
bible/style-guide.md, and the author has been reminded to register them in the projectAGENTS.md"Book-specific profile" forfiction-reviewcalibration[author] - No frozen chapters have been modified (frozen chapters only received analysis reports), and no other master writing entry points (e.g.,
canon.md,world-rules.md) have been overstepped[model]
Output
- Mode A: A technique diagnosis, step-by-step revision method, or demonstration rewrite for the current problem (by default, presented directly in the reply, with the author deciding whether to adopt; for frozen chapters, only deliver analysis and handover to-dos).
- Mode B: Create or update
bible/style-guide.mdin the project root (refer to assets/style-guide.template.md). Output suggested entries to sync to.fiction/config.json/.fiction/lint-patterns.txt, as well as the benchmark sample chapter paths forfiction-review. - Report Format: Briefly summarize the reference documents/genre packs used in this invocation, changed file paths (if any), to-dos passed to sibling skills (if any), and any convention divergences or sample segments pending author confirmation.
Reference Documents
Contract Excerpts
| Problem | Which Document to Read |
|---|---|
| Check project directory structure, layering, conflict resolution, file responsibilities, master writing entry registry (SB §1–§5) | references/formats/project.md |
Technique References
| Problem | Which Document to Read |
|---|---|
| Scenes feel unfocused, lack visual impact, slow openings, clumsy transitions, imbalanced fast/slow pacing, flat endings, writing feels like a log | references/scene-craft.md |
| Weak payoff/power fantasy feel, conflict escalation stuck, Scene-Sequel rhythm out of control, broken reader anticipation, flat emotional wave, major events without ripple effects, new areas feel like travel notes, chaotic multi-character scenes | references/narrative-techniques.md |
| Dialogue feels like a stage play, all characters sound the same, characters are just mouthpieces for the author's exposition, thin subtext, redundant narration after dialogue explaining it, writing strong characters but guessing their psychology | references/dialogue.md |
| Dumping too much setting at once, repeating the same information, in-world documents/books feel like lectures, hard-to-understand jargon, three-layer structure of overt/covert lines, system/identification UI crossing the line, desensitization for real-world metaphors | references/information.md |
| Atmosphere too exaggerated, lack of restraint when describing anomalies, missing sense of scale, environmental descriptions feel like landscape paintings, genre-blended language clashes | references/atmosphere.md |
| Need to write preparation/gathering chapters, action/exploration chapters, loot/inventory/equipment swap, trade/purchase scenes, rulebook scenes | references/chapter-types.md |
Need to create or update bible/style-guide.md, or reverse-engineer writing style from existing chapters | references/style-guide-template.md and template assets/style-guide.template.md |
Genre Packs
Genre-specific differences are uniformly stored in references/genres/, loaded according to .fiction/config.json's book.genres (blended genres can load multiple):
| Genre | Reference Document |
|---|---|
| Xianxia / Xuanhuan (Cultivation Fantasy) | references/genres/xianxia.md |
| Urban / Modern | references/genres/urban.md |
| Suspense / Mystery | references/genres/suspense.md |
| Romance | references/genres/romance.md |
| Sci-Fi | references/genres/scifi.md |
| Historical | references/genres/history.md |
| How to add custom genre packs | references/genres/README.md |