agentleFS
PatriotAgenticLLCPatriotAgenticLLC/better_claude_skillz/skills/continuous-learning-v2/SKILL.md

continuous-learning-v2

Skill3 starsChanged 5 months agoMITView on GitHub

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.

29 other projects use a version of this, 26 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use springboot-tdd, e2e-testing and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AshfaqbsSkill

    springboot-tdd

    Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

    Also in 4 projects that use this

  • etewiahSkill

    e2e-testing

    Playwright E2E testing and Lighthouse performance auditing. Use when setting up E2E tests, running Playwright tests, performing Lighthouse audits, or debugging E2E test failures.

    Also in 3 projects that use this

  • OpenAISkill

    finishing-a-development-branch

    Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

    Also in 3 projects that use this

  • OpenAISkill

    dispatching-parallel-agents

    Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

    Also in 3 projects that use this

  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • +6 more from openai

The file

We split this skill into the rules it gives an agent

7 rules. 5 are common, 1 is distinctive, and 1 is very specific to this project.

  • 5

    Common

    Most of the 27 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add to your ~/.claude/settings.json:

    line 95
  2. Distinctive:

    When you use the Skill Creator GitHub App, it now generates both:

    line 199
  3. Common:

    Every tool call is observed

    line 231
  4. Common:

    No patterns are missed

    line 232
  5. Common:

    Stop hook still runs (but now also feeds into v2)

    line 239
  6. Common:

    Only instincts (patterns) can be exported

    line 245
  7. Common:

    No actual code or conversation content is shared

    line 246

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Continuous Learning v2 - Instinct-Based Architecture

An advanced learning system that turns your Claude Code sessions into reusable knowledge through atomic "instincts" - small learned behaviors with confidence scoring.

What's New in v2

Featurev1v2
ObservationStop hook (session end)PreToolUse/PostToolUse (100% reliable)
AnalysisMain contextBackground agent (Haiku)
GranularityFull skillsAtomic "instincts"
ConfidenceNone0.3-0.9 weighted
EvolutionDirect to skillInstincts -> cluster -> skill/command/agent
SharingNoneExport/import instincts

The Instinct Model

An instinct is a small learned behavior:

---
id: prefer-functional-style
trigger: "when writing new functions"
confidence: 0.7
domain: "code-style"
source: "session-observation"
---

# Prefer Functional Style

## Action
Use functional patterns over classes when appropriate.

## Evidence
- Observed 5 instances of functional pattern preference
- User corrected class-based approach to functional on 2025-01-15

Properties:

  • Atomic -- one trigger, one action
  • Confidence-weighted -- 0.3 = tentative, 0.9 = near certain
  • Domain-tagged -- code-style, testing, git, debugging, workflow, etc.
  • Evidence-backed -- tracks what observations created it

How It Works

Session Activity
      |
      | Hooks capture prompts + tool use (100% reliable)
      v
+---------------------------------------------+
|         observations.jsonl                   |
|   (prompts, tool calls, outcomes)            |
+---------------------------------------------+
      |
      | Observer agent reads (background, Haiku)
      v
+---------------------------------------------+
|          PATTERN DETECTION                   |
|   - User corrections -> instinct            |
|   - Error resolutions -> instinct           |
|   - Repeated workflows -> instinct          |
+---------------------------------------------+
      |
      | Creates/updates
      v
+---------------------------------------------+
|         instincts/personal/                  |
|   - prefer-functional.md (0.7)              |
|   - always-test-first.md (0.9)              |
|   - use-zod-validation.md (0.6)             |
+---------------------------------------------+
      |
      | /evolve clusters
      v
+---------------------------------------------+
|              evolved/                        |
|   - commands/new-feature.md                  |
|   - skills/testing-workflow.md               |
|   - agents/refactor-specialist.md            |
+---------------------------------------------+

Quick Start

1. Enable Observation Hooks

Add to your ~/.claude/settings.json:

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "*",
      "hooks": [{
        "type": "command",
        "command": "~/.claude/skills/continuous-learning-v2/hooks/observe.sh pre"
      }]
    }],
    "PostToolUse": [{
      "matcher": "*",
      "hooks": [{
        "type": "command",
        "command": "~/.claude/skills/continuous-learning-v2/hooks/observe.sh post"
      }]
    }]
  }
}

2. Initialize Directory Structure

mkdir -p ~/.claude/homunculus/{instincts/{personal,inherited},evolved/{agents,skills,commands}}
touch ~/.claude/homunculus/observations.jsonl

3. Run the Observer Agent (Optional)

The observer can run in the background analyzing observations:

# Start background observer
~/.claude/skills/continuous-learning-v2/agents/start-observer.sh

Commands

CommandDescription
/instinct-statusShow all learned instincts with confidence
/evolveCluster related instincts into skills/commands
/instinct-exportExport instincts for sharing
/instinct-import <file>Import instincts from others

Configuration

Edit config.json:

{
  "version": "2.0",
  "observation": {
    "enabled": true,
    "store_path": "~/.claude/homunculus/observations.jsonl",
    "max_file_size_mb": 10,
    "archive_after_days": 7
  },
  "instincts": {
    "personal_path": "~/.claude/homunculus/instincts/personal/",
    "inherited_path": "~/.claude/homunculus/instincts/inherited/",
    "min_confidence": 0.3,
    "auto_approve_threshold": 0.7,
    "confidence_decay_rate": 0.05
  },
  "observer": {
    "enabled": true,
    "model": "haiku",
    "run_interval_minutes": 5,
    "patterns_to_detect": [
      "user_corrections",
      "error_resolutions",
      "repeated_workflows",
      "tool_preferences"
    ]
  },
  "evolution": {
    "cluster_threshold": 3,
    "evolved_path": "~/.claude/homunculus/evolved/"
  }
}

File Structure

~/.claude/homunculus/
├── identity.json           # Your profile, technical level
├── observations.jsonl      # Current session observations
├── observations.archive/   # Processed observations
├── instincts/
│   ├── personal/           # Auto-learned instincts
│   └── inherited/          # Imported from others
└── evolved/
    ├── agents/             # Generated specialist agents
    ├── skills/             # Generated skills
    └── commands/           # Generated commands

Integration with Skill Creator

When you use the Skill Creator GitHub App, it now generates both:

  • Traditional SKILL.md files (for backward compatibility)
  • Instinct collections (for v2 learning system)

Instincts from repo analysis have source: "repo-analysis" and include the source repository URL.

Confidence Scoring

Confidence evolves over time:

ScoreMeaningBehavior
0.3TentativeSuggested but not enforced
0.5ModerateApplied when relevant
0.7StrongAuto-approved for application
0.9Near-certainCore behavior

Confidence increases when:

  • Pattern is repeatedly observed
  • User doesn't correct the suggested behavior
  • Similar instincts from other sources agree

Confidence decreases when:

  • User explicitly corrects the behavior
  • Pattern isn't observed for extended periods
  • Contradicting evidence appears

Why Hooks vs Skills for Observation?

"v1 relied on skills to observe. Skills are probabilistic--they fire ~50-80% of the time based on Claude's judgment."

Hooks fire 100% of the time, deterministically. This means:

  • Every tool call is observed
  • No patterns are missed
  • Learning is comprehensive

Backward Compatibility

v2 is fully compatible with v1:

  • Existing ~/.claude/skills/learned/ skills still work
  • Stop hook still runs (but now also feeds into v2)
  • Gradual migration path: run both in parallel

Privacy

  • Observations stay local on your machine
  • Only instincts (patterns) can be exported
  • No actual code or conversation content is shared
  • You control what gets exported

Related


Instinct-based learning: teaching Claude your patterns, one observation at a time.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.