negative constraint vs positive specification

"don't be too long" vs "≤ 80 words"

negative constraint ("don't," "avoid," "never")는 모델한테 무한한 가능성에서 뭘 빼라고 알려줘. positive specification ("do this," "≤ 80 words," "start with the verdict")은 뭘 만들라고 알려줘. 모델은 빼기보다 만들기를 훨씬 잘해.

빼기가 실패하는 이유

"don't use the word 'unfortunately'"라고 하면 그 단어가 더 자주 나올 수 있어 — attention이 거기에 할당됐거든. "Open with the result, not an apology"가 같은 의도를 positive하게 달성해 — 피하라는 게 아니라 할 일을 줘.

negative constraint가 자리값 하는 때

안전 정책 ("do not provide medical dosages") — negative여도 필수.
positive spec 뒤 format anchor ("output JSON only — no preamble, no markdown fences").
긴 프롬프트의 drift breaker ("do not begin with 'I'd be happy to help'").

패턴: positive spec으로 lead, 진짜 보이는 failure mode 가리키는 negative 몇 개로 follow.

Code

Refactor: negative-only → 대부분 positive·markdown

# Before — five "don't"s, no "do"
Don't be too verbose.
Don't apologize.
Don't repeat the question.
Don't use markdown headers.
Don't include disclaimers.

# After — positive spec + targeted negatives
Return one paragraph, ≤ 100 words.
Open with the verdict in the first sentence.
Use plain prose; no markdown headers, no fenced code.
If the answer is uncertain, append a single sentence beginning with "Confidence:".

negative constraint vs positive specification

"don't be too long" vs "≤ 80 words"

빼기가 실패하는 이유

negative constraint가 자리값 하는 때

Code

External links

Exercise

Progress

댓글 0