12 pluggable feature modules — 9 template-based (instant) and 3 Claude-powered (AI-generated).
All features are idempotent and stack-aware. They detect your project's stack (Next.js, Go, Python, Node.js) and generate appropriate files. Running a feature twice skips it unless you pass --force.
These features render from EJS templates instantly, with no API key required.
vibe add docker
Generates a stack-aware Dockerfile and docker-compose.yml.
Files created: Dockerfile, docker-compose.yml, .dockerignore
vibe add ci
Generates a GitHub Actions CI pipeline that runs on push to main and pull requests.
Files created: .github/workflows/ci.yml
vibe add testing
Sets up a test framework with a sample test file.
_test.go fileFiles created: vitest.config.ts (or equivalent), __tests__/sample.test.ts
vibe add logging
Adds structured logging to your project.
src/lib/logger.ts modulelogger.py moduleFiles created: src/lib/logger.ts (or equivalent for your stack)
vibe add validation
Adds environment variable validation so your app fails fast on misconfiguration.
process.env at startupBaseSettings modelFiles created: src/lib/env.ts (or equivalent)
vibe add health
Adds a /api/health endpoint that returns service status, useful for load balancers and monitoring.
src/app/api/health/route.tsFiles created: src/app/api/health/route.ts (or equivalent), plus a health check test
vibe add hooks
Sets up git hooks for code quality enforcement on every commit.
Files created: .husky/pre-commit, .husky/commit-msg, commitlint.config.js
vibe add auth
Provides authentication setup guidance and starter files for your stack. Includes middleware patterns, session handling recommendations, and integration points.
vibe add db
Sets up Prisma ORM with a base schema and database client.
Files created: prisma/schema.prisma, src/lib/db.ts
These features use Claude CLI to generate custom code based on your arguments. They require the Claude CLI to be installed.
vibe add api users
vibe add api products
vibe add api orders
Generates a complete REST API endpoint with CRUD operations and a corresponding test file. Claude generates the implementation based on your entity name and detected stack.
Files created: API route file + test file (paths depend on your framework)
vibe add component Card
vibe add component UserProfile
vibe add component DataTable
Generates a React component with TypeScript props interface, styling, and a test file.
Files created: Component file + test file
vibe add model Order
vibe add model Product
vibe add model User
Generates a Prisma model definition with appropriate fields, relations, and a migration.
Files created: Updated prisma/schema.prisma + migration file
New in v0.6.1 — vibe-init integrates with the Agile Vibe Coding framework for traceable, accountable AI-assisted development.
npm install -g @agile-vibe-coding/avc
cd your-project
vibe avc
AVC provides structured agile ceremonies adapted for AI-assisted coding:
Every epic, story, and task links back to a requirement — making governance auditable end-to-end. Combined with vibe-init's 59 governance policies, this creates a complete traceability chain from business requirement to deployed code.
Manifesto Principle III — Traceable Intent: Every feature and generated code must link back to a requirement or decision. Without traceability, you can't audit, you can't maintain, and you can't scale.
vibe-init wires up two complementary knowledge graph engines so Claude navigates by structure instead of grepping through every file:
vibe codegraph init -i # builds a local SQLite knowledge graph
vibe codegraph status # health check
vibe codegraph query UserService
Code-only. Auto-installed via npm install -g @colbymchenry/codegraph on first run. vibe init writes a marker-fenced ## CodeGraph block in CLAUDE.md, a .claude/commands/codegraph.md skill, and pre-allows mcp__codegraph__* permissions in .claude/settings.json.
vibe graphify . # build the graph
vibe graphify install # always-on hooks
vibe graphify query "show the auth flow"
vibe graphify path NodeA NodeB
vibe graphify explain UserService
vibe graphify stats
Cross-modal — code, docs, papers, images, audio, and video. Auto-installed via uv tool install graphifyy (or pipx / pip) on first run. vibe init writes a marker-fenced ## Graphify block in CLAUDE.md and a .claude/commands/graphify.md skill that teaches Claude when to consult the graph.
Every Graphify edge is tagged EXTRACTED, INFERRED, or AMBIGUOUS so the AI cites the confidence level instead of presenting guesses as facts. The two engines are complementary — use Graphify for orientation and cross-modal questions, CodeGraph for callers/callees/impact.
Each feature module includes a detect() method that checks whether the feature is already present in your project. This is used by:
vibe add — to skip already-installed features (unless --force)vibe scan — to report which practices are present/missingvibe doctor — to score health checksDetection is pure filesystem analysis — it checks for config files, directory structures, and package.json entries without making any external calls.