Claude Code Plugins for Non-Coders (Start With One)

If you don’t code, the one Claude Code plugin to install first is skill-creator. It writes skills for you when you describe what you want. Most of the official catalog is developer tooling you can skip. Once you start building apps or pages, add superpowers, frontend-design, and security-guidance. Skip the Word, Excel, PowerPoint and PDF skills too, because your Claude account already brings those.

311 plugins and a brand new install

This week I helped my sister set up Claude Code, and once VS Code was installed and signed in, the first question was which plugins and skills to install. The official plugin catalog listed 311 plugins the day I checked. That’s a lot of choices for someone who opened VS Code an hour ago.

Search for “best Claude Code plugins” and the lists that come up are written for developers. They recommend language servers, documentation lookups for code libraries, and GitHub tools. Good picks if you’re a developer. This post is for everyone else, the people who build by asking Claude in plain English.

My first plugin went in back in March, and my list is five plugins now, one of them switched off. skill-creator was the first plugin I ever installed. frontend-design came nine days later, superpowers joined in May, and security-guidance in June. Everything else I use, I made myself or reworked from something I found, which is the second half of this post.

If you haven’t installed Claude Code yet, start with my Claude Code setup, which walks through VS Code, the extension, and your first folder. This post picks up right after that.

What is a Claude Code plugin?

A Claude Code plugin is an add-on package you install from a catalog, and it can hold skills plus other pieces like commands and connections to outside tools. Anthropic’s plugin docs put it in one line: “A Claude Code plugin is a directory of skills, agents, hooks, MCP servers, or other components that Claude Code installs and loads as one unit.”

A skill is smaller. It’s a single file of plain-English instructions that Claude reads when it fits what you asked for. So a plugin is the box, and skills are usually what’s inside it. You install plugins from someone else. Skills are the thing you’ll end up writing yourself.

Which Claude Code plugin should a non-coder install first?

skill-creator, from Anthropic. It’s the one plugin I’d hand anyone, whether they write, research, build apps, or just sort files. Its catalog description is “Create new skills, improve existing skills, and measure skill performance,” which in plain terms means you say “I keep asking you to do this, save it” and it writes a working skill file without you ever opening one.

It goes first because it’s the bridge to everything after. Every other plugin is someone else’s idea of what you need. skill-creator is how you build what you need.

If you mostly use Claude Code to write, research, or organize files, you can stop here. That’s a complete setup.

How do you tell which Claude Code plugins are for developers?

Read the one-line description and look for coding words. The catalog files 123 of its 311 plugins under “development,” and another 73 under database, monitoring, deployment, testing and migration. That’s 196 of 311 built for people who write and ship code.

The category label alone won’t settle it, though. skill-creator is filed under development too, and it’s the one I’d give everybody. So I go by the description. Skip a plugin when it mentions any of these:

• Repositories, pull requests, commits, or branches
• Language servers, TypeScript, Python, or any other programming language by name
• Databases, SQL, or migrations
• Deployments, builds, logs, or monitoring
• Test-driven development or test suites

If you can’t say in one sentence what a plugin would do for you this week, skip it too. Each one adds to what Claude reads before it starts working, which is why Claude Code’s plugin details list a “Context cost” for each one.

What you can skip no matter what

• Word, Excel, PowerPoint and PDF skills. When you sign in with a claude.ai account, those skills come along. Anthropic’s docs say pdf and xlsx always sync, and the rest follow what you’ve turned on in your claude.ai skills settings. Mine show up in VS Code with no install.
• Plugins from random marketplaces, for now. More on that below.

Which Claude Code plugins should you add once you start building?

Three, and only when you start making apps, tools, or web pages with Claude Code. That’s when I added them, and they’re the only other plugins I keep switched on.

Plugin	When to add it	What it does
skill-creator	Day one, everyone	Writes and improves skills from a plain-English description
superpowers	When you start building apps or tools	Makes Claude brainstorm and plan before it builds, debug step by step, and check its work
frontend-design	When you build pages or tools people will look at	Gives what you build a real design instead of the default look
security-guidance	When anything you build has logins or other people’s data	Reviews the code Claude writes for security holes, like passwords left in the code

superpowers is the one that changes how Claude behaves. Its README says it best: when it sees you’re building something, “it doesn’t just jump into trying to write code. Instead, it steps back and asks you what you’re really trying to do.” That’s the habit you want when you’re building. It’s also made for building software, with skills for testing and version control, so if you only write or research, it adds planning steps to requests that don’t need them. It’s made by a developer who goes by obra and listed in Anthropic’s catalog.

frontend-design and security-guidance are both from Anthropic. Claude uses frontend-design on its own whenever you’re building something with a screen. security-guidance watches the code as Claude writes it, and it’s the one I’d add before anything you build goes live.

How do you install a Claude Code plugin in VS Code?

Type /plugins into the Claude Code prompt box and pick from the list. The whole thing takes about two minutes:

1. In the Claude Code panel in VS Code, type /plugins (with an s) and press Enter. The Manage plugins window opens.
2. Find skill-creator and click Install.
3. When it asks where to install, pick the option for you across all your projects.
4. Later, when you start building, come back and add the other three the same way.
5. If it tells you to run /reload-plugins, run it. Or just close Claude Code and open it again.

Using Claude Code in a terminal instead? Type /plugin install skill-creator@claude-plugins-official, and swap in any other name from the table. If you’re following another guide, watch for this: /plugin is the terminal command, and in VS Code it’s /plugins, plural. The notes I worked from this week had it the terminal way. One letter.

To check it worked, type / in the prompt box and scroll. Plugin skills show up with the plugin’s name in front, like skill-creator:skill-creator.

How do you start making your own Claude Code skills?

You start by not making any. Use Claude Code normally for a week or two, and pay attention to what you ask for more than once. That repeat is your first skill.

The habit is two sentences you say out loud to Claude:

• “Turn this into a skill.” Say it right after Claude does something well that you’ll want again. With skill-creator installed, it writes the skill file and saves it for you.
• “Remember not to do that.” Say it when Claude does something you didn’t like. That’s how it stops repeating the same mistake. I wrote more about that in how Claude Code memory works for me.

That’s how my own setup got built, one repeat at a time. I have over a hundred skills now, and at my last count, most of the ones I installed from someone else I never touched. The ones I lean on every day are the ones that know me, and that only happens when you make them or rework them. I wrote the whole argument in I don’t install Claude Code skills, I customize them.

If you want to see what’s inside a skill file before you let Claude write one, what a Claude Code skill is, and how to make one has one you can copy, line by line.

A prompt to make your first skill

Paste this into Claude Code at the end of a chat where you did something you’ll want to do again:

Look back over what we did in this chat. Find the task I'd want to repeat, and use the skill-creator skill to turn it into a Claude Code skill for me. Before you write it, ask me up to 3 questions, one at a time: how I want it done, what the finished result should look like, and anything it should never do. Save it where my personal skills go, then tell me in one sentence what I'd say to use it next time.

What to watch out for with plugins

A plugin can do more than a skill can, so it gets more trust than a skill does. Anthropic says so plainly in its plugin security docs: “A Claude Code plugin you install can execute arbitrary code on your machine with your user privileges.” Its advice is to review a plugin before you install it, whichever catalog it comes from.

That’s the reason I’d stay inside the official catalog for your first month. A few more things to know before you install:

• superpowers phones home a little. Its README says an optional visual feature loads a logo from its maker’s website, and that request includes which version you’re running. You can turn it off with a setting called SUPERPOWERS_DISABLE_TELEMETRY, and Claude can set that for you if you ask.
• Turning a plugin off is one switch. In VS Code, type /plugins and flip its toggle. In the terminal, /plugin uninstall plus the install name removes it. Nothing is permanent.
• Official plugins update themselves. You’ll get a note to run /reload-plugins when a new version lands.

Frequently asked questions

Try it yourself

If you don’t code, the first Claude Code plugin to install is skill-creator, and it can be your whole list until you start building apps or pages. Then add superpowers, frontend-design, and security-guidance, and skip anything whose description talks about repositories, databases, or deployments. Install skill-creator, use Claude Code for a week, and the first time you catch yourself asking for the same thing twice, say “turn this into a skill.”

I write up everything I build with Claude Code here, the good parts and the “one letter off” parts. Subscribe if you want the next one, and go install your first plugin.