Nougan Edit Prompt Template 🧩

If you do any instruction-editing work - Qwen-Image-Edit, Flux Kontext, MiniMax H3 - you've typed the same closing sentence a thousand times: "preserve the composition, lighting, style, facial expressions, and backgrounds." NouganEditPromptTemplate exists so you type it once. It takes your edit instruction, appends a preservation suffix, and hands you a ready-to-use prompt string. It's the "stop writing the same boilerplate" node from Winnougan's Nougan_Nodes suite.

How it works

Dead simple by design: your edit_instruction gets trimmed, and if enable_suffix is on, the suffix (with the sensible default above) is joined onto it. The separator picker controls the join - newline, space, or comma - which is the knob that actually matters, because edit models respond differently to the boilerplate being on its own line versus inline. The output is a single prompt STRING you wire into any text-encode or edit-model node.

It also passes dynamicPrompts through, so the {} wildcard syntax works in the instruction if your workflow uses that.

The inputs that matter

• edit_instruction - your actual edit: "Change the red car into a blue van."
• enable_suffix - on by default. Turn it off when you want a bare instruction.
• suffix - the preservation sentence, editable. This is the field you'll tune for your model; the default is written for edit models that respect a "don't touch anything else" clause.
• separator - newline / space / comma.

Output: prompt, the combined string.

Installing

Manager search Nougan, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Winnougan/Nougan_Nodes
# restart ComfyUI

No dependencies. It's pure string assembly.

Where people get burned

Two honest notes, neither deep. First, the default suffix is tuned for preservation, and instruction-edit models genuinely differ on how much boilerplate they tolerate - some handle "keep everything else" clauses beautifully, others start ignoring your actual instruction when the prompt gets long. If your edits come out over-conservative, the fix is a shorter suffix or separator comma, not a different node. Second, this is a template, not a validator: nothing checks that your instruction is well-formed, so garbage in is garbage out exactly as expected. It's a convenience for a repetitive chore, and for edit workflows it's a real timesaver.