Negation Prompting Is Weak: Instead, Explicitly Describe the Desired Behavior

Prompting with negation — "don't be verbose," "don't add caveats," "don't moralize" — is surprisingly ineffective. A detailed Reddit post breaks down why and offers concrete replacements that actually steer model behavior.
Negation Doesn't Cancel Topics
When you say "don't be wordy", the model still activates the concept of wordiness and writes around it, but doesn't truncate responses. Same for "don't add caveats" — the model generates caveats, then tries to negate them, resulting in verbose, hedged answers.
Positive Instructions Work
- Instead of "don't be wordy":
"Respond in 1–2 sentences unless I ask for more." - Instead of "don't moralize":
"Give me a direct answer, treat caveats as optional." - Instead of "don't use bullets":
"Use plain prose, no lists."
Tone Leak from Closing Politeness
Ending a prompt with "thanks!" or "please." shifts the model's tone toward warmer and wordier responses. Neutral endings (just the instruction) yield neutral tones. The effect appears consistent across Opus 4.7 and Sonnet 4.6, and presumably in Haiku too.
Practical Takeaway
These aren't hacks — they're how instruction following actually works. Tell the model what you want, not what you don't want. Explicitly describe the desired output format and style, and keep the prompt tone-neutral if you want a neutral response.
📖 Read the full source: r/ClaudeAI
👀 See Also

Treating Agent Runs as Review Packets: A Practical Pattern for Claude Code & Codex
A developer shares how producing a structured folder per agent run (research, drafts, evals, approval packet, metrics, memory) makes failures visible and iterations faster.

Worker Agents Shouldn't Write Memory Directly: A Curator-Agent Pattern
A Reddit post details a Memory Curator pattern that prevents worker agents from writing directly to shared memory, routing events through a validation and scoping layer.

Claude Code /insights command provides debugging and autonomous task tips
A Reddit user shares two practical techniques for using Claude Code's /insights command: asking for at least three potential root causes when debugging bugs, and using comprehensive task specifications with --dangerously-skip-permissions for autonomous runs.

Claude User Shares 'Don't Manage My Feelings' Prompt for Direct Technical Feedback
A Claude user recommends setting a specific prompt in user preferences to reduce validation preamble and get more direct technical feedback. The prompt tells Claude to skip diplomatic phrasing and provide straightforward criticism on technical and creative work.