Reusable frameworks

7 Dystopian Prompts 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 dystopian prompts make the system concrete and internally logical, show who benefits and who pays the cost, and give the protagonist a personal dilemma inside the system rather than relying only on generalized oppression.

  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.
Dystopian Prompts Template 1
Dystopian engine: [character] wants [goal], but [specific obstacle] forces [choice with cost].
Dystopian Prompts Template 2
Constraint engine: Set the scene in [place/time], require [unusual constraint], and make [ordinary object/detail] matter to the outcome.
Dystopian Prompts Template 3
Reversal engine: Begin with [expected situation]. Reveal [new fact] that changes what the character thinks the problem is.
Dystopian Prompts Template 4
Relationship engine: Put [character A] and [character B] in conflict over [shared concern], while each is hiding [different fact].
Dystopian Prompts Template 5
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dystopian Prompts Template 6
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].
Dystopian Prompts Template 7
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 → [ ].