Start here: the setup prompt
There are 14 tools on this page, from three of my videos. Please don’t install them all at once. Pick one, add it, use it for a week, then come back for the next.
Open Claude Code in your project, copy this prompt, fill in the one you want and let Claude walk you through it.
Plugins, skills and extensions aren’t the same thing
Most of these install inside Claude Code with a /plugin command. A few are skills, an installer you run once, or a browser extension. That’s why the prompt tells Claude to read each tool’s own instructions instead of guessing.
The five to install first
From the “don’t use Claude Code without these” video. The four /plugin ones are from Anthropic’s official plugin marketplace. Type the command inside Claude Code, not in your normal terminal.
1. Security Guidance
Watches while Claude writes and warns you about things like hard-coded passwords and keys, plus 25-odd other kinds of security problems. It checks edits as they happen, reviews the changes when Claude finishes, and can check a commit.
The catch: It needs Python on your computer. It flags problems, it doesn’t make your app secure on its own.
2. Playwriter
Lets Claude drive your own Chrome: open your app, click through it and find what’s broken before your customers do. It’s a Chrome extension plus a small command-line tool and a skill, not a /plugin, so there are three parts.
The catch: It works in your real, logged-in Chrome. Test on a practice page or local copy of your site, not your live checkout.
3. Frontend Design
Turns generic AI-looking pages into something that looks designed. Claude makes deliberate choices about colour, fonts and layout for your brand instead of reaching for template defaults.
4. Code Simplifier
Looks at the code Claude just changed and tidies the bloat, without changing what the code does.
Try it: “Use the code simplifier on what you just changed.”
5. Code Review
Sends a team of four review agents over a pull request (a proposed change on GitHub) and posts only the problems they’re confident about. You fix them before you merge.
Try it: on a pull request branch, type /code-review.
The catch: It reviews one pull request at a time, not your whole project, and it needs the GitHub command-line tool (gh) set up. No GitHub yet? Skip this one for now.
Five that put you ahead
From the “five plugins to get you ahead of 99% of Claude users” video.
6. Claude-Mem
Gives Claude memory across sessions. It captures what happens while you work and brings the useful parts back next time.
The catch: Not from Anthropic. The installer offers a hosted memory service that’s free for 30 days; you can skip that sign-in. Don’t use npm install -g claude-mem, that only installs the code library.
7. Superpowers
Makes Claude plan the work first, then test and review it before calling it done. Start here when every new feature turns into a pile of fixes.
Try it: “Use Superpowers to plan a small change to my contact form. Show me the plan first.”
8. Ralph Loop
Keeps Claude working on a task on its own, feeding it the same instructions again each time it tries to stop, until it hits your finish line.
Try it: /ralph-loop "your task" --completion-promise "DONE" --max-iterations 20
The catch: It stops when Claude says an agreed finish phrase or hits your iteration limit, and there is no limit unless you set one. Always add --max-iterations (for example 20) so it can’t run up your usage.
9. GSD (Get Shit Done, now GSD Core)
Fights context rot, which is when Claude’s answers get worse as the conversation fills up. It hands the heavy research, planning and building to fresh helpers so your main session stays clean.
The catch: The original Get Shit Done project has moved. Its new home is GSD Core (“Git. Ship. Done.”). It’s an installer you run once in your terminal, not a /plugin, and it asks which tool you use and where to install.
10. Context7
Looks up the current documentation for the tools you’re using, so Claude stops guessing from old training data.
The catch: It works without an account. A free key from context7.com gives you higher limits if you use it a lot.
Building a website? Add these
From my earlier PLUGINS video about building and checking a website. Superpowers was in that one too, it’s number 7 above. The npx and npm lines go in your terminal, inside your project folder.
11. Find Skills
Tell Claude what you want to do and it searches for a skill that fits, instead of you guessing names.
Try it: “Find a skill for reviewing the accessibility of my booking form. Show me its source before installing it.”
12. Web Design Guidelines
Checks your website files against Vercel’s interface guidance: forms, buttons, accessibility and mobile layout.
13. Impeccable
Gives the design a proper critique: weak hierarchy, generic layouts and the little details that need cleaning up.
14. Playwright CLI
Opens your site in a browser, clicks through it and takes screenshots so Claude can see what it built. It’s evidence, not a verdict: you still look at the result yourself.
Check it worked
Restart or reload
After a /plugin install, Claude Code may ask you to reload plugins or restart. Do what it says.
Look at your list
Type /plugin inside Claude Code to see what’s installed and switch things off.
Run one small test
Use the “try it” line, on a test page or a practice project. A completed install is the start; a working result is what you came for.
Sources checked 27/09/2026: Anthropic’s official plugin marketplace and each tool’s GitHub page linked above. Website tools first checked 14/09/2026.
Ready to go deeper?
Where to go from here.
Wright Mode Membership
Join a community of women entrepreneurs implementing AI and automation in their businesses. Live calls, templates, and ongoing support.
Claude Masterclass
Learn how to use Claude like a pro. From prompting fundamentals to building real workflows that save hours every week.
Claude Code Masterclass
Go beyond the chat interface. Build automations, process data, and create tools with Claude Code — no developer experience needed.