Reusable frameworks

6 Fantasy Tropes Templates

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.

Use the framework

How to personalize a template

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.

  1. 1
    Choose the template closest to your actual purpose.
  2. 2
    Replace every bracketed field with specific information.
  3. 3
    Delete any sentence that does not belong in your situation.
  4. 4
    Read the result aloud for unnatural transitions or repeated phrasing.
  5. 5
    Verify names, dates, links, facts, and promises before sending or publishing.
Fantasy Tropes Template 1
Trope sheet: expectation [x] | reader promise [y] | story-specific change [z] | cost [c] | payoff [p].
Fantasy Tropes Template 2
Subversion test: Readers expect [event]; instead [change] happens because [character/world cause], producing [new payoff].
Fantasy Tropes Template 3
Combination engine: Trope A creates [pressure], Trope B creates [counter-pressure], forcing [choice].
Fantasy Tropes Template 4
Scene test: This trope changes the character’s goal/relationship/knowledge by [specific change]; otherwise cut or merge the scene.
Fantasy Tropes Template 5
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].
Fantasy Tropes Template 6
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 → [ ].