Three Claude Code Plugins Worth Installing on Your First Day

Last time we taught Claude Code to remember your project by writing skills and agents by hand. That's the right instinct — but you don't have to forge every knife in your own kitchen. Some tools, someone already made better than you would, and you just buy them.

That's what plugins are. A plugin is a bundle of skills, agents, hooks, or tool connections that another person built and packaged so you can install it in one command. Claude Code ships with an official marketplace — a curated shelf, vetted by Anthropic — already switched on. You browse it, pick what you want, and it drops straight into your kitchen.

Here's how to open the shelf, and the three plugins I'd hand a beginner before anything else.

Opening the shelf

Inside Claude Code, type /plugin and press Tab until you reach the Discover tab. That's the catalog. Every plugin below lives on the official marketplace, so you can also skip the menu and install by name:

/plugin install <name>@claude-plugins-official

One thing that trips people up: after installing, run /reload-plugins to actually switch it on in the current session. Now, the three picks.

1. commit-commands — the dishwasher for git

If you've vibe-coded anything real, you've hit this wall: the code works, and now you're staring at git trying to remember whether it's add . then commit -m then push, and what to even write in the message. Version control is the chore nobody enjoys, so beginners skip it — right up until they break something and have nothing to roll back to.

commit-commands does the dishes for you. It reads what you changed, writes a sensible commit message describing it, and makes the commit — in a single step.

/plugin install commit-commands@claude-plugins-official

After /reload-plugins, make a change to a file and run:

/commit-commands:commit

It stages your work, generates the message from the actual diff, and commits. The same plugin also handles pushing and opening pull requests when you're ready for those. The real win isn't saved keystrokes — it's that saving your progress stops being a decision you have to make, so you actually do it.

2. security-guidance — the smoke detector

Here's the quiet fear of building with AI: I can't read this code well enough to know if it's dangerous. You asked for a feature, you got forty lines that look plausible, and somewhere in there might be a hole a stranger could walk through.

security-guidance is the smoke detector you mount and forget. Once installed, it reviews each change Claude makes for common vulnerabilities — things like command injection, unsafe handling of untrusted data, and cross-site scripting — and tells Claude to fix what it finds in the same session, before the risky code ever settles into your project.

/plugin install security-guidance@claude-plugins-official

There's no command to run. It works in the background, like a detector on the ceiling: silent until it smells smoke, then loud enough that the problem gets fixed while you're still standing there. For a beginner shipping AI-written code to the open internet, that safety net is worth the thirty seconds it takes to install.

3. explanatory-output-style — the chef who explains while cooking

The first two plugins do work for you. This one teaches you — and for a learner, that compounds faster than either.

By default Claude Code is efficient: it makes the change and moves on. explanatory-output-style changes its manner so that as it works, it drops in short notes about why — why this approach over the obvious one, what trade-off it just made, what a given line is guarding against.

/plugin install explanatory-output-style@claude-plugins-official

The difference is the gap between watching a chef plate a dish and having them talk you through each move as they make it. You're building the same thing either way, but with one of them you walk away able to cook it yourself. If your goal is to understand what you're shipping and not just ship it, turn this on and leave it on for a few weeks.

Before you install everything on the shelf

Two habits will save you later.

Only install from sources you trust. A plugin can run code on your machine with your permissions — that's what makes it powerful, and also why you don't grab random ones. The official marketplace is curated by Anthropic, which is exactly why all three picks here live on it. Wander to other marketplaces only once you know what you're doing.

Every plugin has a rent. Each one you install adds a little to what Claude Code carries in its head every single turn — the Discover tab even shows a "context cost" estimate before you install. Three well-chosen plugins is a sharp kitchen. Twenty you never use is clutter that quietly makes every session slower. Install deliberately, and clear out what you stopped reaching for.

Start with these three: one to save your work without thinking, one to catch what you can't see, one to actually teach you as you go. That's a beginner's kitchen properly stocked — and every plugin you add after this, you'll add because you felt the gap, which is exactly the right reason.

New to this? Start with the Claude Code setup guide, and if you want to build your own skills instead of installing them, here's how to give Claude Code a memory.