Claude will provide a comprehensive review based on team standards, covering all critical aspects from code quality to security.

Project Setup

When starting a new project:

/project-setup

Claude will guide you through the complete setup process, ensuring all team conventions are followed.

For Team Administrators

Customizing Plugins

You can customize these plugins to match your specific team standards:

1. Fork this repository
2. Edit the command files in plugins/*/commands/*.md
3. Update the marketplace.json to point to your fork
4. Team members can then add your customized marketplace

Adding New Plugins

To contribute new plugins to this marketplace:

1. Create a new plugin directory under plugins/
2. Include the required structure:

   plugins/your-plugin-name/
   ├── .claude-plugin/
   │   └── plugin.json
   └── commands/
       └── your-command.md
   

3. Update .claude-plugin/marketplace.json to include your plugin
4. Submit a pull request with a description of the plugin's purpose

Plugin Structure

Each plugin follows this structure:

plugins/plugin-name/
├── .claude-plugin/
│   └── plugin.json          # Plugin metadata
└── commands/
    └── command-name.md       # Command definition and prompts

plugin.json Format

{
  "name": "plugin-name",
  "version": "1.0.0",
  "description": "Brief description of what the plugin does",
  "author": {
    "name": "Your Name"
  }
}

Command Markdown Format

Command files use YAML frontmatter for metadata:

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

# Command Name

Detailed instructions for Claude on how to execute this command...

Marketplace Structure

The marketplace is defined in .claude-plugin/marketplace.json:

{
  "name": "marketplace-name",
  "owner": {
    "name": "owner-name",
    "url": "https://github.com/owner-name"
  },
  "description": "Marketplace description",
  "plugins": [
    {
      "name": "plugin-name",
      "source": "./plugins/plugin-name",
      "description": "Plugin description"
    }
  ]
}

Best Practices

1. Keep Commands Focused: Each command should have a single, clear purpose
2. Document Thoroughly: Use clear descriptions and provide examples
3. Version Control: Update version numbers when making significant changes
4. Test Locally: Test plugins locally before sharing with the team
5. Gather Feedback: Regularly collect feedback from team members and iterate

Contributing

We welcome contributions from team members! To contribute:

1. Fork the repository
2. Create a feature branch (git checkout -b feature/new-plugin)
3. Make your changes and test thoroughly
4. Commit with clear messages (git commit -m 'Add: new deployment plugin')
5. Push to your branch (git push origin feature/new-plugin)
6. Open a Pull Request with a detailed description

Resources

• Claude Code Plugins Documentation
• Plugin Marketplaces Guide
• Anthropic's Plugin Announcement

License

MIT License - See LICENSE file for details

Support

For questions or issues:

• Open an issue in this repository
• Contact the team maintainer
• Refer to the Claude Code documentation

Made with ❤️ for streamlined team collaboration