Skip to main content
VibeKit is specifically optimized for VibeCoding and LLM-driven development, which requires extensive configuration files to guide AI agents through complex workflows. The .rulesync directory serves as the source of truth for all LLM configuration files, managing the sophisticated rule system that powers AI-assisted development.

​
.rulesync Configuration

The .rulesync directory serves as the source of truth for all LLM configuration files. This system allows you to manage rules, commands, and subagents in a centralized location and automatically generate them for different AI tools: 
.rulesync/
├── commands/           # High-level command structures
├── subagents/          # Persona-driven specialized agents
└── rules/              # Workspace-wide guidelines and best practices
Key Benefits:
  • Single Source of Truth: All LLM configurations managed in one place
  • Automatic Generation: Run pnpm sync:rules to generate files for Claude, Cursor, and other tools
  • Version Control: Track changes to AI configurations alongside code changes
  • Consistency: Ensure all AI tools follow the same guidelines and workflows
To generate all LLM configuration files, run the following command: 
pnpm sync:rules

# Files are automatically generated to:
# - .claude/ (for Claude Code)
# - .cursor/ (for Cursor IDE)

​
Claude

For Claude models, prompt engineering is handled through a set of dedicated files in the .claude/ directory. These files include detailed instructions, examples, and best practices to guide LLMs in generating accurate and efficient code:
  • agents/: Contains prompts for persona-driven agents that specialize in tasks like Test-Driven Development, documentation, and feature writing.
  • commands/: Includes prompts that define high-level command structures for planning, execution, and version control.
  • hooks/: Provides scripts that can be triggered at different stages of the development lifecycle, such as pre-task and post-task actions.
Additionally, CLAUDE.md provides comprehensive guidance for Claude Code when working with the Vibekit codebase, including architecture overview, development standards, and code quality guidelines.

​
Cursor

Cursor rules files are located in the .cursor/rules directory. These files define best practices, workflows, and workspace conventions for building and maintaining agents:
  • createVibekitAgent.mdc: A guide for creating and configuring new agents, including best practices, required dependencies, and setup instructions.
  • vibeCodingWorkflow.mdc: Outlines the step-by-step development workflow for agents, including the Planner/Executor roles, task breakdowns, and conventions for collaborative development.
  • workspaceRules.mdc: Documents workspace-wide guidelines and best practices for the monorepo, such as dependency management, development scripts, and CI/CD standards.
⌘I