Table of Contents
Most AI writing tools give you one workflow and call it a day. Sudowrite's Plugin Builder lets you bottle your genre's exact craft moves into a tool you can fire once and reuse forever. A romance writer's "slow-burn tension amplifier" looks nothing like a thriller writer's "ratchet the stakes" button, and Plugin Builder is the workshop where you build the difference.
This is the feature most Sudowrite users underuse. Once you understand variable injection from Story Bible and how to match the right model to your prompt, you stop nudging the AI scene by scene and start running your own genre-specific assembly line.
What Plugin Builder Actually Is
Plugin Builder is a prompt-construction tool inside Sudowrite that lets you create reusable AI commands tailored to your genre, your characters, and your craft preferences. Think of each plugin as a saved instruction set with placeholders. You write the prompt once. Then every time you run it, Sudowrite swaps in real values from your current scene and Story Bible.
Sudowrite ships with the Plugins library full of community-built tools. There's a "Hemingway Mode" that strips adjectives. A "Lovecraftian Dread" plugin that adds cosmic horror beats. A "Banter Generator" for snappy dialogue exchanges. You can install any of them with one click. But the real power is building your own.
Custom plugins matter because no community tool knows your protagonist's specific scar, your magic system's hard rules, or the unreliable narrator voice you've been calibrating for forty chapters. A plugin you build yourself can.
Why a Genre-Specific Plugin Beats a Generic Prompt
Run a generic "make this scene more tense" prompt and you'll get tension that could belong to any book. The thriller writer wants pulse-pounding short sentences and a sudden physical threat. The romance writer wants withheld touch, a glance that lingers two beats too long, breath catching. The horror writer wants the wrong sound from the wrong room.
Same word. Three completely different craft moves. A plugin lets you encode your genre's actual technique into the prompt itself.
The other reason matters more if you're a working writer. You write at speed. Stopping every scene to retype "increase tension using these specific beats, in my POV character's voice, consistent with the magic system rules from chapter three" is a productivity killer. A plugin makes it one click.
The Anatomy of a Sudowrite Plugin
Every plugin has three structural pieces you need to understand before you build one.
The prompt is the instruction you'd give the model if you were typing it fresh each time. This is where craft lives. You tell it the technique, the tone, the constraints, and what to avoid.
The variables are placeholders that pull from your Story Bible automatically. When you write {{characters}} in your prompt, Sudowrite injects your actual character cards at runtime. The same goes for {{worldbuilding}}, {{style}}, {{outline}}, {{synopsis}}, and {{braindump}}. You also get {{highlighted_text}} for the selection in your document and {{previous_text}} for the prose right before the cursor.
The model is the engine that runs the prompt. Different models write differently. The CX prose-modes matrix is your cheat sheet for matching engine to genre, and I'll break it down in a minute.
Get these three pieces right and your plugin works the first time. Get them wrong and you'll spend ten iterations wondering why the output feels off.
Picking the Right Model: The CX Prose-Modes Matrix
Sudowrite gives you a curated set of models, each suited to specific kinds of fiction. The prose-modes matrix the CX team uses is worth memorizing because it's been calibrated against thousands of writer sessions.
- Muse is Sudowrite's in-house fiction-trained model. It's the default for romance, erotica, horror, and thriller. Muse won't refuse explicit content or dark material, and it writes like a novelist instead of a customer-service bot. If your plugin involves sex, violence, body horror, or any morally complex territory most general AI tools flinch at, Muse is the right pick.
- Claude 3.7 Sonnet works best for fantasy, mystery, and YA. It's clean, smart, and handles complex worldbuilding logic without losing the thread. If your plugin needs to track a magic system or seed clues for a later reveal, this is the model to use.
- Claude 3 Opus is the literary heavyweight. Use it for literary fiction, historical fiction, and serious sci-fi. The prose comes out denser and more careful. Sentences have rhythm. It's slower and costs more credits, but for a "rewrite this in literary register" plugin, nothing beats it.
- Deepseek-R1 is excellent for adventure and crime fiction. Pulpy, propulsive, plot-forward.
- GPT-4o Mini handles non-fiction tasks cleanly. Useful if you're building a plugin to generate research notes or character backstory documents instead of prose.
Match the engine to the work. A romance plugin running on a model that softens every steamy scene into a Hallmark card is doing nothing for you.
Walkthrough: Building a Tension Amplifier Plugin From Scratch
Let's build something real. We're going to make a plugin called Slow-Burn Tension Amplifier for romance writers. The goal: take a scene where two leads are in the same room and crank the unresolved sexual tension without losing voice or POV.
Step 1: Open Plugin Builder
From your Sudowrite dashboard, head to the Plugins area and click Create Plugin. You'll see fields for name, description, the prompt itself, and the model selector. Name it something you'll recognize at 2 a.m. mid-draft. "Tension+" is fine. "Plugin 7" is not.
Step 2: Write the Description
This is the line you'll see when you hover over the plugin in your sidebar. Keep it precise. Something like: Amplifies unresolved romantic tension between two characters in a shared scene. Adds glances, near-touches, and interrupted dialogue. Keeps POV and voice consistent.
Step 3: Write the Prompt With Variables
Here's where craft enters. A weak prompt says "make this more tense." A strong prompt tells the model how romance tension actually works. Here's the structure:
You are revising a scene from a romance novel. The protagonist is in the same physical space as their love interest. Your job is to amplify the unresolved sexual tension between them without making it physical. Use these techniques:
- Lengthen one specific beat where they almost touch but don't.
- Add a sensory detail the POV character notices about the other person but tries to ignore (the shape of their wrist, the curve of their mouth mid-sentence, a flicker of a tattoo).
- Insert one moment where dialogue gets cut off, trailed away, or interrupted by an action.
- Add a single internal monologue line where the POV character lies to themselves about what they're feeling.
- Do not consummate anything. Do not add a kiss. Hold the line.
Maintain the POV and tense already established. Match the voice you find in {{style}}. Stay consistent with the character histories in {{characters}}. The scene to revise is below:
{{highlighted_text}}
Notice what's happening with the variables. {{style}} pulls in the voice notes from your Story Bible. {{characters}} grounds the rewrite in your specific people. {{highlighted_text}} is the prose you've selected in the document. Without these injections, you'd be asking the model to revise blind.
Step 4: Pick Muse as the Model
Romance is one of the four genres where Muse is the default per the CX matrix. It won't sanitize chemistry, won't dodge longing, and writes with the rhythm of someone who's actually read genre romance. Pick Muse.
Step 5: Set the Creativity Dial
For tension amplification, set the Creativity Dial somewhere between 4 and 6. Too low and you'll get safe, predictable beats. Too high and Muse will start adding plot turns you don't want, like a sudden phone call from the ex or a thunderstorm. You want it loose, not chaotic.
Step 6: Test on a Real Scene
Save the plugin. Pull up a draft chapter where your leads are stuck on a long car ride, or trapped at a wedding, or working late in an office. Highlight the scene. Run the plugin.
Read the output critically. Did it preserve your POV? Did it stay in your voice (the {{style}} injection should have helped)? Did it actually add the techniques from your prompt, or did it just rephrase a few sentences?
If a beat falls flat, refine the prompt. Plugins are not one-and-done. The best ones you'll iterate on for weeks until they're calibrated to your work.
Variable Injection: The Part That Changes Everything
Variable injection from Story Bible is what makes Sudowrite plugins different from prompts you'd type into a generic AI tool. Most writers underuse it.
The variables available to you map directly to your Story Bible structure:
- {{characters}} injects your character cards, including voice notes, personality, and evolving traits.
- {{worldbuilding}} pulls in your Rules, Lore, Factions, Settings, and Items.
- {{style}} hands the model your style guide, which is gold if you've written one.
- {{outline}} gives the model awareness of where the scene sits in your story arc.
- {{synopsis}} provides a high-level frame of the book.
- {{braindump}} is where your loose notes, themes, and reference materials live.
- {{highlighted_text}} grabs whatever you've selected in the document.
- {{previous_text}} grabs the prose right before your cursor for continuation work.
Use them all when relevant. A fantasy plugin that doesn't inject {{worldbuilding}} is asking the model to make up magic rules on the fly, which is how you get contradictions Chapter Continuity will flag later anyway. A romance plugin that skips {{characters}} won't honor your protagonist's specific brand of avoidance or their love interest's particular cocky-but-soft archetype.
Genre Plugin Ideas Worth Building
If tension amplifier is too narrow for your work, here are plugin concepts that have shipped real value for genre writers.
For Fantasy Writers
Magic System Audit. A plugin that takes a magic-use scene and checks it against your hard rules in {{worldbuilding}}. Sanderson-style consistency, but automated. Run it before you commit to a chapter.
Politics Layer. Adds a faction tension subtext to dialogue scenes. Useful for GRRM-style multi-POV epics where every conversation is also a chess move.
For Romance Writers
Banter Sharpener. Inspired by the dialogue-driven romance of Sarah J. Maas. Takes a flat back-and-forth and adds wit, deflection, and one moment where the mask slips.
Trope Beats. A plugin built for forced-proximity, enemies-to-lovers, or fake dating. Encodes the expected beats and makes sure your scene is hitting them or subverting them on purpose.
For Thriller and Crime Writers
Ratchet. Takes a scene and tightens it. Cuts adverbs. Shortens sentences. Adds a physical threat or time pressure. Channels Chandler when the genre calls for noir grit.
Red Herring Generator. Drops a detail into a scene that could be a clue or could mean nothing. Critical for whodunits where the reader needs to suspect everyone.
For Horror Writers
Wrong Detail. Adds one sensory detail to a setting that's slightly off. The smell of something burning when nothing is burning. A door that was closed but is now open. Slow-build dread, not jump scares.
For Literary Writers
Subtext Pass. Takes dialogue and rewrites it so the characters are never quite saying what they mean. Best run on Claude 3 Opus for the literary register.
Sharing Plugins With the Community
Once you've built a plugin you love, you can share it. Sudowrite's Plugins library is community-driven, and your "Slow-Burn Tension Amplifier" might be exactly what a thousand other romance writers need.
Sharing is straightforward from the Plugin Builder interface. Give it a clean name, a clear description, and add usage notes if the plugin works best on certain kinds of scenes. Other writers can install it with one click.
There's also a reverse angle worth knowing. Browse the community library before you build. Sometimes a plugin already exists that's 80 percent of what you need. Install it. Then duplicate and modify it for your specific use case. That's faster than building from zero.
Common Mistakes to Avoid
The biggest mistake new plugin builders make is being too vague in the prompt. "Make it better" is not a prompt. The model needs to know what "better" means in your genre.
The second mistake is forgetting the variables. If you don't inject {{characters}}, the model will write generic people. If you don't inject {{style}}, the prose won't sound like you. Spend the time building your Story Bible. The plugins repay that investment a hundred times over.
The third mistake is picking the wrong model. A literary plugin running on Deepseek-R1 will give you pulp instead of prose. A romance plugin running on a non-Muse model might dodge the very tension you're trying to build. Reference the CX matrix every time.
The fourth mistake is treating plugins as static. Your craft evolves. Your plugins should too. Revisit them every few months and refine.
Where Plugins Fit in a Working Drafting Practice
Plugins are most powerful when you treat them as part of a layered workflow alongside Write, Rewrite, Describe, Expand, and Chat. You're not replacing those features. You're adding genre-specific tools to a kit that already includes Tone Shift, Chapter Continuity, and the Creativity Dial.
A working session might look like this. You draft a scene using Write in Auto mode. You run a tension plugin on the dialogue. You hit Describe to expand one sensory beat. You ask Chat whether the scene serves the arc your {{outline}} calls for. You run Chapter Continuity at the end of the chapter to catch contradictions.
Plugins are the layer where your specific craft lives. They're how Sudowrite stops being a generic AI tool and starts being your tool.
If you've been writing inside Sudowrite without touching Plugin Builder, you're leaving the most powerful feature on the table. Build one plugin this week. Pick the genre move you make most often and encode it. You can try Sudowrite free and start experimenting with Plugin Builder in your first session.