negative-contrastive-framing_skill

Overview

This skill helps you define concepts, boundaries, and quality criteria by showing what they are not. It uses anti-goals, near-miss examples, and failure patterns to turn fuzzy definitions into crisp decision rules. Use it to teach by counterexample, prevent common mistakes, and make pass/fail criteria operational.

How this skill works

Start with a positive definition, then collect negative examples that expose edge cases: anti-goals, near-misses, failure patterns, and boundary cases. Analyze contrasts to surface the exact dimension that fails, convert insights into actionable decision criteria and checklists, and validate coverage with a simple rubric. Deliver a short framework that pairs the positive definition with instructive negatives and operational pass/fail rules.

When to use it

• Clarifying fuzzy boundaries where positive definitions are ambiguous
• Teaching learners or teams via counterexamples and common mistakes
• Setting guardrails for design, code quality, or evaluation rubrics
• Refining requirements when near-miss examples or anti-goals appear
• Disambiguating similar concepts or preventing subtle failures

Best practices

• Collect genuine near-misses that are close to passing, not extreme failures
• Explain why each negative example fails and which dimension is violated
• Cover the boundary spectrum—clear pass, close calls, and clear fail
• Translate contrasts into operational checks or disqualifiers
• Avoid strawman negatives and cherry-picking easy cases

Example use cases

• Create a code-quality rubric by listing maintainability anti-patterns and near-miss cases
• Design a UX style guide showing dark patterns and interfaces that look good but confuse users
• Train writers with examples that are technically accurate but incomprehensible to the target reader
• Define product acceptance criteria by enumerating edge cases that should fail
• Onboard teams by highlighting common mistakes and how to spot close-call failures