@chada007/vibing

🎵 Vibe Coding CLI Toolkit for Next.js projects with Subagent configuration and specs generation.

🚀 Quick Start

Installation

npm install -g @chada007/vibing
# or
npx @chada007/vibing init

Basic Usage

Initialize a new Vibe Coding project:

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

Generated Files

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

📦 Commands

init - Project Initialization

npx @chada007/vibing init [options]

Options:

• -n, --name <name> - Project name
• -b, --brand <brand> - Brand preset: default, artemisium, or path to custom brand
• -c, --config <path> - 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:

npx @chada007/vibing init --name myapp --brand artemisium
npx @chada007/vibing init --name my-poc --poc  # POC mode with mock data

add-module - Add Business Module

npx @chada007/vibing add-module <name> [options]

Options:

• -t, --type <type> - Module type: crud (default), readonly, workflow, dashboard
• -p, --permissions <perms...> - Required permissions
• --with-tests - Include test generation (default: true)
• --no-tests - Skip test generation
• --mock - Force mock data generation for this module
• -d, --dir <dir> - Project directory

Example:

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.md
• src/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

sync-rules - Update AI Rules

npx @chada007/vibing sync-rules [options]

Options:

• -f, --force - Overwrite all files without confirmation

Sync latest Cursor rules and Subagent prompts without reinitializing.

🚀 POC Mode

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:

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/<module>.json - Sample data
• src/lib/mock/<module>-mock.ts - 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.

🎯 Core Concepts

Vibe Coding

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.

Subagent Roles

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

🎨 Brand Presets

Built-in Brands

• Default: Generic design system (recommended for quick start)
• Artemisium: Artemisium brand design system

Custom Brands

Create a brand.json file:

{
  "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:

npx @chada/vibing init --brand ./brand.json

📋 Configuration

After initialization, edit vibing.config.json to customize:

{
  "version": "0.1.0",
  "projectName": "my-app",
  "brand": "default",
  "techStack": "nextjs-app",
  "features": {
    "auth": true,
    "i18n": true,
    "analytics": false
  },
  "modules": []
}

🧙 Development Scripts

# Development
npm run dev          # Watch mode compilation
npm run build        # Production build

# Testing
npm run test         # Run tests
npm run test:watch   # Watch mode testing
npm run test:ui      # Test UI dashboard
npm run test:coverage # Coverage report

# Code Quality
npm run lint         # Check code style
npm run format       # Auto-format code
npm run type-check   # TypeScript type checking

# Publishing
npm run prepublishOnly # Pre-publish checks

📚 Documentation

Core Guides

• Vibe Coding Methodology
• API Specifications
• Contributing Guide

Feature Guides

• POC Mode Complete Guide - Frontend-only development with mock data
• Claude Skills Usage Guide - Enhance your project with Claude Code skills
• Spec-Kit Integration Guide - Combine requirements with technical specs

🐛 Reporting Issues

Found a bug? Open an issue on GitHub

📄 License

Dual License Model

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.

Get a Commercial License

Need to use this in a commercial product?

• Purchase: https://vibecodetool.com/pricing
• Trial: https://vibecodetool.com/trial (30 days free)
• Questions: [email protected]

🙏 Acknowledgments

Built with Commander.js, Inquirer.js, and EJS.

Version: 0.4.0 Status: Alpha (Under Development) Last Updated: January 17, 2026