Developer Kit for Claude Code

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.
Quick Start
# 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
Architecture
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.
Workflow
The Developer Kit follows a systematic development workflow that ensures high-quality, well-documented features from idea to implementation:
1. Brainstorming Phase
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):
- Idea Refinement: Deep exploration through structured dialogue
- Use Case Definition: Define user behaviors and business rules
- Acceptance Criteria: Establish testable conditions for completion
- Specification Review: Validate with user
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
2. Specification to Tasks Phase
Command: /devkit.spec-to-tasks [--lang=java|spring|typescript|nestjs|react|python|general] [spec-file]
Converts the functional specification into atomic, executable tasks:
- Task Decomposition: Break down specification into actionable tasks
- Dependency Mapping: Identify task dependencies
- Acceptance Criteria: Each task has clear completion criteria
- Implementation Commands: Pre-filled commands for execution
- Complexity Scoring: Automatic calculation of task complexity (0-100+ scale)
- Strong Constraint: Tasks with score ≥ 51 MUST be split before implementation
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
2.5. Task Management Phase (NEW)
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: