Cursor rule

1---
2globs: drizzle/**/*, sql/**/*, packages/core/src/schemas/**/*, packages/core/src/models/**/*
3---
4 
5## Database & Migrations
6 
7- **Role**: Provide a consistent schema and migration history that works in both:
8  - PostgreSQL with pgvector (server mode).
9  - PGlite (browser-only mode).
10 
11### Schema Definition
12 
13- Treat the TypeScript schema in `packages/core/src/schemas` / `models` as the **source of truth**.
14- Ensure any schema change is reflected consistently in:
15  - TS schema/models.
16  - Generated Drizzle migrations under `drizzle/`.
17  - Any raw SQL helpers under `sql/` if present.
18- Prefer Drizzle's typed query APIs over raw SQL to keep Postgres and PGlite behavior aligned.
19 
20### Migrations
21 
22- Use `drizzle-kit` (`pnpm run db:generate`) to generate new migrations; avoid hand-writing large SQL files.
23- For production-safe changes:
24  - Make migrations forward-only and additive when possible.
25  - Avoid destructive operations without a clear, tested migration path.
26- If a generated migration needs manual tweaks:
27  - Keep custom SQL focused and well-commented.
28  - Verify both Postgres and PGlite behavior where applicable.
29 
30### Performance & Indexing
31 
32- For vector search:
33  - Ensure vector dimensions match the configured embedding model.
34  - Use pgvector indexes where needed, and make them explicit in migrations.
35- For analytical queries (stats, charts):
36  - Prefer precalculated or indexed aggregates over complex ad‑hoc joins on hot paths.
37 
38