Vibe Coding CLI toolkit for Next.js projects with Subagent configuration and specs generation
npm install @chada007/vibingšµ Vibe Coding CLI Toolkit for Next.js projects with Subagent configuration and specs generation.



``bash`
npm install -g @chada007/vibingor
npx @chada007/vibing init
Initialize a new Vibe Coding project:
`bash`
npx @chada007/vibing init
Answer the interactive prompts to configure your project:
``
? Project name: my-next-app
? Choose tech stack: Next.js (App Router)
? Choose brand preset: Default (Generic)
? Select features: (use arrow keys)
ā User Authentication
ā Internationalization (i18n)
⯠Analytics
After initialization, you'll get:
`
docs/
āāā ui-spec.md # UI design specifications
āāā api-spec.md # API design specifications
āāā permission-spec.md # Permission & RBAC model
āāā domain-spec.md # Domain model specifications
āāā testing-spec.md # Testing guidelines
āāā architecture.md # Architecture overview
.cursorrules # Cursor/Claude AI rules (legacy)
.cursor/rules/ # Cursor AI rules (2025 format)
āāā vibe-coding.mdc
āāā ui-standards.mdc
āāā api-standards.mdc
āāā testing.mdc
prompts/ # Subagent Prompt Templates
āāā infrastructure/ # 5 Infrastructure Agents
āāā module/ # 6 Business Module Agents
āāā bi-ai/ # 5 BI/AI Agents
vibing.config.json # Vibing project configuration
`
`bash`
npx @chada007/vibing init [options]
Options:
- -n, --name - Project name-b, --brand
- - Brand preset: default, artemisium, or path to custom brand-c, --config
- - Load configuration from file--auth
- - Enable authentication feature (default: true)--no-auth
- - Disable authentication feature--i18n
- - Enable internationalization (default: true)--no-i18n
- - Disable internationalization--analytics
- - Enable analytics feature--no-analytics
- - Disable analytics feature (default: true)--poc
- - Enable POC mode (frontend-only with mock data)
Example:
`bash`
npx @chada007/vibing init --name myapp --brand artemisium
npx @chada007/vibing init --name my-poc --poc # POC mode with mock data
`bash`
npx @chada007/vibing add-module
Options:
- -t, --type - Module type: crud (default), readonly, workflow, dashboard-p, --permissions
- - Required permissions--with-tests
- - Include test generation (default: true)--no-tests
- - Skip test generation--mock
- - Force mock data generation for this module-d, --dir
- - Project directory
Example:
`bash`
npx @chada007/vibing add-module Product -t crud -p product.view product.create product.update
npx @chada007/vibing add-module Product --mock # Force mock data for this module
Generated files:
- docs/modules/product-api-spec.mdsrc/domains/Product.ts
- src/app/products/page.tsx
- (List page)src/app/products/[id]/page.tsx
- (Detail page)src/app/products/[id]/edit/page.tsx
- (Form page)src/permissions/product.ts
- tests/product.spec.ts
-
`bash`
npx @chada007/vibing sync-rules [options]
Options:
- -f, --force - Overwrite all files without confirmation
Sync latest Cursor rules and Subagent prompts without reinitializing.
POC (Proof of Concept) Mode enables rapid frontend development without backend infrastructure:
Features:
- Frontend-Only: No backend API or database required
- Mock Data: All data stored in browser localStorage
- Full CRUD: Complete Create, Read, Update, Delete operations
- Instant Setup: Start building immediately without infrastructure setup
- Easy Migration: Seamlessly upgrade to full-stack mode later
Use Cases:
- Rapid prototyping and demos
- Frontend development before backend is ready
- Educational projects
- Proof of concepts and MVPs
Quick Start:
`bash`
npx @chada007/vibing init --name my-poc --poc
cd my-poc
vibing add-module Product # Automatically uses mock data
npm run dev
Generated Mock Files:
- src/data/mock/ - Sample datasrc/lib/mock/
- - Mock service with CRUD operations
All data persists in localStorage across page refreshes. When ready to add a backend, simply update the configuration and regenerate modules.
Vibe Coding is a methodology for organizing AI agent collaboration using clear boundaries and concurrency principles:
- Subagent Separation: Break down complex tasks into specialized agents
- Clear Boundaries: Define what each agent is responsible for
- Maximum Concurrency: Only serialize when modifying the same "source of truth"
- Progressive Evolution: Start with infrastructure, add business modules, then analytics
See Vibe Coding Documentation for details.
After initialization, you'll have Prompt templates for:
Infrastructure Phase:
- Infra Agent - Database, APIs, deployment
- Auth Agent - Authentication & authorization
- API Spec Agent - API contract definitions
- Front Scaffold Agent - Frontend structure
- DevOps Agent - CI/CD, containerization
Module Phase:
- Module Lead Agent - Module architecture
- Domain Agent - Business logic entities
- API Agent - API implementation
- UI Agent - Frontend pages & components
- Permission Agent - Access control
- Test Agent - Quality assurance
BI/AI Phase:
- Data Modeling Agent - Metrics & dimensions
- ETL Agent - Data pipeline
- BI Agent - Dashboards & reports
- AI Prompt Agent - LLM integration
- Eval Agent - Testing & evaluation
- Default: Generic design system (recommended for quick start)
- Artemisium: Artemisium brand design system
Create a brand.json file:
`json`
{
"name": "MyBrand",
"colors": {
"primary": "#3b82f6",
"secondary": "#8b5cf6",
"accent": "#f59e0b",
"success": "#16a34a",
"warning": "#f59e0b",
"error": "#dc2626"
},
"typography": {
"fontFamily": {
"sans": ["Inter", "system-ui", "sans-serif"],
"mono": ["Fira Code", "monospace"]
}
}
}
Then use it:
`bash`
npx @chada/vibing init --brand ./brand.json
After initialization, edit vibing.config.json to customize:
`json`
{
"version": "0.1.0",
"projectName": "my-app",
"brand": "default",
"techStack": "nextjs-app",
"features": {
"auth": true,
"i18n": true,
"analytics": false
},
"modules": []
}
`bashDevelopment
npm run dev # Watch mode compilation
npm run build # Production build
Found a bug? Open an issue on GitHub
This project is available under two licenses:
š Open Source (Apache 2.0) - Free
- Personal projects
- Educational use
- Open-source projects
- Non-profit organizations
š¼ Commercial License - Paid
- Commercial products/services
- SaaS applications
- Enterprise use
- Closed-source projects
See LICENSE for details and COMMERCIAL_LICENSE.md for commercial terms.
Need to use this in a commercial product?
- Purchase: https://vibecodetool.com/pricing
- Trial: https://vibecodetool.com/trial (30 days free)
- Questions: licensing@chada007.dev
Built with Commander.js, Inquirer.js, and EJS.
---
Version: 0.4.0
Status: Alpha (Under Development)
Last Updated: January 17, 2026