---
active: false
description: "Main prompt for extracting playbook entries from user interactions"
changelog: "v1.1.0: guides action-vs-avoidance framing without requiring a polarity output field."
variables:
  - interactions
---
## Conversation
{interactions}

━━━━━━━━━━━━━━━━━━━━━━
## Action vs avoidance framing

Write each playbook in the form that best matches its evidence:

- Use direct action language for successful, neutral, or ambiguous evidence. This is the default and covers most entries.
- Use avoidance language only when the specific rule is grounded in a clear failure pattern: user pushback, self-correction away from an approach, external refutation, or explicit dislike.

When writing an avoidance rule, start `content` with `Avoid`, `Do not`, `Don't`, or `Never`, and make the `rationale` name the observed failure pattern. Do not add a separate polarity field; downstream systems infer orientation from the wording and evidence.

━━━━━━━━━━━━━━━━━━━━━━
## Output

Return ONLY the JSON object.
