// Manage complete plugin lifecycle - install, uninstall, reset, destroy. Use when user runs /install-plugin, /uninstall, /reset-to-ideation, /destroy, /clean commands, or says 'install [Name]', 'remove [Name]', 'uninstall [Name]', 'delete [Name]'.
| name | plugin-lifecycle |
| description | Manage complete plugin lifecycle - install, uninstall, reset, destroy. Use when user runs /install-plugin, /uninstall, /reset-to-ideation, /destroy, /clean commands, or says 'install [Name]', 'remove [Name]', 'uninstall [Name]', 'delete [Name]'. |
| allowed-tools | ["Bash","Read","Edit","Write"] |
| preconditions | ["Varies by mode (see mode-specific preconditions)"] |
Purpose: Manage the complete lifecycle of plugins from installation to removal with proper state tracking and safety features.
This skill handles all plugin lifecycle operations on macOS:
~/Library/Audio/Plug-Ins/)All operations include proper permissions, cache clearing, state tracking, and safety features (confirmations, backups).
This skill operates in different modes based on the invoking command:
| Mode | Operation | Command | Purpose |
|---|---|---|---|
| 1 | Installation | /install-plugin | Deploy to system folders |
| 2 | Uninstallation | /uninstall | Remove binaries, keep source |
| 3 | Reset to Ideation | /reset-to-ideation | Remove implementation, keep idea/mockups |
| 4 | Destroy | /destroy | Complete removal with backup |
| Menu | Interactive | /clean | Present menu, user chooses mode |
Invocation Pattern:
When user runs /install-plugin [Name], the command expands to a prompt that invokes THIS skill.
Determine mode by examining command (see references/invocation-protocol.md), then load ONLY the relevant reference file:
references/installation-process.md ONLYreferences/uninstallation-process.md ONLYreferences/mode-3-reset.md ONLYreferences/mode-4-destroy.md ONLYIMPORTANT: Do NOT load other mode reference files. Load only the reference file for the active mode to optimize context window usage.
Installation targets (macOS):
~/Library/Audio/Plug-Ins/VST3/, ~/Library/Audio/Plug-Ins/Components/~/Library/Application Support/Avid/Audio/Plug-Ins/ (future)Copy this checklist to track installation progress:
Installation Progress:
- [ ] Step 1: Build verification (BLOCKING)
- [ ] Step 2: Product name extraction
- [ ] Step 3: Old version removal
- [ ] Step 4: Copy to system folders (BLOCKING)
- [ ] Step 5: Permissions verification (BLOCKING)
- [ ] Step 6: Cache clearing
- [ ] Step 7: Verification (BLOCKING)
- [ ] Step 8: PLUGINS.md update (BLOCKING)
Execute these steps in order:
Build Verification (BLOCKING) - Check Release binaries exist, offer to build if missing
references/installation-process.md Step 1Product Name Extraction - Extract PRODUCT_NAME from CMakeLists.txt
references/installation-process.md Step 2Old Version Removal - Remove existing installations to prevent conflicts
references/installation-process.md Step 3Copy to System Folders (BLOCKING) - Install VST3 and AU to macOS plugin directories
references/installation-process.md Step 4Permissions Verification (BLOCKING) - Set 755 permissions for DAW access
references/installation-process.md Step 5Cache Clearing - Clear Ableton Live and Logic Pro caches
references/cache-management.mdVerification (BLOCKING) - Confirm installation with file checks and size validation
references/installation-process.md Step 7PLUGINS.md Update (BLOCKING) - Record installation status and locations
references/installation-process.md Step 8Note: Steps marked BLOCKING must succeed before proceeding.
Feedback Loop: If Step 7 (Verification) fails:
references/error-handling.mdIf verification succeeds, proceed to decision menu.
See references/installation-process.md for complete implementation.
See references/cache-management.md for cache clearing procedures (invoked during installation and uninstallation).
See references/uninstallation-process.md for complete uninstallation process (locate, confirm, remove, clear caches, update PLUGINS.md).
Surgical rollback - removes implementation, preserves idea/mockups. Use case: Implementation failed but concept is solid. See references/mode-3-reset.md for complete process.
Complete removal with backup. Use case: Abandoned experiment, never using again. Requires exact plugin name confirmation (safety gate). See references/mode-4-destroy.md for complete process.
When invoked via /clean [PluginName], present interactive menu:
Plugin cleanup options for [PluginName]:
1. Uninstall - Remove binaries from system folders (keep source code)
2. Reset to ideation - Remove implementation, keep idea/mockups
3. Destroy - Complete removal with backup (IRREVERSIBLE except via backup)
4. Cancel
Choose (1-4): _
Menu logic:
After successful operations, check workflow mode before presenting decision menu:
Check workflow mode:
.claude/preferences.json for workflow.mode settingManual mode (default):
Express mode:
Note: plugin-lifecycle operations are terminal (don't chain to next stage), so express mode behavior is: complete operation → skip menu → end workflow.
Invoked by:
/install-plugin [PluginName] → Mode 1 (Installation)/uninstall [PluginName] → Mode 2 (Uninstallation)/reset-to-ideation [PluginName] → Mode 3 (Reset)/destroy [PluginName] → Mode 4 (Destroy)/clean [PluginName] → Interactive menuplugin-workflow skill → After Stage 3 (auto-installs)plugin-improve skill → After successful changes (offers reinstallation)Invokes:
Invocation patterns: See references/invocation-protocol.md for mode detection and routing.
Updates:
PLUGINS.md → Table row: status, version, last updatedplugins/[Name]/NOTES.md → Status metadata, timeline entries, installation detailsCreates:
~/Library/Audio/Plug-Ins/VST3/[Product].vst3~/Library/Audio/Plug-Ins/Components/[Product].componentBlocks:
Installation is successful when: VST3/AU installed with 755 permissions, caches cleared, PLUGINS.md updated, user informed of next steps.
Orchestrator for WebView UI mockup workflow - delegates design iteration to ui-design-agent and implementation scaffolding to ui-finalization-agent. Use when user mentions UI design, mockup, WebView interface, or requests 'design UI for [plugin]'.
Multi-agent parallel investigation for complex JUCE problems. Use when troubleshooting fails after Level 3, problems require novel research, or user requests /research command.
Orchestrates Stage 0 research and planning for JUCE plugins - creates architecture.md and plan.md contracts through subagent delegation. Use when creative brief exists and plugin needs DSP architecture specification, complexity assessment, or implementation planning. Invoke via /plan command, natural language (plan architecture, research DSP), or as first implementation step.
Fix bugs, add features to completed plugins. Includes versioning, backups, regression testing, changelog automation. Auto-detects deep-research handoffs to preserve investigation context. Trigger terms - improve, fix, add feature, modify plugin, version bump, rollback
Load plugin context from handoff files to resume work. Invoked by /continue command, 'resume [PluginName]', 'continue working on [PluginName]', 'pick up where I left off with [PluginName]', or 'show me where [PluginName] is at'. Locates handoff across 2 locations, parses state, presents summary, and routes to appropriate continuation skill.
Validates audio plugins through automated tests, pluginval, or manual DAW testing. Use for MANUAL testing via /test command. Note - Automatic validation now built into workflow (validation-agent runs after each stage). This skill is for manual testing only, after bug fixes, or when user mentions test, validate, validation, pluginval, stability, automated tests, run tests, check plugin, or quality assurance.