Bible Network Crypto DeFi Onchain RWA AI Agent Stablecoin Chain SAFU CryptoTax DeFAI AGI Claude Me Claude Skill Claude Design Claude Cowork
Independent Media
Not affiliated with any project
Let Claude Do the Work, Not Just Answer
claudecowork-me.com
LATEST
No More Tab-Switching: What Claude's Slack Integration Can Actually Do, and Where It Can't  ·  Think Claude Is Just a Chatbot? Here's the Real Difference Between Claude and Google Search  ·  Why Your Claude Project Seems to Get 'Dumber' Over Time: Diagnosing and Fixing Context Rot  ·  Combining Scheduled Tasks: Turning Three Separate Automations Into One Weekly Work Rhythm  ·  Client Email Workflow: The Three Hardest Types to Write and How to Use Claude to Find the Right Tone Balance  ·  Weekly Report Automation: Turn Your Most Painful 30 Minutes Into a 3-Minute Paste-and-Done
Glossary · prompt-techniques

Negative Prompting

prompt-techniques 新手

30-Second Version · For the impatient
Negative prompting means explicitly telling Claude what not to do, rather than only describing the outcome you want. Most people default to positive requests only (like 'keep it short'), but a lot of output problems actually come from not ruling out a specific wrong direction — adding the 'don't' part is often more effective than piling on more positive description.
Full Explanation +
01 · What is this?

What is negative prompting, and how is it different from how people usually write prompts?

Negative prompting means explicitly telling Claude which direction not to go, rather than only describing what your desired outcome looks like. Most people's habit when writing prompts is to put all their effort into positive description — 'write me a friendly-toned email,' 'present the key points as a bulleted list' — these all tell Claude which direction to head in, but don't clarify which directions you specifically don't want.

The difference: positive description marks out a range, and that range can still contain variations you don't like. Say you ask for a 'friendly tone' — Claude might write something friendly but full of stiff, formulaic pleasantries, because 'friendly' alone doesn't rule out 'formulaic.' Negative prompting adds an extra line like 'don't use stiff, formulaic pleasantries,' directly excluding that unwanted direction from the range. The two aren't mutually exclusive — they work together: positive description draws the range of what you want, negative prompting carves out the corners of that range you don't.

02 · Why does it exist?

What are the common mistakes with negative prompting, and which one gets overlooked most?

The most overlooked point is that negative prompting has limited effect if it's too abstract. Say you tell Claude 'don't sound too AI' — this is actually hard for Claude to map onto anything specific to adjust. Is it the sentence structure that's too neat? The word choice too formal? The structure too templated? 'Sounds too AI' is a vague impression, not a concrete, actionable direction. An effective negative prompt needs to specifically name which trait to avoid — say, 'don't start every sentence with list words like first, second, finally' — so Claude actually knows what to exclude.

The second commonly overlooked point is that negative prompting can't replace positive description on its own. If you only say 'don't use stiff, formulaic pleasantries' without clarifying what tone you actually want, Claude rules out one direction but might fill the gap with another direction you equally dislike. The value of negative prompting is in excluding, not defining — the two need to be used together to get the result you actually want.

03 · How does it affect your decisions?

When should you add negative prompting, and when isn't it really necessary?

The best time to add negative prompting is after you've already tried a positive-only prompt once, but the output still falls into a specific pattern you don't like — and that pattern has repeated more than once. This means positive description alone can't rule out that direction, and you need to explicitly state 'don't do this.' For example, if you've already said 'keep it shorter' two or three times, but Claude keeps adding a summary paragraph at the end anyway, explicitly adding 'don't add a summary paragraph at the end' will be more effective than continuing to emphasize 'shorter.'

You don't especially need negative prompting when the task itself is simple and the scope is clear enough that positive description is already precise with no room for ambiguity. 'Translate this passage into English,' for instance, is already clear enough on its own — there's not much extra direction to exclude. A simple test: if you notice you've corrected the same issue more than once, and each correction points in a similar direction, that's the moment to add negative prompting and directly rule out that recurring problem.

04 · What should you do?

How should advanced users design negative prompts to actually fix the problem rather than just treat the symptom?

The key move for advanced users is identifying the specific trait causing the problem first, then writing the negative prompt — rather than writing a vague 'don't do this' as soon as the output feels off. In practice, this means carefully comparing the output you're unhappy with to pinpoint exactly which specific element is causing it — a particular sentence pattern, particular word choice, particular structural arrangement — and naming that specific element clearly. Only then will the negative prompt actually hit the root of the problem, instead of vaguely asking Claude to guess what you don't like.

A second advanced technique is placing the negative prompt alongside the positive description in the same sentence, as a direct contrast, rather than listing them as two separate rules. Instead of just writing 'use a relaxed tone, not too formal,' write 'use a tone like chatting with a coworker, not formal letter phrases like sincerely or best regards.' Putting the positive reference point and the specific negative exclusion together lets Claude understand both 'which way to go' and 'which way not to go' at once — this contrastive phrasing is usually more precise than issuing the two as separate instructions.

Real-World Example +

Say you ask Claude to help write an announcement email to your team. The first time, you only say 'use a friendly tone.' The email you get back is polite in tone, but full of stiff corporate phrases like 'please be advised' and 'this is to inform you,' and still reads stiffly. Instead of repeating 'be friendlier,' the more effective move is to explicitly add a negative prompt: 'write it like you're chatting with a coworker in the break room — don't use formal phrases like please be advised or this is to inform you.' Pairing the positive reference point (break room chat) with the specific negative exclusion (formal corporate phrases) lets Claude accurately grasp exactly what kind of 'friendly' you want, instead of guessing repeatedly within the same vague direction. The practical takeaway: next time you're correcting an output's direction, first figure out exactly which specific element you dislike, then write it explicitly into a negative prompt — that gets you to the result you want faster than piling on more positive adjectives.

Diagram
Positive Prompt Alone vs Positive + NegativeComparison showing a positive-only prompt leaving room for an unwanted output pattern, versus adding a negative constraint that closes off that specific directiPositive Only vs Positive + NegativePositive Prompt Only"Keep it short"stiff toneStill room for unwanted outputPositive + Negative"Keep it short"stiff toneexcludedSpecific direction ruled outClaude Cowork Me · claudecowork-me.com
Feel free to share. Please credit the source.
Common Misconceptions +
✕ Misconception 1
× Misconception 1: More negative prompting is always better — piling on extra 'don'ts' always helps. In reality, vague, abstract negative prompts (like 'don't sound too AI') have limited effect. Only naming a specific trait actually works — stacking vague negatives just makes it harder for Claude to figure out what you actually want excluded.
✕ Misconception 2
× Misconception 2: Negative prompting can replace positive description — just being clear about what you don't want is enough. Negative prompting's job is to exclude, not to define. Stating only what you don't want, without clarifying what you do want, means Claude might rule out one direction but fill the gap with another one you equally dislike.
✕ Misconception 3
× Misconception 3: As soon as an output feels off, you should add a 'don't do this.' An effective negative prompt requires first specifically identifying the root-cause element of the problem. Vaguely shouting 'don't do this' without clarifying what 'this' specifically refers to is about as limited in effect as not saying anything at all.
The Missing Link +
Direct Impact

The biggest advantage of negative prompting is precisely excluding a recurring wrong pattern that positive description alone can't avoid, especially useful when you've already corrected the same direction more than once. The cost is needing to first put in the effort to specifically identify the root-cause element of the problem — if you just vaguely shout 'don't do this,' the effect is about the same as saying nothing, wasting the effort entirely. Negative prompting fits well when you've already tried positive description but the output keeps falling into a specific disliked pattern that can be named concretely. It doesn't fit when the task is simple and the scope is already clear, or when you yourself haven't yet figured out exactly which trait you dislike. In short, negative prompting trades the effort of 'figuring out the root cause first' for the effect of 'precise exclusion' — whether that trade is worth it depends on whether you actually took the time to find that specific element, rather than just rephrasing 'I don't like it.'

Ask a Question
Please enter at least 10 characters