Two years of prompting. Hundreds of “god tier” prompts tested. And the thing that actually moved the needle? A list of what NOT to do.
A power user on r/ChatGPTPromptGenius noticed something the rest of the community keeps missing. Every popular prompting guide tells you to add more: more context, better personas, step-by-step reasoning commands, chain-of-thought instructions, temperature metaphors, elaborate role definitions. He went the opposite direction. Output quality jumped more than any persona prompt ever gave him. Not marginally more. Noticeably, immediately, every single time.
Here’s why it works.
The Problem With “Add More Instructions”
Modern chat models have default behaviors baked into their training. Behaviors almost nobody actually wants:
- 🤖 “Great question!” openers every single time
- Headers and bullets on everything, regardless of fit
- Caveats you didn’t ask for
- Hedging on things the model is actually confident about
- A summary paragraph that just repeats what was already said
You can stack “be confident and direct” instructions on top all day. They don’t override this stuff. It’s trained in. The model learned these patterns from millions of examples where users apparently rewarded them, so the behavior is sticky. Positive instructions compete with that training. Negative instructions cut through it.
Think of it like a default stylesheet in CSS. You can keep adding styles, but unless you explicitly override the defaults, they’ll keep bleeding through. The “don’t” block is your reset layer. It removes the noise before you even start building the signal.
The way to kill default behaviors is to name each one explicitly and say: don’t do that.
The Template That Actually Works
Here’s the prompt structure he settled on:
You are a [specific role, not "expert"] Task: [one sentence] Don't: - Start with an acknowledgement - Add caveats I didn't ask for - Use headers or bullets unless I ask for them - End with a summary Before you answer, tell me the two assumptions your answer depends on. If either could be wrong, ask instead of guessing.
That last line is the real unlock. Half of bad AI responses aren’t the model being wrong. They’re the model making a reasonable wrong guess about what you wanted, then writing 800 words based on that guess. It picks the most statistically likely interpretation of your request and runs with it. By the time you realize it misunderstood, you’ve already read the whole thing.
Forcing it to surface assumptions first turns most of those into a one-line clarifying question instead. The model has to commit to its interpretation before answering, which means you get to correct it in two sentences rather than re-prompting from scratch after a full failed response. Saves more time than anything else in this approach.
Real Examples Where This Made a Difference
Code review. Old way: 3 real bugs buried in 10 style nitpicks nobody asked for. Add “don’t suggest style changes, don’t praise the code, if something’s a bug just call it a bug” and you get only the bugs. Half the reading time on every review. You stop playing “find the actual problem in the wall of feedback” and the review becomes something you actually want to run.
Design docs. Used to spend 20 minutes after every generation cutting the generic background section and boilerplate risk bullets that looked identical across every doc. Adding “don’t include a background section unless I ask, only flag risks specific to this system” means the doc is usable on the first try. No more copy-paste artifact that somehow made it into production docs because nobody had time to clean it properly.
Learning new concepts. “Explain X” used to return a Wikipedia-tier answer you could have Googled. Adding “don’t define terms I didn’t ask about, don’t open with history, don’t use analogies unless the concept is genuinely counterintuitive” gets an explanation that actually teaches something new. The model stops performing education and starts doing it.
Drafting emails. Without constraints, you get formal openers, three paragraphs where one would do, and a closing sentence offering to “jump on a call at your convenience.” Add “don’t use formal openers, don’t exceed three sentences unless complexity requires it, don’t offer follow-up meetings I didn’t mention” and you get something you’d actually send without editing.
✅ How to Apply This Right Now
Take any prompt you already use. Add a “don’t” section. Start with the behaviors that frustrate you most:
- No opening fluff or acknowledgements
- No unsolicited caveats or disclaimers
- No bullet points unless you ask for them
- No closing summary
Then add the assumptions line at the end. Run it on something you’ve prompted before and compare outputs side by side. The difference tends to be obvious on the first try, not after a week of testing.
Keep a running “don’t” list you can paste into any prompt. Over time it becomes a personal filter that reflects exactly how you like to work. The prompts get shorter and the outputs get cleaner.
Two years of testing across every “expert mode” prompt that circulates this community, and subtraction beat addition every time. Try it on your next real prompt and watch what changes.
telling the model what NOT to do works better than any “expert mode” prompt i’ve tried in 2 years
by u/Rich_Specific_7165 in ChatGPTPromptGenius