plugin-lazylisted

# Plugin Lazy Loader Load disabled plugins on demand without keeping them in every session's context window. Skills-only plugins are read directly from cache and executed inline. Agent-heavy plugins are toggled on and require a session restart. ## Procedure ### Step 1 — Resolve config paths and read plugin registry Determine the Claude config directory: `$env:USERPROFILE\.claude` on Windows, `$HOME/.claude` on Unix/macOS. All paths below are relative to this directory. Read two files to build the plugin catalog: 1. **Installed plugins:** `<config>/plugins/installed_plugins.json` — the `plugins` object has keys like `plugin-name@marketplace-name` with arrays of install records. Each record has `installPath`, `version`, and `scope`. 2. **Enabled plugins:** `<config>/settings.json` — the `enabledPlugins` object has keys like `plugin-name@marketplace-name` with boolean values. If `installed_plugins.json` does not exist or has no entries, report "No plugins installed yet." and stop. A plugin is **disabled** if it appears in `installed_plugins.json` but its `enabledPlugins` entry is either absent or `false`. A plugin is **enabled** if its `enabledPlugins` entry is `true`. ### Step 2 — Detect mode - User said "setup", "lazy setup", or "configure plugins" → go to **Setup Mode** (end of this file). - User asked to **disable** an enabled plugin → go to Step 6. - User named a specific plugin to load → skip to Step 4 (after classifying per Step 3). - Otherwise → show the disab