prisma-cli

To run Prisma migrations in production, use the `migrate deploy` command. This applies pending migration files without resetting data or triggering interactive prompts, ensuring safe schema synchronization for deployment workflows.

While this skill details `migrate dev` for creating and applying migration files during development, `db push` skips migration history to directly sync schema changes. Use `migrate dev` for trackable, repeatable database schema workflows.

To introspect an existing PostgreSQL database, run the `prisma db pull` command. This connects to your datasource and automatically generates or updates your `schema.prisma` file to reflect the current database structure.

Yes, you can manage database records visually by running `prisma studio`. This launches a local web interface allowing you to view, edit, and manage your PostgreSQL data directly without writing raw SQL queries.

Initialize a new Prisma ORM project with PostgreSQL by running `prisma init`. This creates the `schema.prisma` file with a PostgreSQL datasource provider configured, providing the baseline for database management and client generation.

You must run `prisma generate` after schema changes to update the Prisma Client code. This ensures your TypeScript application has type-safe database access matching the latest models, properties, and relations defined in your schema.