Promote Proven Memory to Project Rules
Turn proven Claude Code memory into scoped project rules, check conflicts, and retire only the captured source entries.
Before & after
Same prompt, same agent — the only difference is the skill.
The promote concept lets you capture a working pattern from your session notes and move it into permanent configuration so it becomes a standard practice. This would involve documenting the pattern and adding it to your codebase rules. Over time, this helps ensure consistent behavior across your team without needing to re-explain the same guideline repeatedly. I could help you draft the documentation.
PROMOTION WORKFLOW: Session pattern to permanent rule CURRENT STATE: Pattern documented in auto-memory at .claude/projects///-/memory/MEMORY.md (this session only, expires next session). STEP 1 - EXTRACT: Copy the exact pattern from MEMORY.md: "Before pushing any branch, always run local tests first. Never force-push to main/master. Rebase after merging if release branch has moved." STEP 2 - PROMOTE TO CLAUDE.md: Add new section CLAUDE.md (checked into repo, survives all sessions, all team members see it). STEP 3 - PROMOTE TO .claude/rules/: Create file .claude/rules/merge-before-deploy.md (enforces on every AI interaction, gated by hook system). Git-committed so it blocks everyone, not just you. OUTPUT ARTIFACT: Updated CLAUDE.md + new rule file + git commit message ready to push. NOTE: Once promoted, all future sessions see this rule automatically. Team members who clone the repo get it too. If you need to refine the rule, edit CLAUDE.md and re-commit; rules don't auto-update mid-session (next session picks up changes). WHY: MEMORY.md is transient (session-scoped). CLAUDE.md is codebase-scoped (all sessions, team visibility). Rules/ are enforcement-scoped (system hooks running on every Claude action). Promotion sequence ensures escalating visibility.
About this skill
Claude keeps repeating a correction even though you already saved it in memory. Turn that proven lesson into a concise project instruction, put it where it applies, and retire the original note only after verifying the replacement.
What it does
- Separates durable conventions from temporary environment facts, one-off fixes, and unsupported conclusions.
- Chooses between project-wide CLAUDE.md instructions and scoped .claude/rules/ files.
- Converts discovery notes into actionable rules with explicit triggers, required behavior, and exceptions.
- Checks existing instructions for duplicates, contradictions, and accidental scope expansion.
- Verifies the saved rule before removing or marking only the matching memory entry.
- Supplies a proposed patch when file access is unavailable, without claiming the change was applied.
What you get
A verified project-rule edit with a short explanation of its evidence, scope, and source-memory disposition. When working from pasted text, you get the exact proposed changes and the checks still needed.
Best for
Claude Code users and teams who repeatedly correct the same behavior, maintain project instructions, or need to move stable conventions out of auto-memory.
SKILL.md preview
---
name: promote-proven-memory-to-project-rules
description: >-
Promote a proven Claude Code auto-memory entry into a durable CLAUDE.md or scoped .claude/rules/ project rule. The workflow checks the evidence, picks the narrowest workable scope, reconciles existing rules and legacy exceptions, and verifies the destination before retiring the source. Use when the user says "make this learned behavior permanent", "promote this memory", "promote our memory to rules", "move this into CLAUDE.md", "turn this into an official project rule", "my Claude keeps forgetting this", or "/si:promote".
---
# Promote Proven Memory to Project Rules
… (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.