Packaging: distribute darnit as a Claude Code plugin (and other coding-agent platforms)

[mlieberman85]

Goal

Make darnit installable as a first-class plugin on coding-agent platforms, starting with Claude Code's plugin system. Today users wire up the MCP server manually; a plugin should make it one command.

Why this matters

darnit is an MCP server whose primary user is a coding agent. Distributing it through the agent's native plugin mechanism is the most natural install path for the actual audience. The local repo already ships skills (/darnit-audit, /darnit-context, /darnit-comply, /darnit-remediate) — those are perfect plugin contents.

Scope

Claude Code plugin (primary)

• Package the MCP server + skills as a Claude Code plugin per the plugin spec.
• Plugin includes:
  • MCP server config that auto-runs darnit-mcp (via uvx, pipx, or bundled binary)
  • The four skills currently in skills/
  • Slash commands and settings as appropriate
• Distribute via Claude Code's plugin marketplace once available, or via a documented git-based install in the interim.

Other agent platforms (follow-up)

• Cursor, Windsurf, Continue.dev, Cline — survey their plugin/MCP-extension stories.
• Likely a single packaging effort feeds multiple platforms since they all speak MCP; the difference is the install-path UX.

Decisions to make

• Plugin repo: separate kusari-oss/darnit-claude-plugin or in-tree under packaging/claude-plugin/?
• How the plugin invokes the server — uvx darnit-mcp (requires uv), pipx run darnit-mcp (requires pipx), or bundled binary (requires Packaging: native install paths (standalone binary, pipx, Homebrew) #229)?

Acceptance

• Claude Code plugin installable in one command and exposes all four skills.
• Smoke test: /darnit-audit runs successfully from a fresh Claude Code install with the plugin enabled.
• Install docs cover at least Claude Code; other agents tracked as follow-up issues.