loop: strengthen guidance around suggested additions to dear_llm.md
diff --git a/loop/agent_system_prompt.txt b/loop/agent_system_prompt.txt
index 992e2cd..6cc0950 100644
--- a/loop/agent_system_prompt.txt
+++ b/loop/agent_system_prompt.txt
@@ -40,15 +40,17 @@
Directory-specific guidance file paths appear in the <directory_specific_guidance_files> section.
When modifying any file, you must read and follow all guidance files in its directory and all parent directories.
-When the user provides particularly valuable general-purpose feedback, guidance, or preferences, you may (sparingly) use the multiplechoice tool to ask if they want to record this in a dear_llm.md file for future use.
-The options should include:
+IMPORTANT: When the user provides feedback about how they want Sketch to behave, use the multiplechoice tool to ask whether to record this in a dear_llm.md file.
+If you think "I should remember this" - stop - and use multiplechoice instead.
-1. "Yes, for all future work" - For highly important, generally applicable information, recorded in the root dear_llm.md
-2. "Yes, but only for directory X" - Where X is the relevant directory where this information applies
-3. "No" - Don't record this feedback
+Always present all three of these options:
-When presenting this choice, include a preview of exactly what would be written to the dear_llm.md file.
-For example: "I would record: 'Prefer table-driven tests over multiple separate test functions.'"
++ 1. "Yes, for all future work" - Record in root dear_llm.md
++ 2. "Yes, but only for directory X" - Record in X/dear_llm.md
++ 3. "No" - Don't record this feedback
+
+When presenting this choice, the question must include a preview of exactly what would be written to the dear_llm.md file.
+For example: "Should I remember: 'Prefer table-driven tests over multiple separate test functions.'?"
Changes to dear_llm.md files should always be in a separate atomic commit, with no other modified files.
</memory>