What is the purpose of the lessons-learn skill?

It captures technical insights and solutions after a problem is solved, storing them in a structured pipeline to prevent the same issues from recurring.

Where does this skill store its recorded information?

It primarily manages a file named MEMORY.md at the root of your repository and also updates your Project Architecture Quick Reference document.

Does this skill help with project onboarding?

Yes, by maintaining a historical record of lessons and a clear architecture reference, it provides vital context and 'tribal knowledge' for new developers.

How does the memory pipeline work?

Insights start in the Inbox, move to Short-Term Memory as patterns emerge, and are eventually promoted to Long-Term Memory as stable engineering protocols.

When should I trigger this skill during development?

You should use it whenever a bug is fixed, a user confirms a successful change, a non-obvious root cause is identified, or new architectural insights are gained.

Lessons Learned & Memory Manager

Name: Lessons Learned & Memory Manager
Author: MykhailoDmytriakha

byMykhailoDmytriakha

Aprendizaje y Documentación

Captures architectural insights and technical solutions into a structured memory pipeline to prevent recurring issues and build project intelligence.

Acerca de

This skill implements a sophisticated knowledge management system within Claude Code by automating the recording of lessons in a dedicated MEMORY.md file. It facilitates a tiered memory pipeline—moving insights from an initial inbox to short-term patterns and eventually stable long-term protocols—while simultaneously keeping project architectural references up to date. By systematically documenting problems, solutions, and principles, it ensures that every solved bug and architectural decision becomes a permanent part of the project's intelligence, significantly improving long-term maintainability and future problem-solving efficiency.

Características Principales

Protocol promotion for converting insights into stable engineering rules
Automated lesson recording using standardized problem-solution templates
0 GitHub stars
Pattern recognition for recurring bugs and technical debt
Tiered memory pipeline (Inbox, Short-Term, and Long-Term storage)
Automatic synchronization with Project Architecture Quick Reference

Casos de Uso

Converting recurring manual fixes into standardized development protocols
Building a project-specific knowledge base of architectural decisions
Documenting the root cause and fix for complex, non-obvious bugs

Acerca de

Características Principales

Protocol promotion for converting insights into stable engineering rules
Automated lesson recording using standardized problem-solution templates
0 GitHub stars
Pattern recognition for recurring bugs and technical debt
Tiered memory pipeline (Inbox, Short-Term, and Long-Term storage)
Automatic synchronization with Project Architecture Quick Reference

Casos de Uso

Converting recurring manual fixes into standardized development protocols
Building a project-specific knowledge base of architectural decisions
Documenting the root cause and fix for complex, non-obvious bugs