continuous-learning-skill

What I do

The full memory-hygiene procedure (user AGENTS.md §Memory Hygiene defers here): capture reusable patterns/decisions/insights from coding sessions into LEARNINGS/ markdown, scoped project or user.

When to use me

Before any review/plan/debug: recall first. After non-trivial fixes/decisions: capture (one entry per fix/decision — never routine commits, secrets, PII, or file contents).

Storage

LEARNINGS/<category>/<slug>.md is the single store (the memory tool has no v2 plugin; the manifest auto-injects per session via the local plugin — glob+read of LEARNINGS/ is the fallback). Categories: patterns/ · decisions/ · solutions/ (short-form) · conventions/ · anti-patterns/ (short-form).

Scope: project = repo learnings (the repo's own LEARNINGS/); user = cross-project preferences (~/.config/opencode/LEARNINGS/). Project detection: git toplevel + repo name. Promote project → user only when a learning proved true in ≥2 projects.

Entry format

[Category]: [Title]
Scope: [project|user]
Confidence: [0.3-0.9]
Trigger: [when this applies]
Action: [what to do]
Context: [when/where this applies]
Detail: [what the pattern/decision is]
Rationale: [why this approach]
Evidence: [what observations support it]
Files: [related paths, if any]

Core workflow

1. Analyze session: files touched, decisions + rationale, errors → solutions, patterns used, config/dependency changes, user corrections (highest-value signal — a wrong assumption was corrected).
2. Extract atomic instincts: trigger + action + confidence + domain + scope + evidence. One instinct per fact; confidence from evidence strength.
3. Categorize per the folder table above.
4. Write the entry — always, in the body format above.
5. Update LEARNINGS/_index.md in the same write as the entry file: insert the new entry directly below the single <!-- Entries are appended here automatically when new learnings are saved --> marker — never re-add the marker (duplicates split the index), never leave the entry unwritten (an unindexed learning is invisible to the _index.md fallback search). Match the existing entry shape: ### <title> + Category / File / Confidence / Scope / (Date) / Summary lines. When an existing learning's facts change, update its index entry (heading + summary) in the same write — a corrected file under a stale index entry is the exact drift this rule exists to kill.
6. Suggest applications: where the learning should change behavior next session (one line).
7. Evolve: a learning re-confirmed in later sessions raises confidence; contradicted → revise or demote (never silently delete — mark superseded).