This skill captures learnings to staging. Triggers on: "that worked", "it's fixed", "working now", "problem solved", "save this", "remember this", /learn command, or when user corrects Claude ("use X instead of Y", "no, do X", "always X", "never Y", "I prefer X"). Also trigger after solving non-obvious problems together.
From learning-loopnpx claudepluginhub app-vitals/marketplace --plugin learning-loopThis skill uses the workspace's default tool permissions.
references/signal-patterns.mdCapture learnings to the staging area in CLAUDE.local.md.
Keep it simple: Just capture the insight. Don't over-structure. /learn-promote will figure out where it belongs.
Capture when you notice:
Don't capture:
Search CLAUDE.local.md for similar content:
grep -i "keyword" CLAUDE.local.md
If similar exists, don't duplicate. Offer to update if the new learning adds context.
Ask yourself:
Keep proposals minimal - don't interrupt the flow:
Got it - want me to save "use uv instead of pip" as a learning?
Or for discoveries:
That was a non-obvious fix. Save to learnings?
"Prisma pool errors in serverless → use connection pooling"
Add to the # Staged Learnings section in CLAUDE.local.md (gitignored):
# Staged Learnings
- Use uv instead of pip for Python package management
- Always run tests before committing
# Personal Learnings
(these are already promoted/permanent - don't add here)
IMPORTANT: Always add new learnings under # Staged Learnings, never under other sections. If the section doesn't exist, create it at the top of the file. The # Personal Learnings section (and any other sections) contains already-promoted items that should not be mixed with staged ones.
Format: Just a simple bullet point. Natural language. No complex tags.
Saved to staged learnings. Run /learn-promote when ready to route.
Skip if:
Capture if:
All staged learnings go to CLAUDE.local.md (automatically gitignored).
For promotion to final destinations, use /learn-promote.