database-changes

Idempotent SQL migrations use IF NOT EXISTS and IF NOT statements to safely re-run without errors. This Skill generates sequential migration files with these patterns built-in, stored in backend/db/migrations, applied via npm run db:migrate to prevent duplicate object creation and enable safe rollback workflows.

Yes. JSONB columns store flexible, evolving data structures in a single column, eliminating the need for new migrations when your data schema evolves. This Skill generates JSONB column definitions, allowing you to store complex nested data like user preferences while keeping your migration count minimal.

pgvector columns store high-dimensional embeddings for semantic search queries. This Skill generates pgvector column definitions and indexes within your migrations, enabling you to add vector search capabilities to your database without manual SQL or extension setup complications.

After running migrations, update your backend/src/types/index.ts and repository files to reflect schema changes. This Skill generates the migrations and guides you through updating type definitions, ensuring your application code stays consistent with your database structure.

Yes. This Skill generates migrations that alter column types, add indexes, and modify constraints using raw SQL with idempotent patterns. All changes live in version-controlled migration files, making schema evolution auditable and reproducible across environments.

No. This Skill uses a file-based, ORM-free workflow with raw SQL migrations. You get full control over your schema without framework abstractions, direct PostgreSQL syntax, and the ability to use advanced features like JSONB and pgvector natively.