Vibe Coders' Kit - One command to install anyone's Claude Code setup*

by•
You've spent hours wiring up Claude Code — skills, agents, MCPs, CLAUDE.md. This is the link you send when someone asks how yours works: back up your setup (secrets stripped locally), publish it, and let anyone install your whole stack with one command

Add a comment

Replies

Best
Maker
📌
Hey PH — maker here. Full disclosure up top: this isn't our first launch. We put Vibe Coders' Kit here about six months ago as "a command center to organize your AI toolkit." It got 0 upvotes. And honestly? Fair. Because organizing was never the problem. Nobody wakes up wanting to file their MCP servers into folders — the filesystem already does that, for free. We'd built a tidier drawer for stuff nobody needed a drawer for. So it sat there: 8 signups in six months, none came back, and the only paying customer was me. So we tore it down and rebuilt around the thing people actually do all day. You wire up Claude Code — skills, subagents, MCP servers, a CLAUDE.md you've tuned for weeks — and then someone asks "wait, how is your Claude Code set up?" and there's no good answer. You paste walls of config, screenshot your settings, or just shrug. Vibe Coders' Kit is the link you send instead: - `npx vibecoderskit` scans your ~/.claude and hands you a report card. No signup, runs locally. - `npx vibecoderskit save` backs it up — secrets stripped on your machine before anything leaves it. - `npx vibecoderskit add /setup` installs someone's entire stack on a fresh machine in one line. That's the whole thing. Share your setup, install anyone else's. Private by default, secrets never leave your machine. I'm around all day — tear into it, tell me what's missing, ask me anything. Genuinely curious: whose Claude Code setup would you want to install first?

finally a home for all my scattered MCPs and prompts, the search alone has saved me so much digging

Would love to see a quick share button for individual prompts or MCP configs, basically a way to send a single item to a coworker without exporting the whole library. That alone would make it way more useful for team workflows.

Would love a shareable template feature so I can package up a stack with MCPs and prompts and send the link to a teammate. Right now everything feels locked to my own setup.