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

API Builder Kit

Stop guessing API design. Ship production-ready REST APIs with zero architectural debt.

TL;DR

Three agents who actually know OpenAPI, OWASP, and rate limiting. Five commands that generate docs you won't hate. One skill that ships APIs day one.

What's Inside

3 Specialist Agents
  • → api-designer - RESTful design patterns, endpoint naming, versioning strategies
  • → api-documenter - OpenAPI 3.1 specs, request/response examples, error schemas
  • → backend-developer - Node.js, Python, Go, Rust. Databases, auth, testing, deployment
2 Automation Commands
  • → /doc-api - Generate OpenAPI specs from code (or code from specs)
  • → /generate-api-documentation - Full API docs: endpoints, schemas, auth flows, examples
1 Production Skill
  • → backend-development - NestJS, FastAPI, Django. OWASP Top 10, JWT, OAuth 2.1, microservices

Copy-Paste Prompts

Real prompts vibe coders use. No fluff. Just results.

Prompt #1 Design a production API
Design a REST API for a SaaS billing system. I need:
- Subscription management (create, update, cancel, reactivate)
- Usage tracking endpoints (POST events, GET aggregated usage)
- Webhook delivery for failed payments
- Multi-tenant isolation by API key

Use RESTful conventions. Include rate limiting strategy. Tell me versioning approach.
Prompt #2 Generate OpenAPI docs
Run /doc-api on my Express routes in src/routes/. Generate OpenAPI 3.1 spec with:
- Request/response schemas for all endpoints
- Auth flows (JWT bearer token)
- Error responses (400, 401, 403, 429, 500)
- Example requests

Output to docs/openapi.yaml
Prompt #3 Secure an existing API
Audit my API against OWASP Top 10 2025:
1. Check for SQL injection risks in query params
2. Verify rate limiting on all public endpoints
3. Review JWT implementation (expiry, refresh, revocation)
4. Scan for sensitive data in logs

Fix what's broken. Tell me what you changed.
Prompt #4 Build a FastAPI endpoint
Create a FastAPI endpoint: POST /api/v1/analytics/events
- Accept batch events (up to 100 per request)
- Validate with Pydantic (event_type, user_id, timestamp, properties)
- Write to PostgreSQL via SQLAlchemy async
- Return 202 Accepted with batch_id
- Add request ID header for tracing

Include tests. Use best practices.
Prompt #5 Document an entire API
Run /generate-api-documentation for my NestJS app. Include:
- All controller endpoints with descriptions
- Authentication (OAuth 2.0 flow diagram)
- Pagination patterns (cursor-based)
- Webhook signature verification
- Rate limit headers

Generate as Markdown. Make it copy-paste ready for developers.

Who This Is For

Perfect If You
  • Ship APIs weekly and hate manual docs
  • Need OWASP compliance but lack security experts
  • Want OpenAPI specs without the YAML hell
  • Build backends in Node, Python, or Go
Skip If You
  • Only build GraphQL APIs
  • Need real-time WebSocket guidance
  • Want frontend API client generation
  • Prefer writing docs by hand

Why Vibe Coders Use This

Zero Security Guesswork

The backend-development skill knows OWASP Top 10 2025. It won't let you ship SQL injection vulnerabilities or missing rate limits. It's like having a security engineer in your terminal.

Docs That Don't Lie

/doc-api generates OpenAPI specs from your actual code. No drift. No stale examples. Your docs update when your routes change.

Production-Ready Day One

api-designer knows versioning strategies. api-documenter knows error schemas. backend-developer knows async patterns. You get production APIs without the trial-and-error phase.

Install in 10 Seconds

npx vibery kit install api-builder

Installs 3 agents, 2 commands, 1 skill. Works with existing projects.

View Full Kit Details

Pair It With