# Vibes Monorepo Cursor Rules

## Project Overview
This is a Vibes monorepo using vertical slice architecture. Features are self-contained units with UI, API, logic, and data layers.

## Architecture
- **Vertical Slices**: Each feature contains all layers
- **No Cross-Feature Imports**: Features are independent
- **Minimal Shared Code**: Only truly generic utilities

## File Structure
```
features/[feature]/
├── ui/        # Components and screens
├── api/       # Routes and handlers
├── logic/     # Services and business logic
├── data/      # Models and types
└── tests/     # Feature tests
```

## Code Patterns
- Use TypeScript for all code
- Export through index.ts files
- Follow REST conventions for APIs
- Use React functional components
- Services use dependency injection

## Common Tasks
1. Create feature: `vibe create [name]`
2. Add component: Create in `ui/components/`
3. Add API: Create in `api/routes/`
4. Add service: Create in `logic/services/`

## AI Guidelines
- Look for AI- prefixed comments
- Check `.ai-metadata.json` in features
- Follow patterns in existing code
- Keep changes within feature boundaries

## Best Practices
- Don't import between features
- Use consistent naming
- Add meaningful comments
- Update barrel exports
- Write tests for new code