Hey friends,
I posted a thread this week about Claude plugins, and it reminded me why I explain this stuff in normal language.
I’m non technical too, not an engineer, not a designer.
When a feature sounds like it was named inside a terminal window, I bring it back to one question:
“Can this help me finish the work I keep repeating?”
That’s where Claude Plugins come in.
And if you read until the end, I've got something special to share with you.
📌 What Is A Claude Plugin?
A Claude plugin is a pre-built work kit you install into Claude.
It can bring skills, MCP tools, subagents, hooks, scripts, and setup instructions into one package.
You give Claude the setup upfront instead of teaching it your process from scratch every session.
⚡️ The Plugins I Keep Coming Back To
I’ve been using these three a lot.
You can also use plugins in Codex, so spend time looking through the plugin marketplaces on both Claude and Codex.
Look for work you already repeat: shipping a page, building a video, setting up payments, reviewing a draft.
✅ 1. HyperFrames
HyperFrames turns ideas into video and motion work with HTML, CSS, and JS.
With the right prompt, you can turn a clear idea into a product demo intro, explainer scene, or visual breakdown without starting from a blank editing timeline.
Use it when you know the message, but the visual version still feels annoying to produce.
BTW, this is even better than Remotion. I rate this highly for ANY type of video creation.
Pro tip: give it a full video job, like a product launch video end to end.
✅ 2. Vercel
Vercel helps when you’re building and shipping web projects. It's where 99% of my projects are deployed.
It gives Claude more context around deployment, environment variables, and the parts that slow you down before the page goes live.
The practical win: you can go from “this page works on my machine” to a real preview link you can test, share, and improve.
Pro tip: ask Claude to check the deployment steps before it starts changing files.
✅ 3. Stripe
Stripe matters because payment workflows punish guessing.
If you’re working on checkout, subscriptions, invoices, or webhooks, Claude needs the right Stripe context before it suggests steps.
That means you can build or inspect a payment flow with fewer guesses around checkout logic, test mode, and webhook behaviour.
🛠 Start Using Plugins Today
- Open Claude Desktop
- Click Customize
- Open Plugins
- Click +, then Browse plugins
- Install one and test
You can also build your own plugin.
If you’re using Codex, just click Plugins in the left side bar.
Your tone. Your checklist. Your client process. Package the way you work.
I’m building my own plugin now because I don’t want to re-explain the same setup every time I open a session. I'll share it once it's ready!
🫡 Final Thoughts
Once you see plugins this way, the next move is building your own work setup.
Claude and Codex get more useful when they know how you work, where your tools are, and what a good result looks like.
That’s what I want Build Your Cowork OS to help with.
It’s a cohort where we co-work through the setup together, pick real goals, build the systems around them, and make sure your AI setup helps you move the work forward. To keep it ultra focused, we’re capping it at 10 people with 4 spots left.
If you want help turning your repeated work into something Claude or Codex can help run, you can join the waitlist here:
To less repeating and better systems,
Nahid
