promote

Promote proven patterns from MEMORY.md into enforceable CLAUDE.md or .claude/rules.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/ano4l/SiteRent --skill promote-ano4l
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/ano4l/SiteRent/tree/main/skills/self-improving-agent/skills/promote
Command: npx skills add https://github.com/ano4l/SiteRent --skill promote-ano4l

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that repeated learnings and patterns discovered during development are transformed into permanent, enforceable instructions within the codebase, reducing drift and miscommunication.

Core Features & Use Cases

  • Promotes a proven pattern from MEMORY.md to CLAUDE.md or .claude/rules/ for lasting enforcement.
  • Supports global, scoped, and path-based rule promotion to fit project structure.
  • Keeps MEMORY.md clean by guiding post-promotion cleanup and verification steps.

Quick Start

Provide the pattern description and target file, then run /si:promote to create the rule.

Frequently Asked Questions about promote

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn Claude project memories into enforceable rules in CLAUDE.md?

To turn Claude project memories into enforceable rules, you promote proven patterns from MEMORY.md into CLAUDE.md or .claude/rules. This distills repeated learnings into concise, permanent instructions within the codebase to reduce drift.

What is the best way to automate promoting development patterns to project rules?

The best way to automate promoting development patterns to project rules is using a memory-to-rule promotion process. It extracts validated patterns from auto-memory and writes them to global or topic-specific rule files for permanent enforcement.

Can I scope Claude rules to specific file paths when promoting from MEMORY.md?

Yes, you can scope Claude rules to specific file paths when promoting from MEMORY.md. The promotion process supports global CLAUDE.md instructions, topic-specific .claude/rules, and path-based scoping to fit your project structure.

How does cleaning MEMORY.md work after promoting entries to .claude/rules?

Cleaning MEMORY.md after promoting entries to .claude/rules involves guided post-promotion cleanup and verification steps. This ensures the memory file remains uncluttered once a learning is successfully distilled and written as a permanent rule.

Why should I promote auto-memory learnings into permanent project rules?

You should promote auto-memory learnings into permanent project rules to ensure repeated development patterns are permanently enforced. Transforming these learnings into strict instructions reduces team miscommunication and prevents codebase drift over time.

Do I need auto-memory entries in MEMORY.md before promoting them to rules?

Yes, you need auto-memory entries in MEMORY.md before promoting them to rules. The promotion process requires proven patterns and learnings to already exist in the memory file so they can be distilled into concise instructions.