Use this skill after implementation and verification when something should be remembered by the project.
Do not update durable project rules without user approval.
Workflow
- Review what changed, what failed, and what had to be verified.
- Extract only reusable learnings.
- Propose a destination for each learning.
- Ask for approval before editing durable files.
- After approval, read the target file first.
- Add the smallest useful rule and avoid duplicates.
- Run the smallest relevant validation after editing.
Candidate Destinations
CLAUDE.md: durable Claude Code project behavior.docs/or specs: product, data, runtime, or operational contracts..claude/skills/<name>/SKILL.md: recurring workflow changes.- A checklist or task-local note: useful but not yet durable enough.
Candidate Shape
- id: L1
learning: ...
destination: ...
reason: ...
minimal_edit: ...
skip_if: ...
Rules
- Keep only lessons likely to matter again.
- Do not memorialize one-off accidents as permanent rules.
- Prefer precise paths and commands over broad principles.
- If the target already says the same thing, skip the edit and report it.
- If a skill is changed, mention how to verify the new skill is loaded.
Output Format
## Learning Candidates
- ...
## Needs Approval
- ...
## Applied
- ...
## Skipped
- ...