Modular plugin marketplace for Claude Code and agentic CLIs, with validated, spec-driven skills, agents, commands, and workflows for Java, TypeScript, Python, PHP, AWS, and AI.
# Add to your Claude Code skills
git clone https://github.com/giuseppe-trisciuoglio/developer-kitπ Languages: English | Italiano | δΈζ | EspaΓ±ol
A modular AI plugin system that supercharges your development workflow across languages and frameworks.
Installation β’ Quick Start β’ Plugins β’ Documentation β’ Changelog
Developer Kit is a modular plugin marketplace for Claude Code that teaches Claude how to perform development tasks in a repeatable, high-quality way. Instead of generic AI responses, you get domain-specific expertise for your exact tech stack.
No comments yet. Be the first to share your thoughts!
developer-kit-javadeveloper-kit-typescript# Install from marketplace
/plugin marketplace add giuseppe-trisciuoglio/developer-kit
# Or install from local directory
/plugin install /path/to/developer-kit
Enable Skills in Settings β Add giuseppe-trisciuoglio/developer-kit
# Clone the repository
git clone https://github.com/giuseppe-trisciuoglio/developer-kit.git
# Install via Makefile (auto-detects your CLI)
cd developer-kit
make install
# Or install for specific CLI
make install-claude # Claude Code
make install-opencode # OpenCode CLI
make install-copilot # GitHub Copilot CLI
make install-codex # Codex CLI
# After installation, start your CLI
claude
# Check available commands
/help
# Use a Developer Kit command
/devkit.refactor
# Or invoke a specs workflow
/specs:brainstorm
Generate a complete CRUD module for User entity with NestJS and Drizzle ORM
Review this Java Spring Boot service for security issues
Create a CloudFormation template for ECS with auto-scaling
Help me refactor this monolithic class into clean architecture
Generate unit tests for this TypeScript service with 100% coverage
Developer Kit provides four layers of capabilities:
Reusable capabilities loaded on-demand. Example:
[Skill: spring-boot-crud-patterns activated]
Skills automatically provide patterns, templates, and best practices for specific tasks.
Specialized sub-agents for complex workflows:
# Invoke via natural language
"Review this code as a Spring Boot expert"
# Or use commands
/devkit.java.code-review
/devkit.typescript.code-review
Transform ideas into production-ready code through a structured workflow:

| Command | When to Use | Output |
|---------|-------------|--------|
| /specs:brainstorm | New features, complex requirements | Full specification with 9 phases |
| /specs:quick-spec | Bug fixes, small enhancements | Lightweight 4-phase spec |
The specification lives in docs/specs/[id]/YYYY-MM-DD--feature-name.md
| Command | Description |
|---------|-------------|
| /specs:spec-to-tasks | Convert specification into executable task files |
| /specs:task-manage | Add, split, update, or reorganize tasks |
Tasks are generated in docs/specs/[id]/tasks/ with individual task files.
| Command | Description |
|---------|-------------|
| /specs:task-implementation | Guided implementation of a specific task |
| /specs:task-tdd | Test-Driven Development approach for the task |
Each task implementation updates the Knowledge Graph for context preservation.
| Command | Description |
|---------|-------------|
| /specs:task-review | Verify task meets specifications and code quality standards |
| /specs:code-cleanup | Professional cleanup: remove debug logs, optimize imports |
| /specs:spec-sync-with-code | Synchronize spec with actual implementation |
| Command | Description |
|---------|-------------|
| /specs:spec-quality-check | Interactive quality assessment of specifications |
| /specs:spec-sync-context | Sync Knowledge Graph, Tasks, and Codebase state |
| /specs:ralph-loop | Automated loop for spec-driven development |
| /devkit.refactor | Refactor existing code with architectural analysis |
| /devkit.github.create-pr | Create PR with comprehensive description |
Path-scoped rules auto-activate based on file patterns:
# Auto-activates for *.java files
globs: ["**/*.java"]
---
Always use constructor injection. Never use field injection with @Autowired.
π Note on Rules Installation
Plugins do not automatically install rules into your project. To use the rules, you can copy them manually or use the Makefile command:
# Copy rules from a specific plugin make copy-rules PLUGIN=developer-kit-java # Or manually copy .md files from the plugin's rules/ folder mkdir -p .claude/rules cp plugins/developer-kit-[language]/rules/*.md .claude/rules/The rules will be automatically activated based on the
globs:patterns defined in the header of each file.
| Plugin | Language/Domain | Components | Description |
|--------|-----------------|------------|-------------|
| developer-kit-core | Core | 6 Agents, 8 Commands, 4 Skills | Required base plugin with general-purpose capabilities |
| developer-kit-specs | Workflow | 9 Commands, 2 Skills | Specifications-driven development (SDD) workflow |
| developer-kit-java | Java | 9 Agents, 11 Commands, 51 Skills, 4 Rules | Spring Boot, LangChain4J, AWS SDK, GraalVM |
| developer-kit-typescript | TypeScript | 13 Agents, 3 Commands, 25 Skills, 17 Rules | NestJS, React, Next.js, Drizzle ORM, Monorepo |
| developer-kit-python | Python | 4 Agents, 4 Rules | Django, Flask, FastAPI, AWS Lambda |
| developer-kit-php | PHP | 5 Agents, 3 Skills, 4 Rules | WordPress, Sage, AWS Lambda |
| developer-kit-aws | AWS | 3 Agents, 19 Skills | CloudFormation, SAM, CLI, Architecture |
| developer-kit-ai | AI/ML | 1 Agent, 3 Skills, 1 Command | Prompt Engineering, RAG, Chunking |
| developer-kit-devops | DevOps | 2 Agents | Docker, GitHub Actions |
| developer-kit-tools | Tools | 4 Skills | NotebookLM, Copilot CLI, Gemini, Codex |
| github-spec-kit | GitHub | 3 Commands | GitHub spec integration |
Total: 150+ Skills | 45+ Agents | 20+ Commands | 45+ Rules
developer-kit/
βββ plugins/
β βββ developer-kit-core/ # Required base
β β βββ agents/ # Agent definitions (.md)
β β βββ commands/ # Slash commands (.md)
β β βββ skills/ # Reusable skills (SKILL.md)
β β βββ rules/ # Auto-activated rules
β β βββ .claude-plugin/
β β βββ plugin.json # Plugin manifest
β βββ developer-kit-java/ # Java ecosystem
β βββ developer-kit-typescript/ # TypeScript ecosystem
β βββ ...
βββ .skills-validator-check/ # Validation system
βββ Makefile # Installation commands
Each plugin is self-contained with its own manifest, components, and dependencies.
Install only the plugins you need:
# Core + Java + AWS
make install-claude
# Then enable: developer-kit-core, developer-kit-java, developer-kit-aws
# Full-stack TypeScript
# Enable: developer-kit-core, developer-kit-typescript, developer-kit-aws
Rules automatically activate based on file patterns:
---
globs: ["**/*.java"]
---
# This rule activates for all Java files
- Use constructor injection
- Follow naming conventions
Language plugins include LSP server configurations (.lsp.json):
| Language | Server | |----------|--------| | Java | jdtls | | TypeScript | typescript-language-server | | Python | pyright-langserver | | PHP | intelephense |
| Language | Skills | Agents | Commands | Rules | LSP | |----------|--------|--------|----------|-------|-----| | Java/Spring Boot | 51 | 9 | 11 | 4 | β | | TypeScript/Node.js | 25 | 13 | 3 | 17 | β | | Python | 2 | 4 | 0 | 4 | β | | PHP/WordPress | 3 | 5 | 0 | 4 | β | | AWS/CloudFormation | 19 | 3 | 0 | 0 | β | | AI/ML | 3 | 1