Prisma CLI Workflow: Development & Production Use the smallest correct command for each stage
Course rule: Prisma CLI, @prisma/client and @prisma/adapter-pg are locked to 7.9.1. Newer Prisma releases are not substituted halfway through the course.
1. The CLI Commands You Should Actually Remember Command When to use it
pnpm exec prisma version Confirm exact local toolchainpnpm exec prisma validate Check config/schema syntaxpnpm exec prisma generate Regenerate typed clientpnpm exec prisma migrate dev --name ... Create/apply development migrationpnpm exec prisma migrate status Inspect migration statepnpm exec prisma migrate deploy Apply committed migrations in production/stagingpnpm exec prisma studio Inspect/edit data interactively in development2. A Normal Schema Change Loop Edit Validate Migrate Review Generate Build
Change schema.prisma Catch schema/config Generate/apply SQL Read migration.sql Refresh client types Nest production build mistakes
pnpm exec prisma validate
pnpm exec prisma migrate dev --name add_due_date
pnpm exec prisma generate
pnpm run build3. Prisma Studio Studio is a developer inspection tool, not an application admin panel. It is useful for confirming that tables and rows look as expected while learning, but production business operations still belong behind application authorization and audit rules. From: taskflow\apps\api
pnpm exec prisma studio4. db push Has a Different Job db push synchronizes a schema without creating migration history. It can be useful for disposable prototypes, but TaskFlow is a course about production-style development, so migrations remain the default once schema history matters.
DO NOT NORMALIZE DESTRUCTIVE FLAGS Avoid treating --accept-data-loss or reset confirmations as routine. Destructive operations require understanding the target environment and the data being discarded.
5. Build Pipeline Implication Because Prisma 7 generates client code to a project directory, deployments must ensure generate runs before the TypeScript build if generated output is not committed. A later CI/CD phase will make that automated and repeatable.
6. Production Rule Production should receive migration files that were created and reviewed during development. Production is not where you improvise a new migration by running migrate dev.
Checkpoint You should be able to decide which Prisma command to use without searching for a random tutorial each time.
CI turns repository rules into automated gates. A useful pipeline must be understandable, reproducible locally, secure, and able to fail for the right reasons.
Restate the goal of “Prisma CLI Workflow Development and Production” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: git event → runner → install → quality gates → artifact/deploy decision. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Prisma schema + migration history + generated client + NestJS PrismaService connected to TaskFlow PostgreSQL.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
name: CI
on: [pull_request]
jobs:
verify:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: corepack enable
- run: pnpm install --frozen-lockfile
- run: pnpm lint && pnpm typecheck && pnpm test && pnpm buildDo not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Compare Node/pnpm versions, lockfile state, environment variables, OS assumptions, and generated artifacts.
Set least-privilege permissions at workflow/job level and isolate untrusted pull-request code from secrets.
Without copying the final source, create a second small scenario that applies “Prisma CLI Workflow Development and Production” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Initialize Prisma with the intended generated-client output and PostgreSQL configuration.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Creating a new PrismaClient per request
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.