A series of agents to support production ready python development
You are a Python expert with deep knowledge of modern Python practices, performance optimization, and the Python ecosystem. You have exceptional ability to spot type safety issues, performance problems, and opportunities for better Python patterns. Your reviews are thorough, educational, and always aim to help developers write better, more maintainable Python code.
Use this agent when the task implementation preparation agent has completed its analysis and the user is ready to execute the actual implementation of a task. This agent should be called after the preparation phase is complete and an Implementation Plan exists on the GitHub wiki. Examples: <example>Context: User has a prepared task ready for implementation. user: 'The preparation is done, please implement the user authentication feature' assistant: 'I'll use the task-executor-tdd agent to implement the authentication feature following TDD principles' <commentary>The task preparation is complete, so use the task-executor-tdd agent to execute the implementation following the established plan.</commentary></example> <example>Context: Task preparation agent has finished and user wants to proceed with implementation. user: 'Great, the plan looks good. Let's implement it now' assistant: 'I'll launch the task-executor-tdd agent to execute the implementation using test-driven development' <commentary>User is ready to move from planning to implementation, so use the task-executor-tdd agent.</commentary></example>
Use this agent when a task implementation has been completed and needs comprehensive review before being considered finished. This agent should be invoked by the task implementation execution agent after code changes are made to ensure quality and correctness before task closure. Examples: <example>Context: The task implementation execution agent has just finished implementing a new API endpoint for user authentication. user: 'I've completed the implementation of the user authentication endpoint with JWT tokens and password hashing' assistant: 'Great! Now let me use the task-implementation-reviewer agent to conduct a thorough review of your implementation' <commentary>Since the implementation is complete, use the task-implementation-reviewer agent to review the git diff, check code quality, ensure tests pass, and verify the implementation meets requirements.</commentary></example> <example>Context: A developer has finished refactoring the database connection logic and wants to ensure the changes are solid before moving on. user: 'Just finished refactoring the database connection pooling logic across the main-api service' assistant: 'Excellent! Let me invoke the task-implementation-reviewer agent to review your refactoring changes' <commentary>The implementation is complete and needs review, so use the task-implementation-reviewer agent to examine the git diff and ensure the refactoring maintains functionality while improving code quality.</commentary></example>
Use this agent when the user requests implementation of a specific task or feature. This agent should be invoked BEFORE any actual implementation begins to ensure proper preparation and planning. Examples: <example>Context: User wants to implement a new feature for invoice processing. user: 'I need to implement the email attachment processing feature for invoices' assistant: 'I'll use the task-prep-architect agent to analyze the requirements and create a comprehensive implementation plan before we begin coding.' <commentary>Since the user is requesting feature implementation, use the task-prep-architect agent to prepare the implementation plan first.</commentary></example> <example>Context: User wants to implement a bug fix or enhancement. user: 'Can you implement the user authentication middleware for the API?' assistant: 'Let me start by using the task-prep-architect agent to gather context and create a proper implementation plan.' <commentary>The user is asking for implementation, so the task-prep-architect agent should be used first to prepare the work.</commentary></example>
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A marketplace for Claude Code plugins focused on production-ready Python development.
To add this marketplace to your Claude Code installation, use one of the following methods:
Option 1: From a local directory
If you've cloned this repository locally:
/plugin marketplace add /path/to/claude-code-plugin-marketplace
Replace /path/to/claude-code-plugin-marketplace with the absolute path to the directory where you cloned this repository.
Option 2: From GitHub (when published)
/plugin marketplace add owner/repo
Replace owner/repo with the GitHub repository path.
.claude-plugin/marketplace.json in that directoryYou can install plugins at different scopes depending on your needs:
Install plugins globally for all your projects using the /plugin command:
/plugin install plugin-name@marketplace-name
This saves to ~/.claude/settings.json and applies across all projects.
Install plugins for a specific project only by manually configuring your project settings:
Create or edit .claude/settings.json in your project root:
{
"enabledMarketplaces": [
{
"name": "code-plugin-marketplace",
"source": "./.claude-plugin/marketplace.json"
}
],
"enabledPlugins": {
"python-coding-agents@code-plugin-marketplace": true,
"voice-notification@code-plugin-marketplace": true
}
}
Benefits of project-level installation:
.claude/settings.json to share with teamFor machine-specific settings that shouldn't be committed:
Create .claude/settings.local.json in your project root. This file overrides both global and project settings but stays out of version control.
Settings are applied in this order (later overrides earlier):
~/.claude/settings.json - Your personal defaults.claude/settings.json - Team shared settings.claude/settings.local.json - Machine-specific overridesA series of agents to support production-ready Python development.
Installation:
/plugin install python-coding-agents@code-plugin-marketplace
Features:
Voice notifications when Claude needs user input, with support for multiple TTS providers.
Installation:
/plugin install voice-notification@code-plugin-marketplace
Features:
Configuration:
Optional environment variables:
ELEVENLABS_API_KEY - For ElevenLabs TTS (highest quality)OPENAI_API_KEY - For OpenAI TTS (high quality)ENGINEER_NAME - Your name for personalized notifications (e.g., "Eduardo")After adding the marketplace, verify it's configured:
/plugin marketplace list
Check available plugins:
/plugin list
Manage installed plugins:
/plugin
claude-code-plugin-marketplace/
├── .claude-plugin/
│ └── marketplace.json # Marketplace configuration
├── python-coding-agents/ # Python development agents plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin metadata
│ ├── agents/ # Agent definitions
│ └── commands/ # Custom commands
├── voice-notification/ # Voice notification plugin
│ ├── plugin.json # Plugin metadata with hooks
│ ├── notification.py # Main notification script
│ └── utils/ # TTS and LLM utilities
│ ├── tts/ # TTS providers
│ └── llm/ # LLM integrations
└── README.md
Make sure you're pointing to the marketplace directory, not the marketplace.json file:
❌ Wrong: /plugin marketplace add ./.claude-plugin/marketplace.json
npx claudepluginhub eduardoarantes/claude-code-plugin-marketplace --plugin python-coding-agentsA series of agents to support production ready development
Tools for product team workflows including issue validation and management
Parallel UI story validation — discovers YAML user stories, fans out bowser-qa-agents with shared auth state, aggregates pass/fail results with screenshots and a markdown report
Voice notifications when Claude needs user input
A series of agents to support production ready typescript development
Audio feedback system with multilingual TTS announcements, AI-powered contextual messages, and sound effects for Claude Code. Transform your coding experience with intelligent voice feedback that keeps you informed without breaking your flow.
Audio feedback when Claude Code agent completes tasks using pocket-tts
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.