[ ] Compiling...
[ ] Bundling...
[ ] Ready
Vibery Kits

Building Vibery Kits: 341 Templates, 1 Command

Why curation beats collection. An honest look at building a template ecosystem for Claude Code.

TL;DR

Built a CLI + website for Claude Code templates. 341 templates curated from MIT-licensed repos. 12 Smart Stacks researched against real data. $0 spent. Phase 1 done, shipping in public.

The Problem

Three weeks ago, I had a problem: Claude Code is incredible, but finding the right agents, commands, and MCPs felt like hunting through a dozen GitHub repos. Every. Single. Time.

So I built Vibery Kits. A curated template ecosystem that gets you from "I want to build a Next.js app" to a production-ready development environment in one command.

npx vibery install nextjs-production

Done. No API calls. No signup. Just templates that work.

What Actually Got Built

The CLI

  • Offline-first installation tool
  • 341+ templates: 192 agents, 37 skills, 35 commands, 24 MCPs, 19 hooks, 8 settings
  • Smart filtering: vibery install --agent, vibery search "docker"
  • Zero external dependencies for core functionality

The Website

  • Astro 5 static site with Vue Islands (interactive parts only)
  • 12 curated Smart Stacks (Next.js, Security, DevOps, etc.)
  • "Warm Terminal" design system (stone/terracotta palette)
  • Deployed on Cloudflare Pages

The Curation

  • Every stack researched against real sources: Stack Overflow 2025, OWASP Top 10 2025
  • Templates from MIT-licensed repos (all credited)
  • Quality bar: Does this solve a real problem? Does it work with other templates?

Why Curation Beats Collection

Here's the thing: GitHub is full of "awesome" lists. Random dumps of links. Zero guidance.

I didn't want that.

When you install the Next.js Production Stack, you get:

  • nextjs-architecture-expert agent (routing, server components, best practices)
  • optimize-bundle-size command (finds bloat, suggests fixes)
  • vercel-deploy command (production deployment checks)
  • Settings optimized for Next.js projects

Not random templates. A tested combination that works together. That's the difference between collection and curation.

The Tech Choices (And Why)

Astro 5 over Next.js

Template catalog is static content. Why hydrate React for text? Vue Islands for cart, modal, search only. Result: 0KB JS on homepage.

MiniSearch over Fuse.js

4KB smaller. Faster indexing for 341 templates. Same quality search.

No External API

CLI works offline. No rate limits, no downtime. Templates install in <1 second.

Cloudflare Pages

Static hosting is free. Edge functions for future features. Deploy previews on every push.

None of this is fancy. It's just choosing boring technology that works.

The Honest Parts Nobody Tweets About

Phase 1 is done.

The CLI installs templates. The website structure exists. The design system is implemented.

Still building:

  • Vue Islands migration (setup done, components in progress)
  • Wizard UI for outcome-based discovery
  • Stack installation via CLI (single templates work, bundles next)

Templates aren't original.

Every single one is curated from MIT-licensed community repos. I didn't write 341 templates from scratch. I found the best ones, tested combinations, documented what works together, and credited every source.

That's the value. Research, testing, curation.

What I Learned Building This

1. Offline-first is underrated

Every SaaS tutorial teaches you to build API-dependent tools. But a CLI that works without internet? That hits different. No auth flow. No rate limits. Just files.

2. Curation is a product

People don't want more options. They want the right option. The Next.js Stack isn't valuable because it has 8 templates. It's valuable because I spent 6 hours researching which 8 to include.

3. Design for paying users early

I picked "Warm Terminal" specifically for professional developers who'd pay for premium stacks. Not flashy neon (free tier vibe). Refined stone/terracotta (professional, trustworthy).

4. Credits build trust

Every template has a source. Every stack has research credits. Being transparent about curation > pretending you built everything from scratch.

5. Static-first scales

Mostly static Astro pages. Vue Islands only for interactive parts. Result? Can handle 100K visitors on Cloudflare's free tier. No database, no backend, no scaling problems.

6. Ship Phase 1 before Phase 4

I could've waited until every feature was polished. But Phase 1 works: CLI installs templates. That's the core value. Ship it. Improve in public.

The Numbers

341
templates curated
12
Smart Stacks
6+
source repos
~2,500
lines of code
3 weeks
to foundation
$0
spent

Try It

# Install a single template

npx vibery install prompt-engineer

# Search templates

npx vibery search "nextjs"

# List all agents

npx vibery list --type agents

Building in Public

If you're building with Claude Code and tired of hunting through random repos, this is for you.

Browse Templates View Smart Stacks

Templates curated from MIT-licensed community repos. All sources credited.