VK
GitHub

Monorepo Support

Vibe Kit automatically detects monorepo structures and intelligently analyzes frontend and backend packages separately.

šŸ“¦ Supported Monorepo Tools

ā€¢ Turborepo
ā€¢ Nx
ā€¢ Lerna
ā€¢ pnpm/yarn/npm workspaces

How It Works

1. Automatic Detection

Vibe Kit scans for monorepo indicators:

  • turbo.json (Turborepo)
  • nx.json (Nx)
  • lerna.json (Lerna)
  • workspaces in package.json
  • packages/ or apps/ directories

2. Package Classification

Each package is automatically classified based on dependencies and structure:

Frontend Indicators

  • React, Vue, Angular dependencies
  • Next.js, Nuxt, Svelte
  • components/ directory

Backend Indicators

  • Express, Fastify, Koa
  • NestJS, Django, Flask
  • server.js, api/ directory

3. Scope Selection

When running vk analyze, you'll be prompted to select:

Frontend

Analyzes React/Vue/Angular packages only

Backend

Analyzes API/server packages only

Both

Generates separate standards for frontend and backend

Usage Examples

Interactive Mode

Vibe Kit will prompt you to select the scope:

vibe-kit analyze

Output: "Which part of the monorepo should we analyze? Frontend (2 packages), Backend (1 package), Both, or Current directory only"

Non-Interactive Mode

Use CLI flags to skip prompts:

vibe-kit analyze --scope frontendvibe-kit analyze --scope backendvibe-kit analyze --scope bothvibe-kit analyze --package apps/admin

Directory Structure

When analyzing both frontend and backend, Vibe Kit generates separate standards:

.vibe-kit/
ā”œā”€ā”€ standards/
ā”‚   ā”œā”€ā”€ frontend/          ā† Frontend-specific standards
ā”‚   ā”‚   ā”œā”€ā”€ code-style.md
ā”‚   ā”‚   ā”œā”€ā”€ testing.md
ā”‚   ā”‚   ā””ā”€ā”€ architecture.md
ā”‚   ā”œā”€ā”€ backend/           ā† Backend-specific standards
ā”‚   ā”‚   ā”œā”€ā”€ code-style.md
ā”‚   ā”‚   ā”œā”€ā”€ testing.md
ā”‚   ā”‚   ā””ā”€ā”€ architecture.md
ā”‚   ā””ā”€ā”€ ...                ā† Shared standards (glossary, etc.)
ā””ā”€ā”€ config.yml             ā† Tracks analysis_scope: "both"

Best Practices

1. Analyze Both Separately

Use --scope both to generate separate standards. This ensures frontend patterns don't mix with backend patterns.

2. Update Config After Analysis

The config.yml file tracks which packages were analyzed, making it easy to re-run analysis later.

3. Share Standards Across Teams

Use vk publish to share your monorepo standards configuration with other teams.

šŸ’” Related Documentation

Enterprise Features ā†’Commands Reference ā†’Project Structure ā†’

Was this helpful?

Help us improve the documentation by sharing your feedback.