Fantasy Tropes Template 1
Trope sheet: expectation [x] | reader promise [y] | story-specific change [z] | cost [c] | payoff [p].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
Strong use of fantasy tropes gives readers the promised emotional or narrative experience while changing the circumstances, consequences, character motives, or combinations enough to make the story feel specific rather than copied.
Trope sheet: expectation [x] | reader promise [y] | story-specific change [z] | cost [c] | payoff [p].
Subversion test: Readers expect [event]; instead [change] happens because [character/world cause], producing [new payoff].
Combination engine: Trope A creates [pressure], Trope B creates [counter-pressure], forcing [choice].
Scene test: This trope changes the character’s goal/relationship/knowledge by [specific change]; otherwise cut or merge the scene.
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].