Daniele
1b709a880f
The chat agents now treat a stated preference about how something should be written — or a correction to a draft they produced — as durable, and record it in a `## Writing style` section of `user-memory/user.md`: preferred wording, how emails open and close, what changes between the formal and the informal register, and contacts written to differently from everyone else. The section is capped at 10 lines, because it shares `user.md`'s own 40-line budget and per-recipient detail is the half that grows without bound; past that, the whole section moves into its own note and leaves a pointer behind. A rule that turns out to be wrong is corrected in place rather than joined by a second bullet contradicting it. Shipped as the shared fragment `common/writing-style.md`, included by the three `type: chat` agents. Only `assistant` injects `user.md` automatically, so the fragment closes by telling the other two to read it before drafting.
1.5 KiB
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.
## 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.