plugin-lifecycle
plugin-lifecycle Skill
Purpose: Manage the complete lifecycle of plugins from installation to removal with proper state tracking and safety features.
Overview
This skill handles all plugin lifecycle operations on macOS:
- Installation (Mode 1): Copy Release binaries to system folders (
~/Library/Audio/Plug-Ins/) - Uninstallation (Mode 2): Clean removal from system folders (preserves source code)
- Reset to Ideation (Mode 3): Remove implementation, keep idea/mockups (surgical rollback)
- Destroy (Mode 4): Complete removal with backup (nuclear option)
All operations include proper permissions, cache clearing, state tracking, and safety features (confirmations, backups).
Mode Dispatcher
More from glittercowboy/plugin-freedom-system
ui-mockup
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]'.
25aesthetic-dreaming
Create aesthetic templates without first creating a plugin - capture visual design concepts through adaptive questioning. Use when you want to build a library of visual systems before plugin implementation.
17plugin-planning
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.
15plugin-packaging
Create branded PKG installers for plugin distribution. Use when user requests to package a plugin, create installer, share plugin with others, or mentions distributing/sending plugin to someone. Invoked by /package command or natural language like 'create installer for TapeAge' or 'package GainKnob'.
15plugin-testing
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.
15plugin-workflow
Orchestrates JUCE plugin implementation through stages 1-3 (Foundation, DSP, GUI) using subagent delegation with automatic validation after each stage. Use when implementing plugins after planning completes, or when resuming with /continue command. Invoked by /implement command.
15