Claude MCP for Plugin Development

Claude Code, with the Rogue Arena MCP plugin loaded, drives the full plugin-development loop — research offline install paths, scaffold the project, write the YAML, manage vault files, and iterate until the plugin ships clean. Two skills do the heavy lifting, in sequence.

/rogue-plugin-brainstorm

Research the install story, then scaffold every local file for develop.

What it does:

• Researches exhaustively online — install paths, version pins, dependency trees, offline-friendly options
• Plans the plugin slate — one plugin or a coordinated set, with names, descriptions, and parent/child relationships
• Prompts you for empty plugin IDs (or an empty canvas) so it has somewhere to land the YAML and vault files
• Scaffolds every project locally — YAML files, download scripts, vault folders, project.json metadata
• Hands the bundle off to /rogue-plugin-develop to take the drafts and turn them into working plugins

Hand it any target — the research is the same:

• “Three RCE-vulnerable Linux apps” → hunts down candidates, picks specific versions with documented CVEs, balances ease-of-install vs. realism
• “Outlook on Windows with mailbox content” → finds the right Office install path, picks an offline-installable channel, plans the mailbox seeding, lines up Auto-Login dependencies
• “Elastic Stack server + Agent on every endpoint” → splits the work across multiple plugins, plans the parent/child wiring, flags which boxes need internet during build

/rogue-plugin-develop

Take scaffolded YAML and loop it into a working plugin.

What it does:

• Reads the local files brainstorm produced (or jumps into an existing plugin you point it at)
• Builds out the testing canvas — VLANs, machines, a DC if needed, the right plugin loadout, all the params filled in
• Reads deploy logs after you hit Apply Plan and triages failures end-to-end
• Loops: write YAML → build → read log → fix → repeat until the plugin installs cleanly with no internet at deploy time
• Pushes the final YAML, params, and vault files up to the platform via MCP

Heads up — Claude will probably ask for internet on the first build

Plugins ship offline, but the first build usually needs the internet to pull installers, packages, container images, or git repos. Claude will ask you to flip “Enable Internet During Architect Build” on the staging machines and redeploy, then it fetches what it needs onto the build VM and pushes the artifacts back into each plugin’s vault for the final offline-only verification.