Learn Rule

[LEARN] Category: One-line rule
Mistake: What went wrong
Correction: How it was fixed

[LEARN] Category: One-line rule

User: You edited the wrong file

Claude: I edited src/utils.ts when you meant src/lib/utils.ts.
Let me fix that.

[Fixes the mistake]

To prevent this in the future:

[LEARN] Navigation: Confirm full path before editing files with common names.
Mistake: Edited src/utils.ts assuming it was the right file
Correction: Asked for clarification: "There are 2 files named utils.ts. Which one?"

Should I add this to LEARNED? (y/n)

User: y

Claude: ✓ Added to LEARNED section. I'll confirm file paths before editing in future sessions.

User: You left console.log in the code

Claude: You're right, I left console.log('user:', user) in src/api/auth.ts:42.
Let me remove it.

[Removes console.log]

To prevent this:

[LEARN] Quality: Remove console.log statements before committing code.
Mistake: Left debug console.log in production code
Correction: Removed before commit, will scan for console.log in future edits

Add to LEARNED? (y/n)

User: yes

Claude: ✓ Learned. I'll scan for debug statements before wrapping up sessions.

User: Don't put business logic in React components

Claude: You're right. I added the user validation logic directly in UserProfile.tsx
when it should be in a separate service.

Let me extract it to src/services/userValidation.ts.

[Refactors code]

[LEARN] Architecture: Keep business logic in services, not React components.
Mistake: Added validation logic directly in UserProfile component
Correction: Extracted to src/services/userValidation.ts, component just calls service

Add this pattern? (y/n)

User: y

Claude: ✓ Learned. Business logic stays in services, components handle UI only.

User: These tests are flaky because you're calling the real API

Claude: You're correct. The auth tests in tests/api/auth.test.ts are calling
the live authentication endpoint, causing intermittent failures.

Let me add mocks:

[Adds API mocks]

[LEARN] Testing: Mock external APIs in tests to prevent flakiness.
Mistake: Called real OAuth API in tests, causing random failures
Correction: Added jest.mock() for auth provider, tests now deterministic

Capture this lesson? (y/n)

User: yes

Claude: ✓ Captured. I'll mock external dependencies in future tests.

.claude/
├── CLAUDE.md          # Core instructions
└── LEARNED.md         # All learning rules

# CLAUDE.md

## Instructions
[Core instructions]

## LEARNED
[LEARN] Navigation: Confirm full path before editing files with common names.
[LEARN] Testing: Mock external APIs in auth tests to prevent flakiness.
[LEARN] Quality: Remove console.log statements before committing code.

~/.pro-workflow/
└── data.db    # SQLite with FTS5 full-text search

## Self-Correction Protocol

When the user corrects me or I make a mistake:
1. Acknowledge specifically what went wrong
2. Propose a concise rule: `[LEARN] Category: One-line rule`
3. Wait for approval before adding to LEARNED section

### LEARNED
<!-- Auto-populated through corrections -->

// settings.local.json (Claude Code)
{
  "learnings": {
    "storage": "file",  // or "database"
    "file": ".claude/LEARNED.md"
  }
}

# Search by keyword
/search testing
/search "file paths"

# List all learnings
/list

# List by category
/list --category Navigation

# Show application frequency
/insights

Learnings matching 'testing' (3 results):

1. [Testing] Mock external APIs in auth tests to prevent flakiness
   Applied: 8 times | Last: 2026-03-05
   
2. [Testing] Run tests before commit, not after
   Applied: 15 times | Last: 2026-03-08
   
3. [Testing] Use --changed flag to test only affected files
   Applied: 3 times | Last: 2026-03-01