shancheas
f2f0be111a
- Added .cursor/sessions/* to .gitignore to prevent session files from being tracked. - Enhanced coding standards in SKILL.md by adding semicolons to TypeScript examples for consistency. - Improved formatting in continuous learning, detail layout, and other SKILL.md files for better readability. These changes aim to streamline development processes and maintain code quality across the project.
1.6 KiB
1.6 KiB
/learn - Extract Reusable Patterns
Analyze the current session and extract any patterns worth saving as skills.
Trigger
Run /learn at any point during a session when you've solved a non-trivial problem.
What to Extract
Look for:
-
Error Resolution Patterns
- What error occurred?
- What was the root cause?
- What fixed it?
- Is this reusable for similar errors?
-
Debugging Techniques
- Non-obvious debugging steps
- Tool combinations that worked
- Diagnostic patterns
-
Workarounds
- Library quirks
- API limitations
- Version-specific fixes
-
Project-Specific Patterns
- Codebase conventions discovered
- Architecture decisions made
- Integration patterns
Output Format
Create a skill file at .agents/skills/learned/[pattern-name].md:
# [Descriptive Pattern Name]
**Extracted:** [Date]
**Context:** [Brief description of when this applies]
## Problem
[What problem this solves - be specific]
## Solution
[The pattern/technique/workaround]
## Example
[Code example if applicable]
## When to Use
[Trigger conditions - what should activate this skill]
Process
- Review the session for extractable patterns
- Identify the most valuable/reusable insight
- Draft the skill file
- Ask user to confirm before saving
- Save to
.agents/skills/learned/
Notes
- Don't extract trivial fixes (typos, simple syntax errors)
- Don't extract one-time issues (specific API outages, etc.)
- Focus on patterns that will save time in future sessions
- Keep skills focused - one pattern per skill