Free to read · no account needed

9 min · prompt

Negative constraints that actually work

Goal: Use a clear don’t-list to block cheerleader openers, fake links, fake user counts, and unapproved roadmap dates.

Best for: When the model keeps adding hype, fake links, cheerleader openers, or unwanted structure.

“Be professional” is vague. “Do not start with Absolutely!; do not invent URLs” is testable. Negative constraints work best as a short, concrete blacklist next to your Goal and Format.

Why beginners skip this

Writing only “what to do” with no “what not to do” lets the model fill the blanks. Write negative constraints in one line.

Step 1 — Specific bans beat vibes

Turn “don’t” into concrete bans (words/structure/invention)—not just “be professional.”

Do not:
- Start with “Absolutely!”, “Great question!”, or “Negative constraints that actually work”
- Invent URLs, paper titles, or citations
- Use more than one emoji
- Add a P.S. unless I ask
- Promise discounts, refunds, or timelines I did not state
If tempted, delete and continue.

Pair with positives: what to do instead (plain opener, “Unknown” for missing links).

Step 2 — Soft-launch note rewrite

Example

Filled prompt

Rewrite this soft-launch note to existing users.
Goal: Tell them the new Guides tab is live; invite feedback.
Format: ≤ 120 words, 3 short paragraphs.
Do not:
- Cheerleader openers
- Invent URLs or user counts
- More than one emoji
- Promise a roadmap date I did not give
Input: [paste rough note]

What good output looks like

  • Opens with the news, not praise for the reader’s question
  • No fake links or “thousands of you already…”
  • Still friendly
  • You can paste into email without scrubbing

Step 3 — Keep the ban list short

If your negatives exceed ~8 bullets, split: one card for voice bans, one for factual bans. Overlong lists get ignored.

Compress my ban list to the 5 highest-impact lines. Keep wording concrete. Do not add new bans I did not imply.
Example

Filled prompt

Homepage subhead for scheduling tool.
Negatives: no "AI-powered magic," no fake "10,000 teams," no empty "seamless."
Return subhead + refused list.

What good output looks like

  • Goal/Format/Boundaries all present for “Ban the specific bad habits that keep sneaking int”
  • One example beats stacked IMPORTANT words
  • Version/date kept when template changes
  • Pass/fail: zero clarifying turns on live task

Negatives need examples

“No fluff” is vague. Show one fluffy sentence and one tight rewrite beside the never-do list.

Keep it real

Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Close the loop

Write one line: next time I run with no negative constraints, I refuse.

One more pass

Re-read your Save-this-card line. If it is vague, rewrite it until a stranger could apply it.

Example

Filled prompt

Landing FAQ answer about pricing.
Negatives: no "contact us for pricing" dodge if page lists a free tier; no fake enterprise logos; no "unlimited" unless my notes say it.
Notes: Free=1 seat; Pro=Unknown on site.
Draft FAQ + refused phrases.

What good output looks like

  • One example beats stacked IMPORTANT words
  • Version/date kept when template changes
  • Pass/fail: zero clarifying turns on live task
  • Goal/Format/Boundaries all present for “Ban the specific bad habits that keep sneaking int”

Red flag

Only louder “do” lines; never-do missing on a risky task—add one clear don’t.

Save this card

Card: A clear “don’t” often beats another louder “do.”. Keep this beside the tool; read before you start.

Wear-test: show your Save card to a teammate for thirty seconds—if they cannot restate the refuse line, tighten the card tonight and date it (Asia/Shanghai).

Before you start

Keep the last failing output visible. You will repair the prompt for “Ban the specific bad habits that keep sneaking” against that failure—not a fresh toy ask. Guide: prompt-negative-constraints. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week for a real task write three negative constraints (no invented numbers, no empty openers, no language mash); fill any missing one.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

PitfallFix
Only “be concise / be nice”Name the banned phrases
40-line constitutionCap ~8; version the rest
Bans without a GoalNegatives support Goal/Format
Never updating after new slop appearsAdd the new phrase to vN changelog
Example

Filled prompt

Temptation: skip the habit for prompt-negative-constraints to save five minutes.
Job still: Ban the specific bad habits that keep
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to prompt-negative-constraints)
  • Still delivers checkable output for “Ban the specific bad habits that keep”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (prompt-negative-constraints #4)

Practice now

Violation probe: one prompt that should trip a negative—confirm refuse (Asia/Shanghai).

Negative drill: three must-not lines above the ask; test one violation path (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight rewrite three vague bans into checkable items (no metaphors / no second person / max 120 words).

One sentence takeaway

Three negative constraints written; fill any missing one before run.

Word-floor practice

Run the Today card once on a real artifact. Write pass/fail + never-do with date Asia/Shanghai. If you only skimmed, do not mark this guide done.

Next

Reject AI slop · GFB pattern · Version templates

← Back to home · Learn · Tools · Compare · Start