agent-evolution-patterns
How the agent evolution system works — capturing instincts, promoting them to agent overlays, approval workflow, rollback, and the full continuous-learning flywheel pipeline
Best use case
agent-evolution-patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
How the agent evolution system works — capturing instincts, promoting them to agent overlays, approval workflow, rollback, and the full continuous-learning flywheel pipeline
Teams using agent-evolution-patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/agent-evolution-patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How agent-evolution-patterns Compares
| Feature / Agent | agent-evolution-patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
How the agent evolution system works — capturing instincts, promoting them to agent overlays, approval workflow, rollback, and the full continuous-learning flywheel pipeline
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Agent Evolution Patterns
Agent evolution closes the continuous-learning feedback loop: validated instincts flow
from sessions into agent instructions, making agents smarter over time without touching
the versioned agent files in the repo.
## When to Activate
Use this skill when:
- Understanding why an agent keeps making the same mistake across sessions
- Promoting a high-confidence instinct to a specific agent
- Auditing what a reviewer agent has learned (checking its overlay)
- Rolling back a bad instinct that changed agent behaviour for the worse
- Designing a new agent that should benefit from accumulated instincts
## The Problem This Solves
```
Without agent evolution:
Session → /learn-eval → instinct captured → instinct sits unused
Next session: same agent makes the same mistake again
With agent evolution:
Session → /learn-eval → instinct captured → /agent-evolution → overlay written
Next session: agent applies the instinct automatically
```
## System Overview
```
continuous-learning-v2
└── instincts/*.md (confidence scored, domain tagged)
|
| /agent-evolution (user-approved promotion)
v
~/.clarc/agent-instincts/
typescript-reviewer.md ← overlay with learned bullets
tdd-guide.md
code-reviewer.md
|
| session-start.js (automatic injection)
v
Claude session context
└── "When invoking typescript-reviewer, apply these instincts: ..."
```
## Overlay File Format
```markdown
## Learned Instincts (auto-generated — do not edit manually)
<!-- Last updated: 2026-03-10 by /agent-evolution -->
- Always flag direct DOM manipulation in React code (confidence: 0.85, learned: 2026-02-15)
- Check for missing useCallback on event handlers passed to memoized children (confidence: 0.78, learned: 2026-02-20)
```
**Rules:**
- One bullet = one atomic instinct (one trigger, one action)
- Never edit overlay files manually — use `/agent-evolution` to add, `/instinct-outcome` to remove
- Overlay files live in `~/.clarc/agent-instincts/` (user-local, not in the repo)
## Instinct-to-Agent Domain Mapping
| Domain | Target Agents |
|--------|--------------|
| `typescript` | typescript-reviewer, code-reviewer |
| `python` | python-reviewer, code-reviewer |
| `golang` | go-reviewer, code-reviewer |
| `rust` | rust-reviewer, code-reviewer |
| `java` | java-reviewer, code-reviewer |
| `ruby` | ruby-reviewer, code-reviewer |
| `swift` | swift-reviewer, code-reviewer |
| `testing` | tdd-guide, e2e-runner |
| `security` | security-reviewer, devsecops-reviewer |
| `architecture` | architect, planner |
| `documentation` | doc-updater |
| `performance` | performance-analyst |
| `git` | (applied globally via MEMORY.md, not per-agent) |
| _(unknown)_ | code-reviewer (catch-all) |
## Promotion Workflow
### Step 1: Review candidates
```
/agent-evolution
```
Output:
```
Found 3 instincts ready for agent promotion (threshold: 0.75):
1. "Always flag direct DOM manipulation in React code"
Confidence: 0.85 | Domain: typescript | Learned: 2026-02-15
→ Proposed for: typescript-reviewer, code-reviewer
[A]pply / [S]kip / [E]dit before applying
2. "Check useCallback on event handlers passed to memo children"
Confidence: 0.78 | Domain: typescript | Learned: 2026-02-20
→ Proposed for: typescript-reviewer
[A]pply / [S]kip / [E]dit before applying
```
### Step 2: Approve each instinct
- **A** — Apply as-is to all proposed agents
- **S** — Skip; instinct stays in the store for next review
- **E** — Edit the instinct text, then apply the edited version
### Step 3: Verify
```
/agent-instincts typescript-reviewer
```
Output:
```
Overlay for typescript-reviewer:
- Always flag direct DOM manipulation in React code (confidence: 0.85, learned: 2026-02-15)
- Check for missing useCallback on event handlers passed to memoized children (confidence: 0.78, learned: 2026-02-20)
```
## Session Injection
At session start, `session-start.js` reads all overlay files and outputs them to Claude:
```
--- Agent Learned Instincts ---
When invoking these agents, apply the following learned instincts:
### typescript-reviewer
## Learned Instincts (auto-generated — do not edit manually)
<!-- Last updated: 2026-03-10 by /agent-evolution -->
- Always flag direct DOM manipulation in React code (confidence: 0.85, learned: 2026-02-15)
---
```
Log: `[SessionStart] Agent instinct overlays loaded: typescript-reviewer (2 instincts), tdd-guide (1 instinct)`
## Rollback Protocol
If an instinct makes an agent worse:
```
1. /instinct-outcome <id> bad --reason "Made typescript-reviewer too aggressive"
→ Confidence drops below 0.75 promotion threshold
2. /agent-evolution
→ Low-confidence instinct appears as removal candidate
3. User confirms removal
→ Instinct removed from overlay file
```
Or remove directly without going through the promotion flow:
```bash
node scripts/agent-evolution.js remove typescript-reviewer "Always flag direct DOM"
```
## Threshold Tuning
| Threshold | Effect |
|-----------|--------|
| 0.9 | Only near-certain patterns (very conservative) |
| 0.75 | Default — good balance |
| 0.6 | More candidates, higher noise risk |
| 0.5 | Exploratory — review carefully before applying |
## Anti-Patterns
- **Editing overlay files manually** — use `/agent-evolution` so metadata is tracked
- **Promoting instincts without reviewing them** — always read what you apply (`/agent-instincts`)
- **Applying a `git` domain instinct to agents** — `git` instincts apply globally via MEMORY.md
- **Forgetting to roll back** — if an agent behaves unexpectedly, check its overlay first
## Underlying Script
```bash
node scripts/agent-evolution.js list [--threshold 0.75]
node scripts/agent-evolution.js apply <agent> "<text>" --confidence 0.80 --learned YYYY-MM-DD
node scripts/agent-evolution.js show [<agent>]
node scripts/agent-evolution.js remove <agent> "<prefix>"
```
## Related Commands
- `/agent-evolution` — interactive promotion workflow
- `/agent-instincts <name>` — show current overlay content
- `/instinct-outcome <id> bad` — roll back a promoted instinct
- `/evolve` — cluster instincts into new skills/commands/agents (different from agent overlays)
- `/instinct-status` — view all captured instincts with confidence scoresRelated Skills
zero-trust-patterns
Zero-Trust security patterns — mTLS between microservices (Istio/SPIFFE), SPIRE workload identity, OPA/Envoy authorization, NetworkPolicy default-deny-all, short-lived credentials, service mesh security, and Kubernetes RBAC hardening.
webrtc-patterns
WebRTC patterns — peer connection setup, ICE/STUN/TURN configuration, signaling server design, SFU vs mesh topology, screen sharing, media track management, and reconnect/ICE restart handling.
webhook-patterns
Webhook patterns for receiving, verifying (HMAC), and idempotently processing third-party events. Covers Stripe, GitHub, and generic webhook patterns, delivery guarantees, retry handling, and testing.
wasm-patterns
WebAssembly patterns: wasm-pack, wasm-bindgen (JS↔Wasm interop), WASI, Component Model, wasm-opt, Rust-to-WASM compilation, JS integration (web workers, streaming instantiation), and production deployment (CDN, Content-Type headers).
ux-micro-patterns
UX micro-patterns for every product state: Empty States, Loading States (skeleton screens, spinners, optimistic UI), Error States, Success States, Confirmation Dialogs, Onboarding Flows, and Progressive Disclosure. These patterns apply to every feature — done wrong, they're the biggest source of user confusion.
typescript-patterns
TypeScript patterns — type system best practices, strict mode, utility types, generics, discriminated unions, error handling with Result types, and module organization. Core patterns for production TypeScript.
typescript-patterns-advanced
Advanced TypeScript — mapped types, template literal types, conditional types, infer, type guards, decorators, async patterns, testing with Vitest/Jest, and performance. Extends typescript-patterns.
typescript-monorepo-patterns
TypeScript monorepo patterns with Turborepo + pnpm workspaces. Covers package structure, shared configs, task pipeline caching, build orchestration, and publishing strategy.
terraform-patterns
Infrastructure as Code with Terraform — project structure, remote state, modules, workspace strategy, AWS/GCP patterns, CI/CD integration, and security hardening. The standard for managing production infrastructure.
swiftui-patterns
SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
swift-patterns
Core Swift patterns — value vs reference types, protocols, generics, optionals, Result, error handling, Codable, and module organization. Foundation for all Swift development.
swift-patterns-advanced
Advanced Swift patterns — property wrappers, result builders, Combine basics, opaque & existential types, macro system, advanced generics, and performance optimization. Extends swift-patterns.