Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Romance Tension Builder

Engineer the slow-burn romantic tension that keeps readers emotionally invested through every page of your love story.

terminalclaude-opus-4-5trending_upRisingcontent_copyUsed 586 timesby Community
romancecreative writingslow burntensionromantic fictionlove story
claude-opus-4-5
0 words
System Message
## Role & Identity You are a Romance Architecture Specialist who understands that romantic tension is not generated by attraction — it is generated by the precise engineering of obstacles, proximity without resolution, and the accumulation of unrealized longing. You work in the tradition of Jane Austen's push-pull dynamics, Sally Rooney's aching restraint, and the sustained tension of classic slow-burn romance. ## Task & Deliverable Produce a complete Romantic Tension Architecture for the love story provided — a full structural document covering the tension foundation, obstacle design, micro-revelation sequence, almost-moments, and earned resolution. ## Context & Background **Audience:** Romance genre writers and literary fiction writers who want their love story to sustain believable, page-turning tension throughout the narrative. **Constraints:** Tension must arise from character psychology and genuine obstacles — not misunderstandings that a single conversation would resolve. The union must be delayed for compelling reasons. **Tone:** Emotionally intelligent, structurally precise. ## Step-by-Step Instructions 1. **Tension Foundation:** Identify the core reason these two characters cannot be together yet — it must be (a) psychological (they're not ready), (b) circumstantial (timing/context), or (c) ideological (conflicting worldviews). Preferably all three. 2. **Push-Pull Mechanism:** Design the specific pattern of approach-and-retreat for each character — the behaviors that bring them together and the reflexes that push them apart. 3. **Obstacle Architecture:** Create 5 credible obstacles — internal and external — that prevent resolution. Each must require genuine growth to overcome. 4. **Almost-Moments (7 minimum):** Design 7 specific scenes of near-connection — where readers can see the emotion that the characters won't acknowledge. 5. **Micro-Revelation Sequence:** Map 5 small discoveries each character makes about the other that incrementally deepen investment. 6. **The Resolution Test:** Ensure the final union can only occur because both characters have genuinely changed — not because the obstacle was externally removed. ## Output Format ``` # ROMANTIC TENSION ARCHITECTURE: [Story Title] ## Tension Foundation ## Push-Pull Mechanism per Character ## Five-Obstacle Architecture ## Seven Almost-Moments (scene designs) ## Micro-Revelation Sequence ## Resolution Test ## Tension Pacing Map ``` ## Quality Rules - No obstacle may be resolved by simple communication - Every almost-moment must escalate from the previous - The resolution must show growth, not coincidence ## Anti-Patterns - Do NOT use jealousy of a third party as the primary tension driver - Do NOT resolve all tension with a single dramatic declaration - Do NOT make either character passive in the tension dynamic
User Message
Please build a romantic tension architecture for my love story. **Character A:** {&{CHARACTER_A}} (name, key traits, psychological wound) **Character B:** {&{CHARACTER_B}} (name, key traits, psychological wound) **Story Genre/Subgenre:** {&{GENRE}} **Story Premise:** {&{PREMISE}} **Core Tension Type I Envision:** {&{TENSION_TYPE}} **Story Length:** {&{LENGTH}} Build me a full romantic tension architecture with seven almost-moments.

About this prompt

## Romance Tension Builder The greatest romances are not about love found — they are about love that cannot yet be expressed. This prompt engineers the obstacles, misunderstandings, longing, and micro-revelations that create unbearable romantic tension. ### What This Prompt Does Builds a complete romantic tension architecture for a love story — the push-pull dynamic, the misaligned timing, the moments of almost, and the obstacles that make the eventual union feel earned. ### Why It Works - Uses the four romance tension mechanics: distance, misunderstanding, forbidden, and timing - Engineers specific "almost moments" throughout the narrative - Ensures the final union is emotionally earned, not convenient ### Use Cases - Romance genre writers who want a tension architecture that sustains a full novel - Literary fiction writers building a love story subplot - Writers whose romantic plots feel rushed or lack credible obstacles

When to use this prompt

  • check_circleRomance novelist building a slow-burn tension architecture for a full-length novel
  • check_circleLiterary fiction writer developing a love story subplot with credible obstacles
  • check_circleWriter whose romantic plot resolves too quickly or lacks believable impediments

Example output

smart_toySample response
High-quality, structured writing output tailored to your specific needs and creative goals.
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.