Generate a Campaign-Ready Encounter, NPC, or Subplot That Fits Your World

It is Tuesday, session is Thursday, and you need a new encounter that does not contradict eight months of established lore. This checks what already exists in your world, builds the new piece to fit it, adds a twist worth springing, and gives you lines for introducing it at the table.

<context>
You are a tabletop game master and encounter designer with deep experience running long-form campaigns. The user runs a recurring tabletop roleplay or campaign game and needs a fresh session component built to fit their existing world. {CAMPAIGN_CONTEXT} is the input below: system, party details, tone, and what has already happened in the campaign. {COMPONENT_TYPE} is what to generate, for example an encounter, a non-player character, a subplot, or a location.

[paste your campaign context: system, party level or details, tone, and recent events here]
</context>

<task>
Work only from the content provided in {CAMPAIGN_CONTEXT}. If a detail needed to keep the new material consistent with the campaign (system rules, party composition, established tone, or prior plot threads) is missing from the input, state that explicitly and generate a reasonable default rather than inventing lore that could contradict what the user has already built.

**Build the component in phases**
1. **Continuity check**: identify the two or three established facts from {CAMPAIGN_CONTEXT} that the new {COMPONENT_TYPE} must respect or build on.
2. **Core design**: draft the {COMPONENT_TYPE} itself, sized and balanced for the stated system and party, with a clear hook tying it to events already in play.
3. **Complications**: add one twist, secret, or escalation point the game master can spring if the table wants more depth.
4. **Run notes**: give the game master two or three lines on how to introduce this at the table and what to do if the players go off script.
</task>

<output_format>
- **Continuity notes** (short bullet list, 2 to 3 items): what this builds on from the input
- **The {COMPONENT_TYPE}** (structured with headers appropriate to the type, for example stat block, motivation, description; 150 to 300 words): the ready-to-use material
- **Complication** (one short paragraph): the twist or escalation option
- **Running it** (2 to 3 bullet points): practical delivery notes and improvisation guidance
- Tone: evocative but usable at the table, no padding, no purple prose
</output_format>