CommunityWriting & Editinggithub.com

fiction-craft

A web-novel craft library and style-guide builder: covers scene craft, scene-sequel pacing, dialogue, layered information, dual-line structure, atmosphere, genre-blend voice, chapter playbooks, and building bible/style-guide.md. Use for technique questions, demos, or codifying a book's voice.

What is fiction-craft?

fiction-craft is a specialized AI agent skill designed to assist web novel and fiction writers with concrete, actionable narrative techniques and style-guide construction. It functions as a comprehensive reference library for common writing challenges such as scene visualization, pacing, dialogue subtext, information layering, dual-line structure, atmosphere creation, and genre-blending voice. The skill also provides practical 'chapter playbooks' (e.g., preparation, action, loot/trade, rulebook) for specific narrative beats, and guides authors in creating or reverse-engineering a per-book `bible/style-guide.md` from sample chapters. It is designed to be used alongside other dedicated skills (fiction-chapter for drafting, fiction-review for editing, fiction-planner for plotting, fiction-continuity for canon tracking) and strictly refrains from overstepping its boundaries—delivering only technique analysis and style calibration without performing full chapter rewrites or plot planning. The skill integrates project-level configuration from `AGENTS.md`, `.fiction/config.json`, and genre-specific references to ensure all advice aligns with the author's unique voice, conventions, and constraints.

Works with✓Claude Code✓Codex CLI~Cursor✓OpenCode
npx skills add https://github.com/interjc/create-fiction-skills/tree/HEAD/skills/fiction-craft

Installed? Explore more Writing & Editing skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

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.md for 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, or fiction-planner that 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 drafting bible/style-guide.md and list missing skeleton to-dos; for updating the frozen list, instruct the author to update .fiction/config.json's frozen.ranges and run lint.mjs --freeze in 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):

  1. AGENTS.md: Focus on ## 本书口径 (Book-specific profile: protagonist profile, POV discipline, book-specific forbidden zones and rules).
  2. .fiction/config.json: Focus on book.genres (genre pack IDs enabled for this book) and lint.* (banned terms, desensitization rules).
  3. bible/sources.md: Confirm the master writing entry point for style_guide (default is bible/style-guide.md). If bible/style-guide.md already 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:

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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

  1. 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.
  2. Read only the hit reference documents: Read 1–2 corresponding references/*.md files according to the routing table at the end of this document. If .fiction/config.json's book.genres has values, simultaneously read the corresponding references/genres/<genre>.md files. Do not load all unrelated documents.
  3. Align with the book's conventions: Cross-reference the general rules in the reference documents with the AGENTS.md "Book-specific profile" and bible/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).
  4. 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 into bible/canon.md. Unconfirmed or conflicting items are passed to fiction-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

  1. 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.
  2. 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.
  3. 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.
  4. 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's lint.banned_terms / lint.desensitize.* (default level block, reports as blocking).
    • Custom sentence patterns or regular expressions → Suggest writing into .fiction/lint-patterns.txt using valid section headers (e.g., [summary:suggest], [custom:block:all]—block reports as blocking, suggest reports as a suggestion; syntax is found in fiction-review's (or fiction-chapter's or fiction-init's) accompanying lint.mjs --help; if none are installed, verify manually). Do not overwrite the existing bible/style-guide.md before confirmation.
  5. Write and handover: After confirmation, write to bible/style-guide.md (and ensure the style_guide registration in bible/sources.md is consistent, see SB §5). Write the confirmed benchmark sample chapter paths into bible/style-guide.md. Simultaneously remind the author to register them in the project AGENTS.md "Book-specific profile" so that fiction-review can 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 existing bible/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.md have been personally confirmed by the author [author]
  • The writing method for literal banned words (config.json lint.banned_terms) versus regex/sentence patterns (lint-patterns.txt valid section headers) is clearly distinguished, and marked with block / suggest levels [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 project AGENTS.md "Book-specific profile" for fiction-review calibration [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.md in 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 for fiction-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

ProblemWhich 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

ProblemWhich Document to Read
Scenes feel unfocused, lack visual impact, slow openings, clumsy transitions, imbalanced fast/slow pacing, flat endings, writing feels like a logreferences/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 scenesreferences/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 psychologyreferences/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 metaphorsreferences/information.md
Atmosphere too exaggerated, lack of restraint when describing anomalies, missing sense of scale, environmental descriptions feel like landscape paintings, genre-blended language clashesreferences/atmosphere.md
Need to write preparation/gathering chapters, action/exploration chapters, loot/inventory/equipment swap, trade/purchase scenes, rulebook scenesreferences/chapter-types.md
Need to create or update bible/style-guide.md, or reverse-engineer writing style from existing chaptersreferences/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):

GenreReference Document
Xianxia / Xuanhuan (Cultivation Fantasy)references/genres/xianxia.md
Urban / Modernreferences/genres/urban.md
Suspense / Mysteryreferences/genres/suspense.md
Romancereferences/genres/romance.md
Sci-Fireferences/genres/scifi.md
Historicalreferences/genres/history.md
How to add custom genre packsreferences/genres/README.md

Individual skills in this repo

This repo contains 4 individual skills — each has its own dedicated page.

fiction-chapter

网文单章写作六步闭环:查前文和设定、摘资料、定章纲、写正文、机检审改、回写追踪表。作者说“写新章”“接着写”“出下一章”“重写这一章”或要求重排单章结构时就用。重排卷纲或设计连载节拍用 fiction-planner;审校及已有章节获授权的局部回修、润色和去 AI 味用 fiction-review。 Write, continue, rewrite, or restructure one web novel chapter, from continuity checks and outlining through drafting, validation, and story bible updates. Use when asked to write a new chapter, pick up where the draft left off, write the next installment, or rewrite a chapter. Use fiction-planner for volume planning and serial cadence, and fiction-review for editorial review or authorized local fixes, polishing, and removing AI-like prose in an existing chapter.

fiction-planner

网文创意孵化、开篇定位与卷级规划:收敛模糊点子为卖点与金手指边界、起草书名简介标签(publish/blurb.md)、设计黄金三章、编排全书大纲与明暗双线节奏、制定卷纲与章节规划表、排布爽点节拍/欲扬先抑/情绪波形/S-A-B-C钩子/日更与爆更分组及区域循环结构,并结合伏笔扫描排期。当作者构思新书、拟书名写简介、磨开篇、列全书大纲、开新卷、重排卷次或调节奏钩子时触发。只管单章以上规划:建书与冻结交给 fiction-init,单章 outline 与写正文交给 fiction-chapter,文案与正文审校交给 fiction-review,平台提交交给 fiction-publish,改短剧交给 fiction-short-drama。 Web-novel ideation, positioning, and volume-level planning: turn vague ideas into marketable hooks, draft publish/blurb.md, design golden first three chapters, whole-book and volume outlines, beat/emotion waves, S-A-B-C hook and daily groupings, region cycles, and foreshadow schedules. Use when brainstorming a book, drafting titles/blurbs, planning volumes, pacing, or scheduling payoffs; hand setup/freezing to fiction-init, chapter outlines/drafting to fiction-chapter, review to fiction-review, submission to fiction-publish, and adaptation to fiction-short-drama.

fiction-short-drama

竖屏短剧改编与原创剧本闭环:立项、分集大纲与章集映射、分批写分集剧本、前 3 秒钩子与付费卡点设计、机检与映射回写。涉及改编短剧、把小说改成竖屏短剧、写短剧剧本 / 分集剧本、分集大纲、章集映射、付费卡点、前 3 秒钩子、断章、原创短剧、续写下一集短剧、检查短剧格式与时长时使用。建项目用 fiction-init;小说策划用 fiction-planner;写小说用 fiction-chapter;改共享档案用 fiction-continuity;润色用 fiction-review;转分镜用 fiction-storyboard;路由用 fiction-workflow。 Vertical short-drama adaptation and original scripting workflow: series setup, episode outlines, chapter-to-episode mapping, batched episode scripts, first-3-second hooks, cliffhangers, paywall breaks, and script checks. Use when adapting a novel into a vertical short drama, writing or continuing short-drama episodes, planning episode outlines or maps, placing paywalls, or checking script format and duration. Use fiction-init for setup, fiction-planner for novel planning, fiction-chapter for novel chapters, fiction-continuity for shared bible edits, fiction-review for polish, fiction-storyboard for storyboards, and fiction-workflow for routing.

fiction-storyboard

竖屏短剧分镜工作流:基于已定稿且过检的分集剧本,先做防剧透简报与视觉资产最小建档,再按“段(一次视频生成)→ 镜(段内剪切)”拆解分镜,逐镜核对台词认领、动作依据、竖屏构图、单瞬起止与跨集连戏,最后跑脚本验收并交接下游提示词。作者说“画分镜”“拆镜头”“做场景脚本”“切镜”“把第几集转成分镜”“剧本改了同步分镜”时就用,即使没提“分镜”二字。写或改分集剧本(含改台词)请用 fiction-short-drama;补全资产锁定词、写图片/视频提示词或做付费生成确认请用 fiction-visual-prompts。 Vertical short-drama storyboard workflow: turn finalized, validated episode scripts into segment-and-shot storyboards with spoiler briefs, minimal visual asset entries, continuity tracking, verbatim dialogue/action claiming, 9:16 vertical framing, single-instant start-to-end shot design, and automated storyboard validation. Use when asked to storyboard an episode, break a script into shots, cut segments, or sync storyboards after script edits. Use fiction-short-drama for writing or editing episode scripts and dialogue, and fiction-visual-prompts for full asset locks, reference-image slots, and image/video prompts.

Related Skills