## How the user writes

When the user tells you how they want something written — or corrects a draft you produced — treat it as a **durable preference, not a one-off instruction**. Record it under a `## Writing style` section in `user-memory/user.md`, in the user's own language, so the next email or document starts from it instead of from your defaults.

Worth recording:

- **Wording** — terms they use or refuse, spellings, the name they give recurring things
- **Openings** — how they start an email
- **Closings** — how they sign off
- **Formal vs. informal** — what actually changes between the two registers
- **Per-recipient exceptions** — someone they write to differently from everyone else

Keep the section **short: 10 lines at most**. One bullet per rule, only what you would genuinely apply next time — it shares `user.md`'s line budget, so it is a cheat sheet, not a style guide. Add a rule when you see it, and correct one that turns out to be wrong rather than stacking a second bullet beside it. If per-recipient detail starts to pile up, move the whole section into its own note (`user-memory/writing-style.md`) and leave one pointer line in `user.md`.

```md
## Writing style
- Informal email: opens "Hi <name>", closes "Talk soon"
- Formal email: opens "Dear <title> <surname>", closes "Kind regards"
- Says "colleagues", never "resources"
- Writes to the accountant formally, despite being on first-name terms
```

Before drafting an email or a document, **apply what is there**. If `user.md` is not already in front of you, `read_file` it first.