Install
/plugin marketplace add giuseppe-trisciuoglio/developer-kitWho it's for
Use Developer Kit when you develop in Claude Code and do not want only generic AI answers, but repeatable, high-quality approaches for your own stack. It is a modular plugin marketplace aimed at Claude Code, teaching development tasks as reusable flows.
The repository title also names Java, TypeScript, Python, PHP, AWS, and AI. Treat that as “domain experience by stack”; do not invent unnamed language pack names.
Precondition: the main install is written as Claude Code’s /plugin marketplace add. The notes also write Multi-CLI Support: GitHub Copilot CLI, OpenCode CLI, Codex CLI. That is a compatibility statement; they give no install commands for those CLIs. Do not apply the Claude marketplace command there.
Another precondition: Plugins do not automatically install rules into your project. To use rules, you can only copy them by hand or go through a Makefile command. Visible text stops at that sentence; do not invent make targets or directories.
First try in 3 minutes
Official page:
https://github.com/giuseppe-trisciuoglio/developer-kit
Run in Claude Code (this changes plugin-marketplace state; confirm the repository name first):
/plugin marketplace add giuseppe-trisciuoglio/developer-kit
After adding, first see whether the plugin appears; do not change business code at once. The first time, do not copy rules — the Makefile command body never appeared.
Success signal: the marketplace source is added, and you can see Developer Kit related commands. If the command fails, stop.
If you want to try a named command, the notes give /devkit.refactor. First pick a disposable small file, have it only describe how it will refactor, without writing to disk; confirm, then run, and look at the diff at once. Do not invent other /devkit.* commands.
Use cases
Case 1: Connect from the marketplace. In Claude Code run /plugin marketplace add giuseppe-trisciuoglio/developer-kit. Confirm the plugin is visible. Do not reuse this command on Copilot / OpenCode / Codex at the same time.
Case 2: A controlled refactor with /devkit.refactor. This writes files. Bound the scope first, confirm, then run, then look at the diff. Rules still do not enter the project automatically; if you need rules, you can only “copy by hand or use a Makefile command” as the notes say, and do not invent a target name before the command body appears.
Boundaries
The main install is evidenced only as /plugin marketplace add giuseppe-trisciuoglio/developer-kit. Do not add an installer that never appeared.
Named commands are evidenced only as /devkit.refactor.
Multi-CLI is evidenced only as “works with Claude Code, GitHub Copilot CLI, OpenCode CLI, Codex CLI”; no install path for the last three.
Rules do not install automatically. The concrete Makefile command never appeared.
The notes give no language coverage or pricing. Keep undocumented items unknown.