plugin-builder

# Plugin Builder

Build local plugin scaffolds for Claude Code. **Requires Runlayer MCP.**

## Before You Start: Check Runlayer MCP

**MANDATORY REQUIREMENT: This plugin cannot function without Runlayer MCP. There is no alternative. Do not offer to proceed without it. Do not ask the user if they want to continue without it. Do not suggest workarounds.**

1. Check if `mcp__runlayer__list_servers` is available in your tools

2. **If NOT available:**
   - Say: "This plugin requires Runlayer MCP. Let me help you set it up."
   - Ask for their Runlayer URL (e.g., `https://your-org.runlayer.com`)
   - Direct them to: `<their-runlayer-url>/servers/d0b2d0c6-5d87-4f87-a2e1-7f0a60a6c0b5`
   - Tell them to click "Add to MCP client" and follow the setup
   - Say: "Let me know when you've installed it and restarted your agent."
   - **STOP HERE. Do not continue. Do not offer alternatives.**

2b. **If tools exist but return connection/auth errors before you even call them:**
   - Say: "I see Runlayer MCP is configured, but it doesn't seem to be authenticated. Please re-authorize and let me know when you're ready."
   - **STOP HERE. Do not continue. Do not offer alternatives.**

3. **If available** - call `mcp__runlayer__list_servers(scope="accessible")` to test it

4. **If you get an auth error:**
   - Say: "Please re-authorize the Runlayer MCP and let me know when you're ready to continue."
   - **STOP HERE. Do not continue. Do not offer alternatives.**

5. **Only proceed to the next section when `list_servers` returns successfully.**

## Directory Context

**Always check the current directory first:**

1. Run `ls -la` to understand the directory structure
2. Check if this is already a plugin marketplace (look for `.claude-plugin/marketplace.json`)
3. If it's a marketplace, new plugins should be created as subdirectories
4. If it's not a marketplace, confirm with the user where they want to create the plugin
5. **Always ask the user to confirm the location before creating any fi