correction-learning
Correction Learning Framework
When This Activates
This skill activates when you detect the user is correcting your output:
- Explicit disagreement
- Preference expressions
- Style corrections
- Terminology corrections
Correction Detection Patterns
Explicit Corrections:
- "no, I meant..."
- "that's wrong/incorrect/not right"
- "actually, I want/need/meant..."
- "I said X not Y"
- "no, not X"
Imperative Corrections:
- "no, use X"
- "use X not Y"
- "use X instead"
- "should be X not Y"
- "it's X not Y"
Action Corrections:
- "don't do/use/add/make X"
- "remove that/this"
- "undo/revert"
- "go back to"
- "change it back to"
Preference Expressions:
- "prefer X over Y"
- "always use X"
- "never use X"
- "stop using X"
Response Protocol
When you detect a correction:
1. Acknowledge Without Defensiveness
"Got it - using [correct approach] instead."
2. Extract the Learning
Identify:
- What was wrong: Your original approach
- What is correct: User's preferred approach
- Category: naming, syntax, patterns, style, terminology
3. Apply Immediately
Make the change in the current response.
4. Record for Future
The system auto-records corrections to ~/.claude-dash/learning/corrections.json
Common Correction Categories
Naming Preferences
User: "No, use camelCase not snake_case"
Learn: {category: "naming", prefers: "camelCase", over: "snake_case"}
Syntax Preferences
User: "Always use arrow functions"
Learn: {category: "syntax", key: "function_style", prefers: "arrow"}
Framework Patterns
User: "Use useQuery not fetch for API calls"
Learn: {category: "patterns", prefers: "useQuery", over: "fetch"}
Style Preferences
User: "Single quotes, not double"
Learn: {category: "style", key: "quotes", prefers: "single"}
EWC Protection (Don't Flip-Flop)
The system uses Elastic Weight Consolidation to prevent:
- A few corrections overriding established patterns
- Flip-flopping between preferences
How it works:
- New preference: requires 60% ratio + 3 observations
- Reinforcing existing: requires 50% ratio + 2 observations
- Changing established: requires 80% ratio + 8 observations
Self-Awareness Phrases
When you notice patterns:
- "I notice I've been corrected on [X] before - using [Y] instead"
- "Based on your previous feedback about [X], I'm using [Y]"
- "Following your preference for [X]..."
What Gets Recorded
{
"timestamp": "...",
"user_message": "no, use useState not useRef",
"correct": "useState",
"wrong": "useRef",
"topic": "react-hooks",
"project_id": "gyst"
}
This feeds into the ReasoningBank for future context retrieval.
More from jamelna-apps/claude-dash
cost-tracking
When user mentions "spending", "usage", "tokens", "API cost", "budget", "expensive", or wants to understand Claude API costs. Provides cost awareness and optimization guidance.
11page-cro
When the user mentions "conversion", "CRO", "landing page", "not converting", "bounce rate", "optimize page", or asks about improving page performance.
7session-handoff
When user says "continue", "pick up where we left off", "last time", "previous session", "what were we doing", or wants explicit session continuity. Provides structured context handoff between sessions.
4error-diagnosis
When user encounters "error", "exception", "failed", "stack trace", "crashed", or needs error categorization. Provides structured root cause analysis and prevention strategies.
4code-review
When the user mentions "review", "PR", "pull request", "code review", "check my code", "feedback on", or asks for code quality assessment.
3smart-routing
When deciding which Claude model (Opus/Sonnet/Haiku) to use, or when "route", "which model", "complex task", "multi-file", "architectural", or "deep debugging" is mentioned. Guides quality-first model selection.
3