claude/skills/continuous-learning/SKILL.md
Automatically extract reusable patterns from Claude Code sessions and save them as learned skills for future use.
npx skillsauth add channinghe/dotfiles continuous-learningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Automatically evaluates Claude Code sessions on end to extract reusable patterns that can be saved as learned skills.
This skill runs as a Stop hook at the end of each session:
~/.claude/skills/learned/Edit config.json to customize:
{
"min_session_length": 10,
"extraction_threshold": "medium",
"auto_approve": false,
"learned_skills_path": "~/.claude/skills/learned/",
"patterns_to_detect": [
"error_resolution",
"user_corrections",
"workarounds",
"debugging_techniques",
"project_specific"
],
"ignore_patterns": [
"simple_typos",
"one_time_fixes",
"external_api_issues"
]
}
| Pattern | Description |
|---------|-------------|
| error_resolution | How specific errors were resolved |
| user_corrections | Patterns from user corrections |
| workarounds | Solutions to framework/library quirks |
| debugging_techniques | Effective debugging approaches |
| project_specific | Project-specific conventions |
Add to your ~/.claude/settings.json:
{
"hooks": {
"Stop": [{
"matcher": "*",
"hooks": [{
"type": "command",
"command": "~/.claude/skills/continuous-learning/evaluate-session.sh"
}]
}]
}
}
/learn command - Manual pattern extraction mid-sessiondevelopment
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
development
# Verification Loop Skill A comprehensive verification system for Claude Code sessions. ## When to Use Invoke this skill: - After completing a feature or significant code change - Before creating a PR - When you want to ensure quality gates pass - After refactoring ## Verification Phases ### Phase 1: Build Verification ```bash # Check if project builds npm run build 2>&1 | tail -20 # OR pnpm build 2>&1 | tail -20 ``` If build fails, STOP and fix before continuing. ### Phase 2: Type Check
tools
Tooling and verification. Apply when encountering unfamiliar third-party libraries, framework updates, uncertain parameter types, verifying best practices, or uncertain API parameters.
development
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.