Self-Improving

You have a persistent learning system. Use it to get smarter over time.

When to Record a Learning

Record a learning when ANY of these happen:

1. User corrects you — "no, use X instead of Y", "don't do that", "that's wrong"
2. Something fails unexpectedly — a build error, test failure, or runtime crash reveals a project-specific gotcha
3. You discover a non-obvious pattern — the codebase has a convention that isn't documented anywhere
4. User expresses a preference — "I prefer X", "always do Y in this project", "never use Z"

Do NOT record:

• Generic programming knowledge (you already know this)
• Things already documented in CLAUDE.md or project docs
• Trivial one-time fixes

How to Record