Learn rule
Skill henriquescastilho/my-claude/.codex/vendor_imports/claude/marketplaces/pro-workflow/skills/learn-rule
Capture a correction or lesson as a persistent learning rule with category, mistake, and correction. Stores, categorises, and retrieves rules for future sessions. Use after mistakes or when the user says "remember this", "don't forget", "note this", or "learn from this".From its SKILL.md
npx -y skills add henriquescastilho/my-claude --skill learn-ruleAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 360 tokens by cl100k_base, as published. Nobody here has run it
Learn Rule
Capture a lesson from the current session into permanent memory.
Trigger
Use when the user says "remember this", "add to rules", "don't do that again", or after a mistake is identified.
Workflow
- Identify the lesson — what mistake was made? What should happen instead?
- Format the rule with full context.
- Propose the addition and wait for user approval.
- After approval, persist to LEARNED section or project memory.
Format
[LEARN] Category: One-line rule
Mistake: What went wrong
Correction: How it was fixed
Categories
| Category | Examples |
|---|---|
| Navigation | File paths, finding code, wrong file edited |
| Editing | Code changes, patterns, wrong approach |
| Testing | Test approaches, coverage gaps, flaky tests |
| Git | Commits, branches, merge issues |
| Quality | Lint, types, style violations |
| Context | When to clarify, missing requirements |
| Architecture | Design decisions, wrong abstractions |
| Performance | Optimization, O(n^2) loops, memory |
Example
Recent mistake: Edited wrong utils.ts file
[LEARN] Navigation: Confirm full path when multiple files share a name.
Add to LEARNED section? (y/n)
Guardrails
- Always wait for user approval before persisting.
- Keep rules to one line — specific and actionable.
- Bad: "Write good code". Good: "Always use snake_case for database columns".
- Include the mistake context so the rule makes sense later.
Output
- The proposed
[LEARN]rule with category - Confirmation after persisting
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.