blueprint-promote
Move generated artifact to custom layer to preserve manual edits. Use when promoting a generated rule, preserving .claude/rules/ changes, or stopping sync warnings.
How do I install this agent skill?
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-promoteIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is designed to manage and preserve modifications to local project rules. It performs routine file operations, such as checking for file existence and updating a local manifest file. No security risks or malicious behaviors were identified.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerwarn
1/1 file flagged
What does this agent skill do?
Copy a generated rule to the custom rules layer for preservation.
When to Use This Skill
| Use this skill when... | Use blueprint-sync instead when... |
|---|---|
| You want to preserve manual edits to a single generated rule | You want to scan all generated content for drift first |
| You want to stop sync warnings on a modified auto-generated file | You want regenerate/keep options across many files at once |
| You say "promote from proposed to custom" or "acknowledge modifications" | Use blueprint-generate-rules instead to regenerate from PRDs |
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
-
Parse argument:
- Extract
namefrom arguments - If no name provided, list available generated rules and ask user to choose
- Extract
-
Locate the rule:
# Check if it's a generated rule test -f .claude/rules/{name}.mdIf not found:
Rule '{name}' not found in generated content. Available rules: - architecture-patterns - testing-strategies - implementation-guides - quality-standards -
Check if already acknowledged:
- Read manifest for
custom_overrides.rules - If already in list, report "Already acknowledged"
- Read manifest for
-
Confirm acknowledgment:
question: "Acknowledge modifications to {name}?" description: | This will: 1. Mark {name} as user-modified in manifest 2. Prevent overwrite warnings during sync 3. Keep the rule in .claude/rules/ options: - label: "Yes, acknowledge" description: "Mark as user-modified and preserve changes" - label: "No, keep as generated" description: "Leave as regeneratable (may show warnings)" -
Update manifest:
- Add to
custom_overrides.rules - Update
updated_attimestamp
Example manifest update:
{ "generated": { "rules": { // testing-strategies still listed } }, "custom_overrides": { "rules": ["testing-strategies"] // added } } - Add to
-
Report:
Rule modifications acknowledged! testing-strategies.md: - Location: .claude/rules/testing-strategies.md - Status: User-modified (acknowledged) This rule will now: - Not show modification warnings in /blueprint:sync - Still be tracked in manifest - Be your responsibility to maintain To edit: .claude/rules/testing-strategies.md
Architecture note (v3.0):
Generated content now goes directly to .claude/rules/ instead of a separate generated layer.
The manifest tracks which rules are user-modified vs auto-generated.
Tips:
- Acknowledge rules you want to customize
- Unacknowledged modified rules will show warnings in /blueprint:sync
- You can regenerate by removing from custom_overrides and running
/blueprint:generate-rules
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/laurigates/claude-plugins/blueprint-promote">View blueprint-promote on skillZs</a>