How to Make Cursor Respect Domain Boundaries

1# .cursorrules
2
3## Domain Boundaries (DDD)
4### Bounded Contexts
5- Auth domain: src/domains/auth/ — handles authentication, sessions, tokens
6- Orders domain: src/domains/orders/ — handles order lifecycle, cart, checkout
7- Payments domain: src/domains/payments/ — handles payment processing, refunds
8- Users domain: src/domains/users/ — handles user profiles, preferences
9
10### Cross-Domain Rules
11- Domains communicate ONLY through their public API (index.ts exports)
12- NEVER import internal files across domains (no deep imports)
13- Shared types go in src/shared/types/ — not duplicated per domain
14- Events between domains use src/shared/events/ event bus
15- Each domain has its own repository — never query another domain's tables directly

1---
2description: Orders domain boundary rules
3globs: "src/domains/orders/**"
4alwaysApply: false
5---
6
7- This is the Orders bounded context
8- Only import from: src/domains/orders/**, src/shared/**
9- NEVER import from: src/domains/auth/**, src/domains/payments/**, src/domains/users/**
10- Communicate with other domains through the event bus: src/shared/events/
11- Repository: src/domains/orders/repositories/ — only access orders tables
12- Public API: src/domains/orders/index.ts — only these exports are visible to other domains
13- Types: use OrderAggregate, OrderItem, OrderStatus from this domain's types/

1// Prompt to type in Cursor Composer (Cmd+I):
2// @src/domains/orders/ @src/shared/types/
3// Add a cancelOrder function to the OrderService.
4// Requirements:
5// - Only use types and repositories from the orders domain
6// - Emit an OrderCancelled event through the shared event bus
7// - Do NOT import anything from payments or users domains
8// - Update order status to 'cancelled' and record cancellation reason

1// Prompt to type in Cursor Chat (Cmd+L):
2// @src/shared/events/eventBus.ts
3// @src/domains/orders/index.ts @src/domains/payments/index.ts
4// Generate an event flow for order payment:
5// 1. Orders domain publishes OrderCreated event with orderId and totalCents
6// 2. Payments domain subscribes and initiates payment processing
7// 3. Payments domain publishes PaymentCompleted or PaymentFailed event
8// 4. Orders domain subscribes and updates order status
9// Keep all domain internals encapsulated — only use public API exports.