promote

Topics in the source

• /si:promote — Graduate Learnings to Rules
• Usage
• Workflow
• Step 1: Understand the pattern
• Step 2: Find the pattern in auto-memory
• Step 3: Determine the right target
• Step 4: Distill into a concise rule
• Step 5: Write to target

Moves a proven pattern from Claude's auto-memory into the project's rule system, where it becomes an enforced instruction rather than a background note. Parse the user's description. If vague, ask one clarifying question: "What specific behavior should Claude follow?" "Does this apply to all files or specific paths?" Show the matching entries and confirm they're what the user means. | Pattern scope | Target | Example | |---|---|---| | Applies to entire project | ./CLAUDE.md | "Use pnpm, not npm" | | Applies to specific file types | .claude/rules/ .md | "API handlers need validation" | | Applies to all your projects | /.claude/CLAUDE.md | "Prefer explicit error handling" | If the user didn't specify a target, recommend one based on scope. Transform the learning from auto-memory's note format into CLAUDE.md's instruction format: Before (MEMORY.md — descriptive): The project uses pnpm workspaces. When I tried npm install it failed. The lock file is pnpm-lock.yaml. Must use pnpm install for dependencies. After (CLAUDE.md — prescriptive): Rules for distillation: One line per rule when possible Imperative voice ("Use X", "Always Y", "Never Z") Include the command or example, not just the

This is an excerpt. Refer to the complete source and its current requirements.