reflect

# Self-Improving Skills (Reflect)

## Overview

The Reflect system enables **continual learning across sessions**. Instead of starting from zero every conversation, Claude learns from corrections, successful patterns, and user preferences - persisting knowledge in **CLAUDE.md's Skill Memories section**.

```
Session 1: User corrects workflow → Reflect captures learning → saves to CLAUDE.md
Session 2: Claude uses correct approach without being reminded
Session 3+: Knowledge compounds, Claude gets smarter over time
```

---

## Architecture

### Single Source of Truth: CLAUDE.md

All learnings are stored in your project's `CLAUDE.md` file under the `## Skill Memories` section:

```markdown
## Skill Memories

<!-- Auto-captured by SpecWeave reflect. Edit or delete as needed. -->

### Devops
- **2026-01-29**: LSP requires ENABLE_LSP_TOOL=1 env var + boostvolt/claude-code-lsps marketplace

### Frontend
- **2026-01-28**: Use shadcn/ui Button component, not custom styles
- **2026-01-27**: Prefer Vercel over Cloudflare for this Remix project

### General
- **2026-01-29**: Always check for credentials FIRST before using CLI tools
```

**Why CLAUDE.md?**
- Single file to manage (no scattered MEMORY.md files)
- Version controlled with your project
- Easy to edit, review, or delete learnings
- Automatically loaded by Claude Code

---

## What It Learns

### ✅ DOES Remember

| Category | Examples |
|----------|----------|
| **Skill-specific preferences** | "frontend: Use shadcn/ui Button component" |
| **Workflow preferences** | "general: User prefers /sw:auto to run tests first" |
| **Project conventions** | "devops: Use pnpm instead of npm for this monorepo" |
| **Tool configurations** | "testing: Run Vitest with --pool=forks for this project" |

### ❌ Does NOT Remember

| Category | Why Not |
|----------|---------|
| Generic coding advice | "use TypeScript strict mode" - not SpecWeave-specific |
| One-time fixes | Won't recur, clutters memory |
| Implementation details | Unre