Evaluate packaging PromptCode as a Claude Code plugin/app

[avivsinai]

Overview

Anthropic recently announced Claude Code Plugins (public beta), a new distribution model for sharing custom collections of slash commands, agents, MCP servers, and hooks. We should evaluate packaging PromptCode as a Claude Code plugin to improve discoverability and ease of installation.

Background

Current State

PromptCode currently integrates with Claude Code via:

• promptcode cc command that installs slash commands to .claude/commands/
• Manual installation and configuration by users
• Limited discoverability (users need to know about PromptCode first)

Claude Code Plugins System

According to Anthropic's announcement:

What plugins can include:

• Slash commands: Custom shortcuts for operations
• Subagents: Specialized development task agents
• MCP servers: Connect to tools and data sources
• Hooks: Customize Claude Code's workflow behavior

Distribution:

• Plugins can be shared via git repositories or GitHub repos
• Installed with a single command: /plugin install <repo>
• Discoverable through plugin marketplaces
• Works across terminal and VS Code environments

Potential Benefits

1. Easier Discovery: Users could find PromptCode in Claude Code plugin marketplaces
2. One-Command Install: /plugin install promptcode-vscode instead of multi-step setup
3. Integrated Updates: Plugin system could handle updates automatically
4. Bundled Experience: Package slash commands, hooks, and potentially MCP servers together
5. Team Sharing: Make it easier for teams to standardize on PromptCode workflows

Evaluation Tasks

• Review Claude Code plugin documentation at docs.claude.com
• Determine what components to include:
  • Existing slash commands (/promptcode-*)
  • Consider creating an MCP server for file selection/prompt generation
  • Consider hooks for prompt optimization workflow
  • Consider subagents for specialized tasks
• Create .claude-plugin/marketplace.json metadata file
• Test plugin installation and functionality
• Determine hosting strategy (this repo vs separate plugin repo)
• Evaluate maintenance overhead vs current approach
• Consider deprecation path for promptcode cc if plugin approach is better

Questions to Answer

1. Does the plugin system support binary CLI tools like promptcode?
2. Can we bundle the CLI installation as part of the plugin?
3. How do plugin updates work with our release process?
4. Should this replace or complement the current promptcode cc integration?
5. What's the user experience for teams vs individuals?

References

• Claude Code Plugins Announcement
• Claude Code Documentation
• Current PromptCode CC integration: packages/cli/src/commands/cc.ts

Timeline

This should be evaluated during Q4 2025 as the plugin ecosystem matures and documentation becomes more comprehensive.