---
name: <what the user wants you to do (or stop doing)>
description: <one-line — describes the rule/preference, not the incident that prompted it>
type: feedback
created: YYYY-MM-DD
# updates: [older_feedback_file.md]   # only if this REVERSES a prior rule
---

**Why:** One short paragraph. What's the reason behind this preference?
Without the why, a future agent may follow the rule mechanically and miss
cases where the *reason* applies but the *letter* doesn't.

**How to apply:** Concrete trigger + action. "When the user asks me to X,
I should do Y instead of Z." If there's a checklist, bullet it.

## Rules (if multi-part)

- Rule 1
- Rule 2

## Exceptions

When does this rule NOT apply? An honest exceptions section beats a
too-strict rule the agent has to silently break.