Engineering skills, current docs, a map of your codebase, real UI components and a security test. What each one does, why it matters and the install command from its own README.
The difference between a junior and a senior developer is rarely typing speed. Seniors write the spec before the code, check the docs for the version they're actually on, know where things live in the codebase and think about how it could be broken before it ships.
Claude Code on its own skips most of that. It'll happily write code for an older version of a library, reread the same files every session and jump straight to building. It can write the code. It just doesn't have the habits yet and that's what these five add.
Each one adds a single habit: a process, fresh docs, memory of your codebase, a component library and a security check. Install one, use it for a week, then add the next.
Not all five are plugins in the strict sense. Agent Skills and 21st install through Claude Code's plugin marketplace. Context7, Graphify and Strix install as a command-line tool plus a skill or an MCP server. They all end up in the same place: Claude Code can use them without you copying anything in by hand. Every command here was checked against the project's own README on 1 November 2026.
The 5 plugins
Agent Skills by Addy Osmani: "Production-grade engineering skills for AI coding agents." It adds slash commands that follow the way software actually gets built: /spec, /plan, /build, /test, /review and /ship. Skills also switch on by themselves, so designing an API pulls in the API design skill.
/agent-skills:review./plugin marketplace add addyosmani/agent-skills /plugin install agent-skills@addy-agent-skills
Context7 by Upstash: "Up-to-date docs for AI agents." It pulls current code examples and documentation for the library you're using straight into Claude's context, so it stops calling APIs that don't exist any more. Add "use context7" to your prompt.
npx ctx7 setup --claude
Graphify turns your codebase, with its docs, SQL schemas, configs and PDFs, into a knowledge graph Claude can query. Type /graphify . in Claude Code to build it.
graphifyy, with two y's.uv tool install graphifyy # or: pipx install graphifyy graphify install graphify claude install # run inside your project
21st.dev Magic MCP, now the 21st MCP: "It's like v0, but in your Cursor / Claude Code / Windsurf." Claude can search a library of 10,000+ real React and Tailwind components and generate new UI from your editor.
npx @21st-dev/cli@latest init --client claude
Strix is open-source AI penetration testing. Its AI agents run your app and validate what they find with working proofs of concept, so each issue comes with evidence that it's real. A senior developer asks how something could be broken before it goes live. Strix asks that question for you, on a local folder, a GitHub repo or a live URL.
npx skills add usestrix/strix.curl -sSL https://strix.ai/install | bash export STRIX_LLM="your-provider/your-model" export LLM_API_KEY="your-api-key" strix --target ./app-directory
github.com/usestrix/strix · strix.ai
Strix actively attacks whatever you point it at. Only run it against apps you own or have written permission to test. Testing someone else's site without permission is illegal in most countries.
Claude already knows how to code. These teach it how to work.
Edit Your Videos with Claude Code · Opus 5.5: describe the edit in plain English and Claude Code writes the Remotion code that builds it.
The Storyboard-First Edit: the framework to paste into Claude Code to trim a raw take, set a look and approve real frames before anything renders.
What this guide won't do: these tools don't replace reviewing what Claude writes. Context7 and 21st need an API key and Strix needs Docker plus your own LLM API key. Star counts and install commands were checked on 1 November 2026 on each project's GitHub page and may change, so if a command fails, check the project's README.
The Audacity to Build is my community for people doing exactly that. It is opening soon. Join the waitlist and you are first in when it does.
If this was useful, follow me. I share what I am actually building, the tools that survive my own testing, and the ones I quietly cancel. New plays every week.
Pop in your name and email and the guide is yours, along with the occasional new guide when I publish one. No spam, ever.