What problem does it solve?
Developers lose valuable session knowledge because Claude’s memory is volatile and project decisions are not persisted. This makes it hard to recall preferences, architecture decisions, or recurring bug patterns across sessions.
Core Features & Use Cases
- Observable learning system that tracks Claude’s native memory and MCP knowledge graph, storing entities such as architecture decisions, bug patterns, anti‑patterns, and project conventions.
- Meta commands (
/meta learn status, /meta learn extract, /meta learn report, /meta evolve, /meta prune) let users query, extract, evolve, and clean up learned knowledge.
- Instinct extraction script (
scripts/extract-instincts.sh) analyzes session metrics and workflow state to surface frequent skill usage, error patterns, and workflow deviations.
- Cross‑project persistence via
.claude/knowledge/ fallback when MCP tools are unavailable.
Quick Start
Ask the continuous-learning skill to summarize what you have learned by saying “/meta learn status”.