73 Close Lessons Learn 150
Productivity73-close-lessons-learn-15073 Close Lessons Learn 150 is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
[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, updating Session State, or enhancing Project Architecture Quick Reference with new insights.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/context-management/73-close-lessons-learn-150-mykhailodmytriakha-my-preacher-helper/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/73-close-lessons-learn-150, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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
- Open
MEMORY.md(repo root). - Append a new Lesson to
## 🆕 Lessons (Inbox)using this template:
### <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
## 💎 Long-Term Memoryas a protocol:- Format: Context → Protocol → Reasoning.
-
Update Session State only if it affects the current task.
-
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.