Help us improve
Share bugs, ideas, or general feedback.
Modular marketplace for developer kit plugins
npx claudepluginhub giuseppe-trisciuoglio/developer-kitCore agents and commands required by all Developer Kit plugins
AI/ML capabilities including prompt engineering, RAG, and chunking strategies
Comprehensive Java development toolkit with Spring Boot, testing, LangChain4J, and AWS integration
AWS infrastructure and CloudFormation expertise
TypeScript/JavaScript full-stack development with NestJS, React, and React Native
PHP and WordPress development capabilities
Python development capabilities
DevOps and containerization expertise
Project management and workflow commands
GitHub specification integration and verification
External tools integration skills for CLI utilities, APIs, and third-party services
Production-ready workflow orchestration with 80 focused plugins, 185 specialized agents, and 153 skills - optimized for granular installation and minimal token usage
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
No description available.
Share bugs, ideas, or general feedback.
A modular plugin system of reusable skills, agents, and commands for automating development tasks in Claude Code
Listed on:
Developer Kit for Claude Code teaches Claude how to perform development tasks in a repeatable way across multiple languages and frameworks. Built as a modular marketplace, you can install only the plugins you need.
# Install from marketplace (recommended)
/plugin marketplace add giuseppe-trisciuoglio/developer-kit
# Or install from local directory
/plugin install /path/to/developer-kit
Claude Desktop: Enable Skills in Settings
Developer Kit is organized as a modular marketplace with 11 independent plugins:
plugins/
├── developer-kit-core/ # Core agents/commands/skills (required)
├── developer-kit-java/ # Java/Spring Boot/LangChain4J/AWS SDK/GraalVM Native Image
├── developer-kit-typescript/ # NestJS/React/React Native/Next.js/Drizzle/Monorepo
├── developer-kit-python/ # Python development/AWS Lambda
├── developer-kit-php/ # PHP/WordPress/AWS Lambda
├── developer-kit-aws/ # AWS CloudFormation/AWS Architecture
├── developer-kit-ai/ # Prompt Engineering/RAG/Chunking
├── developer-kit-devops/ # Docker/GitHub Actions
├── developer-kit-project-management/ # LRA workflow/Meetings
├── developer-kit-tools/ # Additional development tools and MCP integrations
└── github-spec-kit/ # GitHub specification integration
Current marketplace totals: 116 skills, 43 agents, and 44 commands across the 11 plugin manifests.
Language plugins (Java, TypeScript, Python, PHP) include coding rules (rules/ directory) that auto-activate via globs: path-scoped matching to enforce naming conventions, project structure, language best practices, and error handling patterns. They also include LSP server configurations (.lsp.json) for real-time code intelligence, diagnostics, and navigation features.
The Developer Kit follows a systematic development workflow that ensures high-quality, well-documented features from idea to implementation:
Command: /devkit.brainstorm [idea-description]
Start here when you have a new feature idea. This command guides you to create a functional specification (WHAT the system should do, not HOW):
Output: Functional specification saved to docs/specs/YYYY-MM-DD--feature-name.md
Example:
/devkit.brainstorm Add user authentication with JWT tokens
Next step: After specification, continue with /devkit.spec-to-tasks
Command: /devkit.spec-to-tasks [--lang=java|spring|typescript|nestjs|react|python|general] [spec-file]
Converts the functional specification into atomic, executable tasks:
Output: Task list saved to docs/specs/[id]/tasks/TASK-XXX.md with complexity scores
Example:
/devkit.spec-to-tasks docs/specs/001-user-auth/
/devkit.spec-to-tasks --lang=spring docs/specs/001-user-auth/
Next step: Review task complexity and manage tasks with /devkit.task-manage
Command: /devkit.task-manage --action=[list|split|add|mark-optional|update|regenerate-index] [options]
Manage tasks after generation to ensure they're appropriately sized and prioritized: