Unreal Fiction

Write Speculative Fiction

Produce fiction that works as fiction: characters pursue incompatible aims, world rules create consequences, scenes change the available choices, and the prose has a deliberate voice. Treat "no AI feel" as an editorial quality target, never as a guarantee about authorship or detector results.

Load only what the task needs

• Read references/source-grounding.md for every named franchise, canon-accuracy request, or fandom-informed AU.
• Read references/genres.md to route the requested setting, then load only the matching detailed reference: interstellar.md, vampires.md, wizarding-world.md, westeros.md, or assassins.md. Use the compact modules in genres.md for the remaining settings.
• Read references/tropes.md when the user selects a relationship trope or when a relationship-centered request leaves the dynamic unspecified.
• Read references/chinese-web-fiction.md for Chinese prose, especially fanfiction and serial fiction.
• Read references/craft.md before drafting or substantially revising prose.
• Read references/anti-ai.md before drafting any prose, not only at revision. A checklist applied after generation cannot repair the distribution the generation came from; the positive sections in that file are drafting instructions, and the tell lists are what to avoid while writing.
• Use templates/story-bible.md for a multi-chapter work, a continuation, or any story with dense canon.

Route the request

Choose one route without making the user learn the workflow.

1. Original fiction: Start from the user's premise, desired image, relationship, trope, mood, or ending. Infer low-risk details. Ask one compact round of questions only when language, length, content boundaries, or a choice that would fundamentally change the book is missing.

2. Fanfiction or AU: Obtain the source canon and cutoff, the characters, three to five immutable behavioral anchors per lead, intended relationship, AU premise, desired canon divergences, language, length, and content boundaries. Ask only for missing high-impact information. Do not replace characterization with appearance, house, faction, secondary gender, powers, or a fandom stereotype.

   Settle these before drafting. Ask for everything missing in one round, and never ask twice. Ending and length are the two that waste an entire draft when guessed wrong, so state an explicit assumption whenever the user has not given them.

   Variable	Options	If unstated
   Language	Chinese / English	the language the request was written in
   篇幅	flash / chapter / short story / novella / novel	smallest form that carries the premise, named as an assumption
   结局	HE / BE / 开放结局 / 先虐后甜 / HE with a cost	ask; this is the primary tag readers select on
   AU 类型	星际 / 现代 / ABO / 娱乐圈 / 校园 / 民国 / 武侠 / 废土 / 魔法学院 / 赛博朋克 / 兽人 / 穿书 / 重生 / 职场	ask, and confirm the mode in source-grounding section 6
   CP 与方向	the pairing, and which side is which where the fandom marks it	ask
   分级	清水 / 擦边 / explicit	清水
   视角	first person / close third / alternating close third	close third
   私设容忍度	strict canon / 允许私设 / 完全AU	允许私设
   交付方式	one delivery / sequential chapters	by length

   Establish the whole relational map, not only the pairing. A fanfiction pairing reassigns every other relationship in the source: canon partners routinely become friends, comrades, siblings, colleagues, or rivals, and this reassignment is a convention of the form rather than an error to correct. Take the user's fandom conventions as outranking canon relationships, and confirm the reassignment for any canon partner the story will touch.

3. Continuation: Read the existing manuscript, story bible, and the user's revisions first. Continue from established facts and voice. Do not ask the user to restate information already present.

4. Revision: Preserve plot facts, intentional ambiguity, voice, and user-written irregularities unless the user authorizes structural changes. Diagnose before rewriting when the request is only for critique.

5. Planning or worldbuilding: Build decisions that generate scenes. Do not deliver an encyclopedia of decorative lore.

Establish authority and boundaries

For fanfiction, separate three layers in the working notes:

• Source canon: facts valid at the user's chosen cutoff.
• AU divergences: explicit changes and their downstream consequences.
• Inventions: new facts added for this story.

Resolve conflicts in this order: the user's latest explicit instruction, approved AU divergences, already written manuscript, source canon at the chosen cutoff, then cautious inference. If exact franchise lore matters and no reliable source is available, ask or mark the uncertainty; never invent a "canonical" fact.

Invent freely inside the Inventions layer. Do not restrict the story to what the user specified: add the private history, minor institutions, household facts, habits, old injuries, debts, and secondary relationships the scenes need. An invention is binding once written. Log each one so later chapters cannot contradict it, and keep it labeled as invention rather than canon. Ask the user first only when an invention would overwrite a stated character anchor, reverse an established relationship, or change the AU premise itself.

Treat fandom works as reception evidence, trope evidence, and fanon evidence, never as source canon. Preserve a source ledger. When the AU borrows one franchise's setting for another franchise's characters, translate behavioral invariants, relationship history, social leverage, and vulnerabilities before assigning jobs, powers, factions, or costumes.

For ABO, bonding, heat or rut cycles, fertility, scent, blockers, social hierarchy, and legal status are variables rather than universal canon. Define only the variables relevant to the story. Never treat biology as personality or coercion as automatically romantic. Do not sexualize minors. Default to non-graphic intimacy unless the user clearly requests otherwise and the platform permits it.

Calibrate language and voice

Write natively in the requested output language. Do not draft in one language and translate internally.

• Chinese: Use idiomatic modern Chinese appropriate to the requested platform and era. Control pronoun and name repetition, translated syntax, ornamental four-character clusters, explanatory emotion labels, and generic lyrical filler. Let paragraph length, omission, slang, and punctuation serve the chosen voice rather than a generic literary register.
• English: Control abstract phrasing, filter verbs, symmetrical rhetoric, ornamental em dashes, generic sensory bundles, explanatory dialogue, and uniformly polished sentences. Match spelling and register to the requested market.
• Bilingual or translated work: Maintain a terminology ledger. Recreate cadence, social register, and subtext in the target language; do not translate word for word.

If the user supplies writing samples, extract an abstract voice profile: narrative distance, sentence and paragraph distribution, syntax, dialogue ratio, lexical register, sensory priorities, humor, metaphor density, explicitness, and habitual omissions. Use several samples when possible. Match the sample's voice at full fidelity, including the parts that take risks: its jokes, its bluntness, its odd comparisons, its refusals to explain. The boundary is verbatim text, not style. Do not reuse the sample's actual sentences, and do not let voice matching stand in for craft decisions.

For Chinese samples, distinguish evidence about local prose from evidence about whole-story structure. A scene excerpt can calibrate cadence and subtext; it cannot establish a reliable climax pattern, ensemble arc, or novel architecture.

Engineer the AU before plotting

For an AU, complete five private maps:

1. Source invariants: What must remain recognizable about each character and relationship?
2. World substitution: Which source functions receive new equivalents in the AU, and which do not transfer?
3. Institution graph: Identify at least three organizations or offices, their formal powers, dependencies, internal factions, and points of contact with ordinary life.
4. Rule-to-plot chain: Trace at least three causal steps from a world rule to a personal consequence. If the rule never changes a choice, it is decoration.
5. Friction audit: Identify where imported characters do not fit the new system and where the system changes them without erasing them.

Keep the full architecture in notes. Reveal only what the current viewpoint needs through procedure, conflict, work, rumor, or error. Completeness in the story bible does not justify exposition in the manuscript.

Build the story engine

Before prose, determine the following privately or in a compact proposal when the user requests approval:

1. Story promise: the specific experience the opening commits to delivering.
2. Character engine: each major character's immediate want, private need, leverage, blind spot, and line they believe they will not cross.
3. World pressure: a scarcity, rule, institution, custom, or material constraint that changes what characters can do.
4. Causal spine: because of one choice, a consequence removes an option and forces the next choice.
5. Change budget: what becomes newly true, newly impossible, newly costly, or newly misunderstood in each scene or chapter.
6. Open loop: a concrete question, danger, promise, or emotional imbalance worth carrying forward.

If a central relationship trope is unspecified, choose one from references/tropes.md based on the characters' existing asymmetry and the world's pressure. Do not choose a trope independently of characterization. Combine at most one primary and one secondary trope per arc.

For travel, quest, survival, or political stories, prefer a legible progression line: geography, deadline, campaign season, school term, investigation chain, or social ascent. Make each station a local power with its own incentives. Let prior solutions fail under changed conditions.

Make institutions tangible through procedures that affect the plot: rosters, permits, debt, inheritance language, examinations, medical certification, rationing, service agreements, chain of command, or archival proof. A form or rule must grant access, create exposure, transfer power, or impose a cost; otherwise omit it.

Plan at least one memorable set piece for a long short story or larger work. Give it a human objective, legible spatial geometry, a setting-specific rule, an escalating loss of control, an irreversible choice, and material aftermath. Scale without viewpoint and consequence is noise.

Plan at the right scale

Use the user's requested length. If none is given, select the smallest form that can deliver the premise and state the assumption briefly.

Length sets scope, never structural completeness. Every delivered unit, including a flash scene, owes the reader a reason this particular moment is the one being shown, a relationship state that already existed before the first line, at least one person who is not in the room, and a situation that is different at the end. A unit that delivers only atmosphere and a two-hander is a fragment, not a short work. Compress the causes into clauses rather than cutting them.

Do not force a fixed beat sheet onto every chapter. Vary openings, scene lengths, reversal placement, quiet intervals, and endings. A chapter may end on a decision, image, discovery, reversal, or completed emotional movement; do not manufacture a cliffhanger every time. When the user requests 网文感, a platform serial, or web-fiction pacing, apply the propulsion contract in references/chinese-web-fiction.md instead; that register requires a hook at every chapter end.

Draft and revise

For a short piece, draft the whole work and perform the checks below before delivering it. For a long work, create or update a story bible, outline the current arc, then write chapters sequentially. After every chapter:

1. Record what actually happened, not what the outline predicted.
2. Update timeline, location, injuries, possessions, knowledge states, relationships, promises, and unresolved consequences.
3. Check the next chapter against the updated state.
4. Preserve user edits as authoritative prose and evidence of preferred voice.

Run three private passes on prose:

1. Causality and continuity: Verify motivations, spatial logic, rules, timeline, knowledge, and costs.
2. Character and scene pressure: Verify that characters make consequential choices, supporting characters have independent aims, dialogue contains subtext, and the scene changes something.
3. Voice and anti-slop: Apply references/anti-ai.md. Revise clusters of problems, not isolated words. Keep useful roughness.

Before accepting a chapter or major scene, apply the nine quality gates in references/chinese-web-fiction.md when writing Chinese: world logic, ensemble distinction, causal arc, dialogue identity, embodied characterization, spatial clarity, spectacle, dramatization, and relationship movement. A failed gate requires revision, not a promise to improve it later.

For a complete long manuscript, continue chapter by chapter within the same task when the environment supports long-running work and files. Do not pretend that a novel-length manuscript can fit reliably into one model response. Store chapters and state in separate files, then compile only after continuity and revision passes.

Deliver clean fiction

• If the user asks for prose, lead with prose. Do not prepend a synopsis, craft lecture, disclaimer, or list of decisions unless requested.
• Keep planning notes and story-bible material separate from manuscript prose.
• Do not append "Would you like me to continue?" or explain the ending.
• Do not claim the text is undetectable, guaranteed human-written, or free of every AI tell.
• If writing files, use the user's chosen location. For a new long project without a chosen location, create a clearly named project folder in the current workspace with separate state and chapter files. Never overwrite the user's original manuscript.