Developer Kit plugin
A modular plugin set for Claude Code: skills, agents, commands and rules for Java, TypeScript, Python, PHP and AWS
- 360 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The base plugin wires Python hooks, and `developer-kit-tools` registers two MCP servers, NotebookLM and SonarQube
- Skills and agents in the set can run code, so review the plugins before enabling them
Install
- Works in
Manual install
/plugin marketplace add giuseppe-trisciuoglio/developer-kitThen enable `developer-kit-core` and the plugins for your stack.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The base plugin wires Python hooks, and `developer-kit-tools` registers two MCP servers, NotebookLM and SonarQube
- Skills and agents in the set can run code, so review the plugins before enabling them
This is third-party code. Review the repository files before installing.
What it does
Developer Kit splits a developer's tooling by language and domain. The base plugin `developer-kit-core` is required: it holds the shared agents, commands, skills and hooks. Stack plugins go on top of it: `developer-kit-java` (Spring Boot, LangChain4J, AWS SDK, GraalVM), `developer-kit-typescript` (NestJS, React, Next.js, Drizzle ORM), `developer-kit-python`, `developer-kit-php`, `developer-kit-aws` (CloudFormation, SAM), `developer-kit-ai`, `developer-kit-devops` and `developer-kit-tools`. The plugins carry skills, subagents for code review, refactoring, security audits and testing, and slash commands such as `/devkit.refactor` and `/devkit.java.code-review`. Path-scoped rules switch on by themselves when you open matching files, for example `*.java`. They are not copied into the project: you move them by hand or with `make copy-rules`. Besides Claude Code, the set installs into GitHub Copilot CLI, OpenCode and Codex CLI through a Makefile.
Who it is for. For developers on Java, TypeScript, Python or PHP and AWS teams who want ready-made skills, reviewers and rules for their stack in Claude Code.
Good fit when
- You need a review of a Spring Boot service or TypeScript code: `/devkit.java.code-review` and `/devkit.typescript.code-review` call the matching agents
- You are writing a CRUD module on NestJS with Drizzle ORM and want the agent to follow ready patterns and practices
- You need CloudFormation templates, SAM and AWS CLI work: the separate `developer-kit-aws` plugin covers them
- You want code rules to switch on by file mask: for `*.java`, say, the agent always uses constructor injection
- The team uses different CLIs: one set installs into Claude Code, Copilot CLI, OpenCode and Codex CLI
Not a fit when
- You need one small skill: even a single plugin pulls in the required `developer-kit-core`
- Your project is Python and you want ready skills: `developer-kit-python` leans on four agents and four rules
- You cannot accept Python hooks: the base plugin brings them with `developer-kit-core`
- You want rules already in the project with no manual steps: the plugins do not place them there
Example request
Generate a complete CRUD module for the User entity with NestJS and Drizzle ORMLimitations
The `developer-kit-core` plugin is required and the others sit on top of it. Rules do not land in the project on their own: copy the files from a plugin's `rules/` folder into `.claude/rules` by hand or with `make copy-rules PLUGIN=developer-kit-java`. Language plugins ship LSP settings in `.lsp.json` for Java, TypeScript, Python and PHP; the AWS and AI plugins have none.
The author warns that skills can execute code and advises installing plugins only from trusted sources, reading `SKILL.md` before enabling and trying the set outside a working environment. The claimed 150+ skills and 45+ agents are spread across the plugins, so enable only the ones you need.
How to disable. Disable or remove the plugins through the Claude Code plugin manager (`/plugin`). For a Makefile install, delete the copied files from your CLI's directory and remove transferred rules from `.claude/rules`.
FAQ
How do I install Developer Kit in Claude Code?
Run `/plugin marketplace add giuseppe-trisciuoglio/developer-kit`, then enable `developer-kit-core` and the plugins for your stack, such as `developer-kit-java` or `developer-kit-typescript`. A local folder installs with `/plugin install /path/to/developer-kit`.
Is the developer-kit-core base plugin required?
Yes, it is described as the required base. It carries 6 agents, 8 commands and 4 general skills, plus a hooks folder.
How do I turn on rules for Java or TypeScript?
Plugins do not place rules in the project. Copy the `.md` files from the plugin's `rules/` folder into `.claude/rules` or run `make copy-rules PLUGIN=developer-kit-java`. A rule then activates by the file mask in its header.
Does the set work outside Claude Code?
Yes, GitHub Copilot CLI, OpenCode CLI and Codex CLI are supported. After cloning the repository, `make install` detects your CLI, while `make install-claude`, `make install-opencode`, `make install-copilot` and `make install-codex` target a specific one.
What does the Java plugin contain?
`developer-kit-java` holds 9 agents, 11 commands, 51 skills and 4 rules covering Spring Boot, LangChain4J, AWS SDK and GraalVM. Java also gets an LSP setup on jdtls.
Discussion
No questions or reviews yet.
Related
PluginsClaudeKit Skills
ClaudeKit - Agent Skills
A plugin marketplace for Claude Code with a set of thirty-plus skills: frontend, backend, devops, databases, documents, debugging and MCP work
A Claude Code plugin marketplace by Frad LEE: Git and GitFlow, GitHub, refactoring, memory, research, image generation and interface work
Claude Code Skills and Agents
Claude Code Skills & Agents
A Claude Code plugin bundling skills and sub-agents: deep research, image generation, GitHub work, code review and model switching
A set of 24 slash commands for the Claude Code CLI: commits, review, refactoring, tests and cleanup without repeating the same prompts
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
Claude Codex Settings
claude-codex-settings
A marketplace of dozens of plugins for Claude Code, Codex, Cursor and Gemini: skills, commands, hooks, subagents and configs for many tasks
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Repository stars | Main difference |
|---|---|---|---|
| Developer Kit (this entry) | no | 360 | |
| Awesome Claude Code Plugins | no | 986 | a general marketplace of assorted plugins, while this is a connected series of language plugins with a required base |
| Knowledge Work Plugins | no | 32,184 | Anthropic plugins for office roles, while Developer Kit targets software development |
README in short
The description opens with the case for modularity: install only the plugins you need and get matching agents and rules that switch on by themselves. It then covers installation from the marketplace or through a Makefile, a quick start with the `/devkit.refactor` command, a plugin table with agent, command and skill counts, and the plugin folder layout. Near the end it describes validation: component validators, security scans in GitHub Actions and a warning that skills can execute code.