From d4c460583b5912abb63b91e0a5f18e5008ea0fdf Mon Sep 17 00:00:00 2001 From: Michael Panchenko Date: Wed, 13 May 2026 18:52:25 +0200 Subject: [PATCH] Improve onboarding and memory maintenance wording --- .../config/prompt_templates/simple_tool_outputs.yml | 10 ++-------- src/serena/resources/memory_maintenance.md | 2 ++ 2 files changed, 4 insertions(+), 8 deletions(-) diff --git a/src/serena/resources/config/prompt_templates/simple_tool_outputs.yml b/src/serena/resources/config/prompt_templates/simple_tool_outputs.yml index 168840ff..9f5e058d 100644 --- a/src/serena/resources/config/prompt_templates/simple_tool_outputs.yml +++ b/src/serena/resources/config/prompt_templates/simple_tool_outputs.yml @@ -14,8 +14,8 @@ prompts: Target memory layout — use the `write_memory` tool, one call per memory: - * `mem:core` — top-level routing/source map: a terse index pointing at the focused memories - below, plus only those project-wide invariants that don't belong in a focused memory. + * `mem:core` — top-level source map and project-wide invariants that don't belong in a + focused memory. * `mem:tech_stack` — language(s), framework(s), build tools, package manager, version pins where they matter. * `mem:suggested_commands` — project commands the user will actually run (dev, test, lint, @@ -34,12 +34,6 @@ prompts: Acquire information using the available tools. Read only the files needed; do not load entire directory trees. If essential information is missing, ask the user. - Memory body style (full rules in `mem:{{ memory_maintenance_name }}`): dense agent notes — - terse bullets, invariants, paths, commands. No self-referential cues ("Use when…", - "Start here…", "Read before…"); routing belongs in `mem:core` upstream, not inside the - body it points to. References to other memories use `` `mem:NAME` `` (backticked, with - the `mem:` prefix). - When all memories are written, sanity-check the references by mentioning that the user can run `serena memories check` from the project root. diff --git a/src/serena/resources/memory_maintenance.md b/src/serena/resources/memory_maintenance.md index 567d39c3..cfb4c05c 100644 --- a/src/serena/resources/memory_maintenance.md +++ b/src/serena/resources/memory_maintenance.md @@ -11,6 +11,8 @@ - Routing can live outside core memories when needed, but core memories own most module-level routing because they are read before focused memories in that subfolder. - Top-level/startup memory is `mem:core`; top-level memory in each memory subfolder is `/core` (for example `mem:frontend/core`). - Memory references must use a mem: prefix inside backticks, e.g. `mem:frontend/core`. +- Do not add an index that simply re-lists the focused-memory names, the memory name list is already visible. + Only add routing pointers when a target memory's name is not self-explanatory or when a some aspect should be routed to multiple memories. ## Style