Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By primeline-ai
Evolve your Claude Code sessions by learning from corrections, managing context across sessions, and automating workflows with custom commands, hooks, and agents for debugging, code review, planning, and model switching.
npx claudepluginhub primeline-ai/evolving-liteShow context window usage, active tier, and system stats
Create a new custom slash command
Create a new custom automation hook
Systematic debugging with hypotheses and evidence gathering
Show what the system learned and changed recently
Deep health analysis of Evolving Lite - sentinel history, hook performance, recommendations
Checks Evolving Lite data consistency - memory structure, experience index, config validity
Fixes issues found by integrity-checker - repairs JSON, rebuilds indices, fixes permissions
Reviews and refines plans - checks for anti-patterns, missing kill criteria, vague gates
Generates session handoff documents with project state and next steps
Explains how Evolving Lite works when the user asks about the system, its features, or how to use it. Triggers on questions like "how does this work", "what is evolving lite", "what hooks are running", "explain the system".
Auto-activating session startup - reads memory, orients Claude, announces status. Triggers on session start or when user says "continue", "weiter", "resume".
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Analyze Claude Code agent session transcripts to identify inefficiencies, anti-patterns, repeated mistakes, missing tooling opportunities, and user frustration signals for continuous improvement
Automatic context engineering — observes your coding sessions and generates rules, suggestions, skills, and hooks so Claude gets smarter on your codebase over time
(Alpha) Persistent memory, architectural decisions, and safety guardrails for Claude Code. Your agent starts every session with full project context — stack, decisions, patterns, safety rules, and a handoff from the previous session.
Self-improving Claude Code plugin — learns from corrections across sessions via reflexio
Continuous learning hooks for gladiator MCP (observe patterns, reflect on them)
Autonomous, personalized research loops for Claude Code. Set a topic, walk away, come back to a quality-gated report adapted to your projects.
A complete session management system for Claude Code. Memory persistence, session handoffs, context awareness, and delegation basics - extracted from a 650-node production AI system.
5 production-grade workflow skills for Claude Code. Debugging, delegation, planning, code review, and configuration architecture.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.

Claude Code that learns from you. Install once. Work normally. The system remembers what worked, learns from your corrections, and gets better every session — without you lifting a finger.
"I corrected Claude about checking tsconfig strict mode first. A week later, different project, similar type error — Claude checked strict mode before I said anything. That's when I stopped thinking of it as a plugin."
2 min demo: Claude recalls past decisions, learns from a correction, and applies it automatically — no prompt needed.
Evolving Lite prevents drift in real-time. Claude Health audits your full config on demand. Together they close the loop.
| Evolving Lite | Claude Health | |
|---|---|---|
| When | Every session (automatic) | On demand (/health) |
| How | Hooks, pulse checks, correction pipeline | 6-layer config audit with parallel diagnostics |
| Catches | Drift as it happens | Existing gaps and misconfigurations |
Most Claude Code tools add features. Evolving Lite adds feedback loops.
It learns from corrections. Say "No, check tsconfig first" once. The system detects the correction, stores it, and recalls it automatically when a similar situation comes up — across sessions, across projects.
It activates progressively. Session 1: safety net only. Session 3: learning kicks in. Session 10: deep memory. You're never overwhelmed, and each tier earns trust before the next one activates.
It heals itself. Every hook writes a sentinel file proving it ran. Run the health-monitor agent to check all sentinels — silent failures don't stay silent.
It gets leaner, not fatter. Old experiences decay. Stale sessions get archived. The system prunes itself so it stays fast at month 6 the same way it was at day 1.
# 1. Clone
git clone https://github.com/primeline-ai/evolving-lite ~/.claude-plugins/evolving-lite
# 2. Run setup (configures hook paths for your machine)
cd ~/.claude-plugins/evolving-lite && bash setup.sh
# 3. Register (add to ~/.claude/settings.json under "pluginDirectories")
{
"pluginDirectories": [
"~/.claude-plugins/evolving-lite"
]
}
# 3. Start Claude Code
claude
On first start:
Evolving Lite v1.0 | Session 1 | Tier 1 (Safety) | 20 experiences loaded
The system learns from your corrections automatically.
Day 1 — You install it and work normally. Context warnings appear at 70%. Dangerous bash commands get blocked. 20 pre-warmed experiences provide Claude Code best practices from day one. You barely notice it's there.
Week 1 (Session 3+) — The learning tier activates. When you correct Claude, the system captures it. Exploration tasks start routing to cheaper models automatically. Each session ends with an auto-generated summary of what happened and what's next.
Month 1 (Session 10+) — Deep memory kicks in. While Claude thinks, the system searches your stored experiences and injects relevant solutions before you ask. Old data gets archived automatically. Knowledge survives context compaction. It feels less like a tool and more like a colleague who remembers everything.
The system runs on 4 loops that operate in the background. You don't invoke them — they fire on Claude Code events (session start, tool use, prompt submit, session end).
LEARN You correct Claude → correction stored → recalled automatically next time
CONTEXT Budget hits 70% → warning → at 93% knowledge is saved → session continues seamlessly
HEAL Session starts → sentinel check → broken hook? → you see a warning immediately
EVOLVE Usage tracked → stale data archived → routes refined → system stays lean
| Loop | Hooks | What changes |
|---|---|---|
| Learn | correction-detector, thinking-recall | Claude stops repeating your corrections |
| Context | context-warning, precompact-extract | You never lose knowledge to context compaction |
| Heal | health-sentinel, health-monitor agent | Silent hook failures get caught via sentinel checks |
| Evolve | usage-tracker, auto-archival | The system prunes itself and stays fast |