Claude-skill-registry 73-close-lessons-learn-150
[73] CLOSE. Record and maintain Lessons in MEMORY.md after a problem is solved or the user confirms success. Use when capturing a new lesson, moving lessons through the pipeline, or enhancing Project Architecture Quick Reference with new insights.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/73-close-lessons-learn-150" ~/.claude/skills/majiayu000-claude-skill-registry-73-close-lessons-learn-150 && rm -rf "$T"
manifest:
skills/data/73-close-lessons-learn-150/SKILL.mdsource content
Close-Lessons-Learn 150 Protocol
Goal
Capture durable learning from a solved problem and keep the Memory pipeline consistent.
When to use
Use this skill when:
- The user confirms a fix worked (e.g., "works", "fixed", "отлично").
- A non‑obvious bug or root cause was discovered.
- A recurring pattern should be turned into a protocol.
- New architectural insights emerge that should be documented in Project Architecture Quick Reference.
Workflow
- Read the active session log in
for evidence and context..sessions/SESSION_[date]-[name].md - Open
(repo root).MEMORY.md - Append a new Lesson to
using this template:## 🆕 Lessons (Inbox)
### <YYYY-MM-DD> <Short title> **Problem:** <what was broken> **Attempts:** <what was tried, if any> **Solution:** <what fixed it> **Why it worked:** <causal explanation> **Principle:** <one-sentence rule for the future>
-
If 3+ related lessons exist, create a Short‑Term entry:
- Move the related lessons (or summarize them) into
.## 🔄 Short-Term Memory - Write a common pattern and an emerging principle.
- Move the related lessons (or summarize them) into
-
If a principle is stable, promote it to
as a protocol:## 💎 Long-Term Memory- Format: Context → Protocol → Reasoning.
-
Review Project Architecture Quick Reference and enhance if needed:
- Check if the lesson reveals new architectural insights (new directories, patterns, workflows)
- Add missing directories, workspaces, or key patterns discovered during work
- Update existing entries with new information or clarifications
- Keep the reference current and comprehensive
Output expectations
- Report exactly what you recorded or moved.
- If you did not write a lesson, say why.
- If you updated the Project Architecture Quick Reference, specify what was added or modified.
Session Log Entry (MANDATORY)
After completing this skill, write to
.sessions/SESSION_[date]-[name].md:
### [HH:MM] Close-Lessons-Learn 150 Complete **Lessons Recorded:** <count> **Type:** <Inbox/Short/Long-Term> **Key Principle:** <one-line summary>