Exclusion Controls
Say never without learning the syntax
The model keeps adding what you don't want, and the only defense is arcana: "--no hands", negative-prompt incantations pasted from forums — retyped every generation. Exclusion Controls make the negative space structural: click the unwanted element in the output to ban it, keep a visible never-list that persists across generations, and remove any exclusion with one click. Negation is the model's weakest instruction in prose; a blocklist doesn't re-roll each turn.
Framing
The problem
The model keeps adding what you do not want, and the only defense is syntax arcana — negative-prompt incantations retyped every generation.
The pattern
Make the negative space structural: click the unwanted element to ban it, keep a visible never-list that persists across generations, unban with one click.
Why chat breaks here
Negation is the model's weakest prose instruction — "no text in the image" famously produces text — and it re-rolls with every turn.
Risks
Over-exclusion quietly collapses the possibility space — show what the blocklist costs and keep removal effortless.
Avoid when
One-off generations where retyping a negation is cheaper than managing a list.
Use when
The same unwanted elements keep reappearing across generations and prose negation keeps failing.
DOPE evaluation
- Directability
- Banning happens on the artifact — click the element, not describe its absence — and unbanning is one chip click
- Observability
- The never-list is always visible next to the output, so what is being suppressed is never a mystery
- Predictability
- Exclusions persist structurally across generations instead of depending on how well prose negation lands this turn
- Explainability
- Each exclusion chip names what it blocks, and the cost indicator shows how much the blocklist narrows the option space
In the wild
- Leonardo AI · Negative prompt field (Leonardo.Ai) — A dedicated, labeled field for what must not appear — the exclusion as first-class input rather than inline syntax, though still typed prose rather than click-to-ban.
- Stable Diffusion WebUI · Negative prompts (AUTOMATIC1111) — The community convention that proved structural negation works where prose negation fails — persistent per-generation, reusable, and the reason "negative prompt" is a household term in image generation.
- Midjourney · --no parameter (Midjourney) — Exclusion ships as typed flag syntax — exactly the arcana the pattern replaces with visible, persistent chips. The mechanic is proven; the interface is the gap.
FAQ
When should I use the Exclusion Controls pattern?
The same unwanted elements keep reappearing across generations and prose negation keeps failing.
When should I avoid the Exclusion Controls pattern?
One-off generations where retyping a negation is cheaper than managing a list.
What problem does Exclusion Controls solve?
The model keeps adding what you do not want, and the only defense is syntax arcana — negative-prompt incantations retyped every generation.
Why is chat the wrong fit for this?
Negation is the model's weakest prose instruction — "no text in the image" famously produces text — and it re-rolls with every turn.
Related patterns
- Often paired with: Region Lock — Lock what must stay vs ban what must never appear — the two halves of negative control.
- Often paired with: Property Panel — Positive parameters in the cockpit, negative space as a blocklist beside it.
- Alternative to: Inline Prompt Controls — Parsed inline syntax vs a persistent structural blocklist that survives the next turn.