No description
Find a file
2026-05-29 15:45:20 -05:00
.claude-plugin cleaned up orch 2026-05-29 15:24:01 -05:00
development-agents add mcps 2025-11-12 21:47:03 -06:00
example init commit 2025-11-12 14:59:10 -06:00
orchestrate cleaned up orch 2026-05-29 15:24:01 -05:00
plugin-developer add marketplace pluging 2025-12-23 15:13:24 -06:00
.gitignore init commit 2025-11-12 14:59:10 -06:00
CLAUDE.md add marketplace pluging 2025-12-23 15:13:24 -06:00
README.md redo readme 2026-05-29 15:45:20 -05:00

Personal Claude Code Plugin Marketplace

A Claude Code plugin marketplace — both a working set of plugins and a framework for building more.

Overview

This repository is a registered Claude Code marketplace (.claude-plugin/marketplace.json) shipping four plugins, plus reference docs for authoring your own. The example plugin doubles as a template; the rest are production-derived tooling.

Plugins

example-plugin

Minimal template demonstrating plugin structure. Copy it to start a new plugin.

  • Agent: hello-agent · Command: /hello · Skill: code_style · MCP: sample config

development-agents

Opinionated Go-backend and SolidJS-frontend patterns derived from production codebases.

  • Agents: backend-agent (Go/Fiber/GORM, clean architecture), frontend-agent (SolidJS + TanStack Query — not React)
  • Skills: go_logging, gorm_patterns, routing_patterns, dependency_injection, solidjs_patterns, api_integration, code_commenting

plugin-developer

Meta-plugin for creating, validating, and managing Claude Code plugins.

  • Commands: /new-plugin, /new-command, /new-agent, /new-skill, /validate
  • Agents: plugin-architect, command-writer, skill-author, plugin-reviewer
  • Skills: plugin_structure, marketplace_publishing, plugin_validation

orchestrate

Thin-orchestrator full-cycle task delivery — every phase runs in a dedicated sub-agent.

  • Skills: /orchestrate (default), /orchestrate-lite (small tasks, lower model budget), /orchestrate-teams (agent-teams mode, experimental flag)
  • Agents: orchestrate-planner, -implementer, -simplifier, -reviewer, -fixer, -cleaner, plus -teams-implementer/-teams-reviewer
  • Depends on the superpowers and caveman plugins (sub-agents invoke their skills). See orchestrate/README.md.

Quick Start

1. Clone and Customize

# Clone or copy this repository
git clone <your-repo-url>
cd marketplace

# Update marketplace configuration
# Edit .claude-plugin/marketplace.json with your name

2. Create Your First Plugin

# Copy the example plugin as a template
cp -r example my-plugin

# Update plugin metadata
# Edit my-plugin/plugin.json and my-plugin/.claude-plugin/plugin.json

3. Register Your Plugin

Add your plugin to .claude-plugin/marketplace.json:

{
  "plugins": [
    {
      "name": "my-plugin",
      "source": "./my-plugin",
      "description": "Your plugin description"
    }
  ]
}

4. Test in Claude Code

# Start Claude Code in this directory
claude

# Test your command
/hello

Plugin Structure

marketplace/
├── .claude-plugin/
│   └── marketplace.json          # Plugin registry (all plugins listed here)
├── example/                       # Minimal template plugin
│   ├── .claude-plugin/plugin.json
│   ├── agents/hello-agent.md
│   ├── commands/hello.md
│   ├── skills/code_style.md
│   └── .mcp.json                 # MCP server config (optional)
├── development-agents/            # Go + SolidJS patterns
│   ├── agents/                   # backend-agent, frontend-agent
│   └── skills/                   # go_logging, gorm_patterns, ...
├── plugin-developer/              # Meta-plugin for authoring plugins
│   ├── commands/                 # /new-plugin, /validate, ...
│   ├── agents/                   # plugin-architect, plugin-reviewer, ...
│   └── skills/                   # plugin_structure, ...
├── orchestrate/                   # Thin-orchestrator task delivery
│   ├── agents/                   # orchestrate-planner, -implementer, ...
│   └── skills/                   # orchestrate/, orchestrate-lite/, orchestrate-teams/
└── README.md

Each plugin also carries its own plugin.json and a .claude-plugin/plugin.json. Skills may be a single name.md file or a name/SKILL.md directory.

Plugin Components

Commands

Commands are user-facing actions invoked via /command-name.

Structure:

---
description: Brief description of what this command does
---

# Command Instructions

Detailed instructions for Claude on how to respond...

File location: plugin/commands/command-name.md

Agents

Agents are specialized autonomous workers for complex tasks.

Structure:

---
name: agent-name
description: When to use this agent
model: sonnet
color: blue
---

# Agent Prompt

Core competencies and instructions...

File location: plugin/agents/agent-name.md

Skills

Skills are reusable patterns and expertise that Claude can reference.

Structure:

---
name: Skill Name
description: When to use this skill
---

# Skill Content

Guidelines, patterns, and examples...

File location: plugin/skills/skill-name.md

MCP Servers (Optional)

MCP (Model Context Protocol) servers enable integration with external services.

Structure:

{
  "mcpServers": {
    "ServerName": {
      "command": "npx|docker",
      "args": ["..."],
      "env": {
        "ENV_VAR": "${SYSTEM_ENV_VAR}"
      }
    }
  }
}

File location: plugin/.mcp.json

Development Workflow

Adding a Command

  1. Create plugin/commands/my-command.md
  2. Add YAML frontmatter with description
  3. Write instructions for Claude
  4. Test with /my-command

Adding an Agent

  1. Create plugin/agents/my-agent.md
  2. Add YAML frontmatter (name, description, model, color)
  3. Write agent prompt with core competencies
  4. Agent is automatically available

Adding a Skill

  1. Create plugin/skills/my-skill.md
  2. Add YAML frontmatter with name and description
  3. Write skill content (patterns, guidelines, examples)
  4. Reference in commands or agent prompts

Adding MCP Integration

  1. Create or update plugin/.mcp.json
  2. Add server configuration with command and args
  3. Use environment variables for secrets
  4. Restart Claude Code session to load MCP servers

Best Practices

Naming Conventions

  • Commands: lowercase-with-hyphens.md → /command-name
  • Agents: descriptive-name.md
  • Skills: snake_case.md
  • Plugins: lowercase-with-hyphens

Security

  • Never commit credentials - use environment variables
  • Reference env vars: ${VAR_NAME} in configuration
  • Use minimal required permissions for service accounts

Organization

  • Keep plugins focused on a specific domain or workflow
  • Group related commands, agents, and skills together
  • Use clear, descriptive names for all components

Example Plugin

The included example plugin demonstrates:

  • hello-agent - Shows basic agent structure with YAML frontmatter
  • /hello command - Demonstrates simple command with instructions
  • code_style skill - Shows how to define reusable guidelines
  • .mcp.json - Template for MCP server configuration

Use these as templates for your own plugins.

Troubleshooting

Plugin not loading

  • Verify plugin is registered in .claude-plugin/marketplace.json
  • Check that plugin.json exists in both root and .claude-plugin/ directories
  • Validate JSON syntax
  • Restart Claude Code

Command not found

  • Verify command file exists in commands/ directory
  • Check YAML frontmatter is valid
  • Ensure filename matches command name
  • Restart Claude Code

MCP connection failed

  • Verify environment variables are set
  • Check Docker is running (if using Docker-based MCP servers)
  • Validate network connectivity
  • Check MCP server URL and credentials

Resources

License

Customize this section with your preferred license.