toga-ai 1.0.745 → 1.0.746

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.745",
+  "version": "1.0.746",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",

package/rules/common/communication.md

@@ -72,3 +72,22 @@ back to dense wording and teammates missed critical details. To stop that, a hoo
   context right before each reply. So the model is reminded every turn, not just once.
 - The hook is wired in `.claude/settings.json` and ships to every repo on `npx toga-ai`.
 - It never blocks anything; it only nudges. To silence it, set `TOGA_PLAIN_TALK_DISABLED=1`.
+
+## Remember each person across sessions
+
+The "mirror the person" rule (rule 7) only sees the current session. That is not enough —
+you should learn how each developer likes to be talked to and remember it **for good**, so
+they never have to tell you twice. Use the developer's **local Claude memory** for this.
+
+- **Keep a per-person communication profile in local memory** — e.g. a `user`-type memory
+  named `user-communication-profile`. It loads at the start of every session, so you apply
+  their known style before you write a word.
+- **Save a preference the moment they state it — do not wait to be asked.** If a developer
+  says "speak plainly", "don't use the word X", "keep it short", or corrects your wording,
+  write it into their profile right then. An explicit preference is the strongest signal.
+- **At `/capture`, review and update the profile** with any clear new pattern in how they
+  communicated this session (see the capture skill's step for this).
+- **Only record clear signals.** Prefer what they say directly over what you infer. Keep the
+  note short and readable; a wrong guess is worse than no guess.
+- **This profile is private and per-person. Never put it in the team knowledge base** — it
+  lives only in that developer's local memory, on their machine.

package/scripts/hooks/plain-talk.js

@@ -57,6 +57,11 @@ function reminder() {
     'register. Reuse their own terms for things. Match their length: if they write short,',
     'you write short. Never fake misspellings or bad grammar; be natural, just familiar.',
     '',
+    'REMEMBER THEM ACROSS SESSIONS: this developer may have a saved communication profile in',
+    'their local Claude memory (e.g. user-communication-profile) — apply it. If they state a',
+    'preference (a word to avoid, a length, a tone), save it to that profile right away so it',
+    'persists to the next session; do not make them tell you twice.',
+    '',
     'Before you send: could you cut half the words and keep the meaning? Is any word too',
     'rare for a non-native reader? Is the main point on the first line?',
     '</system-reminder>',

package/skills/capture/SKILL.md

@@ -155,6 +155,25 @@ Relay the subagent's final report to the developer: what was written, the publis
 standards/architecture). If the subagent reported everything was NO-OP, relay: "Nothing here
 is durable team knowledge — KB unchanged."
 
+## Step 6 — Update how to talk to this developer (local memory, private — never pushed)
+
+Capture is also when you record **how the developer likes to be communicated with**, so the
+next session already knows. This is a **main-thread, LOCAL memory** action — it never touches
+`knowledge/` and is never pushed to the team repo. (See "Remember each person across
+sessions" in `rules/common/communication.md`.)
+
+1. Look back at how the developer communicated this session — the words they used, the length
+   and tone they preferred, and any preference they stated ("speak plainly", "don't use the
+   word X", "keep it short") or any wording of yours they corrected.
+2. Update their per-person profile in **local Claude memory** (a `user`-type memory named
+   `user-communication-profile`, plus its `MEMORY.md` pointer). Add any clear new signal;
+   don't duplicate what's already there.
+3. **Only record clear signals** — prefer what they said directly over what you infer. Keep
+   the note short and readable. If nothing new came up, do nothing.
+
+An explicit preference should already have been saved the moment it was stated; this step is
+the backstop that also catches patterns.
+
 ### After Capture
 
 After the push is confirmed, suggest the developer persist session state: