Claude Code Memory Curation and Rule Promotion
Audit Claude Code memory, promote verified project rules, and extract recurring fixes into reusable workflows.
Before & after
Same prompt, same agent — the only difference is the skill.
I'd recommend regularly reviewing your project notes to identify patterns that have worked well. You might consider documenting the most important ones in a central place. It could be helpful to extract common solutions you've discovered and potentially turn those into reusable guidelines. You might also want to think about what practices have proven most valuable and consider making them more formal. Would it be useful to look at your notes first to see what stands out? I could help you think through which patterns are most important to capture.
REVIEW MEMORY.MD FOR PATTERNS • Auto-memory shows 23 learnings since last cleanup • Recurring debugging solutions (3): database connection pooling, auth state timing, styled-components SSR • Proven practices (5): prisma schema migrations, Next.js image optimization thresholds, error boundary placement • Environmental gotchas (2): dev API endpoints, local env vs prod state PROMOTE TO CLAUDE.MD Pattern: Use prepare migrations over dev resets → Add rule to AGENTS.md Solution: Auth state sync timing → Extract as shared utility reference Solution: Styled-components import order → Move to .claude/rules/ for consistency EXTRACT REUSABLE SKILL Candidate: The debug workflow for connection pooling errors Recommendation: Promote to skill only if this pattern recurs in 3+ future sessions MEMORY HEALTH Current: 847 lines / 12 KB (healthy) Next cleanup target: 3 more sessions or 1500 lines
About this skill
Claude keeps rediscovering the same fix, but adding more memory has only made the notes harder to trust. This skill sorts useful project knowledge from stale guesses, promotes supported rules to the right scope, and turns recurring fixes into procedures Claude can reuse.
What it does
- Audits MEMORY.md and linked memory notes for duplicates, contradictions, stale assumptions, and unsupported conclusions.
- Distinguishes independent successful uses from repeated copies of the same anecdote before promoting a pattern.
- Routes stable facts to memory, project-wide guidance to CLAUDE.md, narrow rules to .claude/rules/, and recurring procedures to reusable skills.
- Writes rules with an explicit trigger, required behavior, rationale, and supported exceptions.
- Extracts debugging workflows that include diagnosis, verification, and stop conditions instead of preserving only the command that once worked.
- Applies authorized changes with a traceable disposition for each entry and checks that useful context survives cleanup.
What you get
A focused memory audit with evidence-backed decisions and exact replacement text. When editing is authorized and available, you also get updated project files, a concise change summary, and an honest account of what was verified.
Best for
Developers and teams using Claude Code whose project memory has accumulated repeated gotchas, outdated instructions, or debugging notes that deserve a reusable workflow.
SKILL.md preview
---
name: claude-code-memory-curation-and-rule-promotion
description: Curate Claude Code auto-memory by checking provenance, separating stable facts from behavioral rules, and promoting supported knowledge into appropriately scoped project guidance or reusable debugging workflows. Use when the user says "review what you learned", "clean up MEMORY.md", "promote this into a rule", "Claude keeps forgetting this fix", "my memory keeps collecting duplicate notes", "turn this debugging solution into a skill", or "check memory health".
---
# Claude Code Memory Curation and Rule Promotion
… (sign up to view the full skill)More development skills
View all Development skills →Performance Bottleneck Profiling: Node, Python, Go
Classifies a slowdown, gives exact profiler commands, reads the output, and proves the fix with same-conditions p95/p99 numbers.
Feature Scaffolding with Working Tests
Turn a short feature spec into code, runnable tests, and integration wiring that match your existing project.
Feature Flag Rollouts and Kill Switches
Design staged flag rollouts, verify rollback paths, and audit flag debt with explicit defaults, gates, and retirement plans.
Microcontroller Firmware and RTOS Engineering
Build and debug MCU firmware with bounded ISR/RTOS timing, safe DMA ownership, and measured power budgets.