Most people fix a disobedient model by adding more rules. More capital letters, more “never” and “don’t” lines. A recent r/PromptEngineering post by u/k-thekreator points the other way: the prompt rarely says too little. It usually fights itself, or it only tells the model what to avoid. Two rules fix most of it, and they work with any model.
The key idea
A model can only follow a prompt it can read one way. If two instructions pull in different directions, or an instruction describes only what to avoid, the model has to guess. Its guess is not always the one you wanted.
Think of it like handing a new hire two sticky notes. One says “Be quick.” The other says “Be thorough.” They will pick one on a busy afternoon and the other on a slow one, and you will never know which version you get. The model does the same thing. The result looks like randomness, but it is really your prompt giving two orders at once.
The old way vs. the new way
The old way is to patch. The model ignored something, so you add a stricter line below it. Do that ten times and you have a long prompt that nobody, including the model, can read consistently. Each patch also adds a fresh chance for a new conflict, so the prompt gets longer while the behavior stays shaky.
The new way is to clean up. You remove conflicts and rewrite prohibitions as targets. The prompt gets shorter and clearer, and the model has less to untangle. Most teams keep stacking rules. This approach deletes them, and it works faster.
Here is why each rule matters.
Rule 1: No contradictions. Prompts contradict themselves more than you would expect. It can be a plain mistake. It can be drift from a prompt edited again and again, or stitched together from sub-prompts. Often it is a sentence that can be read in a way you never intended. A common case is a system prompt written by one person, then extended by another who never read the first half. Both parts made sense alone. Together they clash.
Rule 2: Stick to positive prompting. A “don’t” rules out one tiny slice of everything the model could do. It can still surprise you with other behavior. Sometimes it finds a workaround and does the exact thing you banned. Tell a model “don’t mention competitors” and it may describe “other tools in this space” in a way that points straight at them. A positive instruction gives the model boundaries to work inside. It does not have to reason around a list of prohibitions. It sees that the instruction applies and follows it. “Talk only about our own features and pricing” leaves far less room for a clever dodge.
Practical steps
- Ask the model to audit your prompt. Paste it in and ask which parts it finds contradictory. Models are good at spotting this, and you get a list of conflicts for free. A simple request works: “List every pair of instructions in this prompt that could conflict, and quote both lines.” 🔍
- Resolve each conflict with a condition. Look at this pair:
- Before: “Keep answers short.” … later … “Always explain your reasoning in detail.”
- After: “If the user asks for your reasoning, explain it in detail. Otherwise, keep answers under 100 words.”
The two rules now apply to different situations, so they no longer collide. ✅
- Hunt for every “don’t,” “never,” and “avoid.” Count them. The goal is close to zero. A quick search through the text for those three words will find most of them in under a minute.
- Flip each one into the behavior you want. Take this:
- Before: “Don’t use jargon. Never write long paragraphs. Don’t be formal.”
- After: “Write in plain, conversational English, in paragraphs of two or three sentences.”
Three bans became one clear target. Ask yourself, “What should the model do instead?” and write that answer down. ✨
- Re-test with the same inputs. Run the cases that failed before and compare the outputs. Keep a small set of three to five tricky inputs so you can repeat the check after every edit and see right away if a change helped or hurt.
One fair caveat
The top comment on the thread notes that a well-placed “don’t” can sometimes save you when the task is open-ended and a positive instruction is vague. That is a reasonable point. Treat the rule as a default, not a law. Start positive, and keep a negative only where a positive version cannot say what you mean.
Try it today
Take the longest prompt you use and run step one. Ask the model what it finds contradictory, fix those lines, then rewrite your top three “nevers” as positives. It takes about ten minutes, and you may find the prompt gets shorter and works better. Got a rule of your own that belongs on this list? Share it in the comments!
Two prompt engineering rules to tame any model
by u/k-thekreator in PromptEngineering