blueprint-promote

Copy a generated rule to the custom rules layer for preservation.

When to Use This Skill

Steps

Purpose:

• Copy generated content from .claude/rules/ to preserve modifications
• Mark as acknowledged in manifest to prevent overwrite warnings
• Generated rules in .claude/rules/ are the standard location (v3.0)

Usage: /blueprint:promote [name]

Examples:

• /blueprint:promote testing-strategies - Acknowledge a rule's modifications

1. Parse argument:

   • Extract name from arguments
   • If no name provided, list available generated rules and ask user to choose

2. Locate the rule:

   Resolve the rules directory from the manifest — never hardcode .claude/rules/ (issues #1043, #1675, #2331):

   RULES_DIR=$(jq -r '.structure.generated_rules_path // ".claude/rules/"' docs/blueprint/manifest.json)
   RULES_DIR="${RULES_DIR%/}"
   

   generated.rules keys are bare filenames including the .md extension, so normalise a bare {name} argument to {name}.md once and resolve it as "$RULES_DIR/{key}" — do not append .md to a manifest key:

   KEY="{name}"; case "$KEY" in *.md) ;; *) KEY="$KEY.md" ;; esac
   test -f "$RULES_DIR/$KEY"
   

   If not found:

   Rule '{name}' not found in generated content.
   
   Available rules:
   - architecture-patterns
   - testing-strategies
   - implementation-guides
   - quality-standards
   

3. Check if already acknowledged:

   • Read manifest for custom_overrides.rules
   • If already in list, report "Already acknowledged"