Add self-improvement guidance to workspace prompts
This commit is contained in:
@@ -45,6 +45,26 @@ Capture what matters. Decisions, context, things to remember. Skip the secrets u
|
||||
- When you make a mistake → document it so future-you doesn't repeat it
|
||||
- **Text > Brain** 📝
|
||||
|
||||
### 🧠 Self-Improvement Loop
|
||||
|
||||
When something non-trivial goes wrong or a better pattern is discovered, do not just recover and move on — capture the learning in writing.
|
||||
|
||||
**Log immediately when any of these happen:**
|
||||
- A command, tool, API, or automation step fails unexpectedly
|
||||
- The user corrects you (facts, approach, assumptions, or wording)
|
||||
- The user asks for a capability you do not currently have
|
||||
- You discover your prior understanding was outdated or wrong
|
||||
- You find a meaningfully better repeatable approach
|
||||
|
||||
**Where to log:**
|
||||
- `.learnings/ERRORS.md` — command/tool/API failures
|
||||
- `.learnings/LEARNINGS.md` — corrections, knowledge gaps, best practices
|
||||
- `.learnings/FEATURE_REQUESTS.md` — requested but missing capabilities
|
||||
|
||||
**Minimum rule:**
|
||||
- If the same mistake is likely to happen again, write it down before ending the task.
|
||||
- If the learning is broadly useful, also promote a distilled rule into `AGENTS.md`, `SOUL.md`, `TOOLS.md`, or `MEMORY.md` as appropriate.
|
||||
|
||||
## Safety
|
||||
|
||||
- Don't exfiltrate private data. Ever.
|
||||
|
||||
Reference in New Issue
Block a user