Novelaire

Run the Chapter Gate (PASS/WARN/FAIL) after drafting a chapter. Use to ensure chapter obeys its fine-outline results and doesn’t contradict upstream canon.

Run the Consistency Gate (PASS/WARN/FAIL) to catch cross-chapter contradictions (character traits/state, world/system rules, timeline, who-knows-what) and produce a prioritized fix list.

Run the Fine-outline Gate (PASS/WARN/FAIL) before drafting chapters. Enforces per-chapter structure and Han > 500 per chapter plan when measurable.

Run the Forgotten Elements Gate to find dropped characters, stalled plot threads, and uncollected foreshadowing in long-form fiction, then output a prioritized fix list.

Run the Outline Gate (PASS/WARN/FAIL) before moving from outline to fine-outline. Use to ensure outline obeys spec constraints and anchors key ambiguity points.

Run the Regression Gate at milestones. Use to scan written chapters for consistency (timeline, knowledge, character state, system boundaries) and produce a prioritized fix list.

Run the Spec Gate (PASS/WARN/FAIL) before moving from spec to outline. Use to verify premise/system/characters/timeline readiness and detect spec-level contradictions.

Define and maintain character canon under spec/characters/ (identity, motive, resources, behavioral boundaries, relationships, state variables). Use when designing main cast, or when outline/chapters show OOC risk.

Define and maintain continuity constraints under spec/continuity/ (tracked state variables, knowledge boundaries, invariants, continuity checklists). Use to prevent “state reset” and cross-chapter contradictions.

Define and maintain factions/organizations canon under spec/factions/ (goals, resources, methods, boundaries, relationships, reaction patterns). Use when plot needs structural pressure and consequences.

Define and maintain terminology and naming discipline under spec/glossary/ (definitions, disambiguation, required/forbidden names). Use to reduce ambiguity and keep terms consistent across outline/chapters.

Define and maintain reusable locations canon under spec/locations/ (purpose, stable details, access rules, dangers, constraints, navigation). Use when scenes reuse places or when space rules cause continuity errors.

Enable and maintain optional mechanism sub-specs under spec/modules/<name>/ (mystery/romance/progression/etc.). Use when a story actually uses a module; avoid creating modules by default.

Define and maintain narrative discipline under spec/narrative/ (POV rules, knowledge boundaries, info release, forbidden shortcuts, content red lines). Use to prevent “cheating” narration and stabilize reader experience.

Define and maintain key objects/resources canon under spec/objects/ (what it is, how it works, limits, ownership/flow, failure, interfaces with system/plot). Use to prevent “magic props” and continuity drift.

Define and maintain story premise constraints under spec/premise/ (logline, core conflict spine, theme, reader promise, non-negotiables). Use when starting a story, when user asks for premise/logline/主线/主题/读者承诺, or when outline/chapters drift off-premise (偏题).

Define and maintain quality gates and checklists under spec/quality/ (what “done” means, pass/warn/fail criteria, regression check items). Use to make progress measurable and gate downstream writing work.

Define and maintain serialization engineering constraints under spec/serialization/ (chapter length targets, update cadence, payoff/recap discipline, volume rhythm). Use to keep outline/fine-outline aligned to a stable release model.

Define and maintain style constraints under spec/style/ (voice contract, rhythm/density targets, dialogue/description balance, avoid/embrace guidelines). Use to stabilize prose voice and reduce “AI-sounding” drift.

Define and maintain mechanism rules and boundaries under spec/system/ (magic/tech/power systems, triggers, costs, limits, failure modes, counters). Use when establishing the story’s “fair tools”, or when plot solutions feel like author fiat / sudden power-ups.

Define and maintain hard timeline anchors under spec/timeline/ (what happens when, causal order, deadlines, irreversible state transitions). Use to prevent time/knowledge continuity errors in outline/chapters.

Define and maintain world facts and hard constraints under spec/world/ (society, geography, history, resources, baseline reality). Use when establishing worldbuilding/世界观 (社会结构/地理/历史/资源), or when plot/scene causality drifts against world reality.

Improve dialogue to feel natural and character-specific (subtext, voice, tension, beats). Use when drafting/revising dialogue-heavy scenes or when dialogue sounds generic/AI-like.

Structure scenes for causality and momentum (goal, conflict, turn, outcome; sequel). Use when drafting or revising scenes that feel flat, unmotivated, or drift-prone.

Capture exploratory discussion into the project drafts as a structured working note (confirmed vs options vs open questions) before committing anything as canon; proactively use when the user is still exploring, undecided, or asks to “note/save/brainstorm first”.

After brainstorming, route confirmed decisions into the correct spec domain and produce reviewable spec proposals (one entry per id) by loading the domain skill and following its template, then apply only after explicit approval.

Produce per-chapter fine outline under outline/ that obeys spec constraints and meets minimum length (Han > 500 per chapter). Use before drafting chapters to lock causality and pacing.

Produce a high-level outline under outline/ that obeys spec constraints and uses @spec:<id> anchors at key ambiguity points; proactively use when spec is ready and the user wants a story spine (acts/arcs/chapter list) without writing prose yet.