continuous-learning-v2

Extract reusable coding behaviors from Claude Code session observations with confidence scoring.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Zenobia000/ai-brainstorming --skill continuous-learning-v2-zenobia000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: continuous-learning-v2
Source: https://github.com/Zenobia000/ai-brainstorming/tree/main/.claude/custom-rule%26skill/skills/continuous-learning-v2
Command: npx skills add https://github.com/Zenobia000/ai-brainstorming --skill continuous-learning-v2-zenobia000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers and AI assistants repeatedly forget project-specific coding conventions and best practices across sessions, leading to inconsistent code quality and repeated corrections. This Skill creates an automatic learning system that observes tool use, detects behavioral patterns, and converts them into reusable, confidence-scored instincts.

Core Features & Use Cases

  • Automatic Session Observation: Hooks capture every tool call in Claude Code to build a comprehensive dataset of user behaviors and corrections.
  • Project-Scoped Isolation: React patterns stay in React projects, Python conventions stay in Python projects, and universal security practices are shared globally to prevent cross-project contamination.
  • Confidence-Based Evolution: Patterns are weighted by frequency and can be promoted from project to global scope or evolved into full skills, commands, and specialized agents.

Quick Start

Enable the observation hooks in your Claude Code settings and start working in any git repository to automatically build a library of project-specific instincts.

Frequently Asked Questions about continuous-learning-v2

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically capture coding conventions from Claude Code sessions?

Hook-based observation captures every tool call in Claude Code sessions to build a dataset of user behaviors, which background Haiku analysis then processes to extract reusable coding conventions automatically.

What is project-scoped isolation for coding instincts and why do I need it?

Project-scoped isolation stores coding instincts within specific git repositories to prevent cross-project contamination, keeping React patterns in React projects and Python conventions in Python projects while sharing universal practices globally.

Can I use continuous learning hooks across multiple git repositories?

Yes, continuous learning hooks work across multiple git repositories, capturing project-specific conventions for solo developers and teams while maintaining isolated storage to prevent cross-project pattern contamination.

How does confidence scoring work for extracted coding patterns?

Confidence scoring weights extracted behavioral patterns by frequency, allowing high-confidence instincts to be promoted from project scope to global scope or evolved into full skills, commands, and specialized agents.

What's the best way to turn repeated coding corrections into reusable instincts?

Automating extraction with atomic instinct patterns and confidence scoring converts repeated coding corrections into reusable instincts by observing tool use and detecting behavioral patterns without requiring manual documentation.

Do I need to manually document project conventions for Claude Code to remember them?

No, manual documentation is unnecessary because the system automatically observes tool use during coding sessions, detects behavioral patterns, and converts them into confidence-scored instincts stored with project-scoped isolation.