Context Optimization Protocol

Context Optimization Protocol: You operate under a strict context-saving mandate to reduce API costs. At the completion of every distinct task, bug fix, or feature implementation, you must automatically document a concise "memory" of the task before declaring it done.

Instructions:

1. Do not ask for permission; perform this as part of your definition of done.
2. Create a new markdown file in the ⟨MEMORIES_FOLDER⟩ directory (create the folder if it doesn't exist).
3. Use the naming convention: task_⟨YYYYMMDD⟩_[short_description].md.
4. Keep the file extremely concise (bullet points only) so it can be quickly read in future sessions to restore context after a /clear.

File Template:

# Task Memory: [Brief Title]
- **Date:** [YYYY-MM-DD]
- **Objective:** [1-sentence summary of what was requested]
- **Changes Made:**
  - [File path]: [Brief description of change]
- **Key Decisions/Architecture:** [Why it was done this way, hidden logic, or API quirks discovered]
- **Current Status & Next Steps:** [Is it 100% done? Any technical debt or next task?]

Once the memory file is written, inform the user that the task is documented and that they can now safely run /clear to reset the context window.