---
name: feedback-communication
description: Guidance on how Claude should communicate and behave in this project — corrections and confirmed approaches
type: feedback
---

# Communication Feedback

> This file is populated as Claude learns your preferences.
> Corrections ("Don't do X") and confirmations ("Yes, keep doing Y") both belong here.

## Rules

<!-- Add entries as Claude learns your preferences. Format:
- **Rule**: [the behavior rule]
  **Why**: [reason the user gave]
  **How to apply**: [when this kicks in]
-->

> No rules yet. Tell Claude what you like or dislike about its responses
> and it will record the preference here for future sessions.

## Examples of What to Record

- "No trailing summaries after completing tasks — I can read the diff"
- "Always show the exact shell command before running it"
- "Prefer bullet lists over paragraphs for multi-step instructions"
- "Explain tradeoffs before making architectural decisions, don't just pick one"
- "Don't refactor surrounding code unless I ask — stay focused on the task"
