sync-claude-code-plugins

**User request**: $ARGUMENTS Sync prompt-engineering plugin components from a local sibling clone of `claude-code-plugins` into this repo's `.claude/` directory. The plugin OWNS only the files it ships — other content in `.claude/agents/` and `.claude/skills/` (manifest-dev sync, KB skills, anything else) must be left alone. ## Source & Target | Role | Path | |------|------| | Source repo | `../claude-code-plugins` (relative to this repo's root) | | Source components | `<source_repo>/claude-plugins/prompt-engineering/` | | Target | `.claude/` in this repo | | Tracking file | `.claude/.claude-code-plugins-sync.json` | ## Sync scope | Component | Source dir | Target dir | |-----------|-----------|------------| | Agents | `agents/` | `.claude/agents/` | | Skills | `skills/` | `.claude/skills/` | prompt-engineering ships no hooks today. ## Territory model **Deletion invariant**: only items in `tracked` (the previously-synced set) are eligible for removal when they disappear upstream. Items never in `tracked` are invisible — that's how project-local content stays safe. The tracked set lives in `.claude/.claude-code-plugins-sync.json`: ```json { "version": 1, "last_synced_at": "ISO-8601 timestamp", "agents": ["prompt-reviewer.md", "..."], "skills": ["prompt-engineering", "..."] } ``` First run (file missing): `tracked` is empty, no deletions happen, file is written at end. ## Sync algorithm Pre-flight: abort if `<source_repo>/claude-plugins/prompt-engineering/`...