prisma init & File Anatomy Understand the files before editing them
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. Initialize Prisma Initialization creates the Prisma workspace inside apps/api. It does not create your production architecture, and it does not replace the database you already created in Supabase. PowerShell - initialize Prisma inside apps/api
# From: taskflow\apps\api pnpm exec prisma init
2. What prisma init Creates apps/api/.env
apps/api/prisma.config.tsapps/api/prisma/schema.prisma.env Stores local environment values. It must never be committed with real secrets.
prisma.config.ts Configures Prisma CLI behavior in Prisma 7, including the schema path, migration directory and the connection URL used by CLI commands.
prisma/schema.prisma Defines the database provider, generated client and data models. In Prisma 7, the datasource URL no longer belongs here for this course.
3. Project Structure After Initialization Relevant paths only
apps/api/ |-- .env |-- prisma.config.ts |-- prisma/ | `-- schema.prisma |-- src/ |-- package.json `-- ...
4. Do Not Re-run init as a Fix Once these files exist, errors should be diagnosed in place. Re-running initialization can overwrite assumptions or encourage deleting the evidence you need to debug.
5. Update the Example Environment File apps/api/.env.example
# Runtime application connection (Phase 08 recommends a session-capable pooled URL for local NestJS). DATABASE_URL=
# Prisma CLI / migration connection. Prefer a direct URL when reachable. DIRECT_URL=
# Optional only if migrate dev cannot create an automatic shadow database. # NEVER point this at the same database as DIRECT_URL. SHADOW_DATABASE_URL=
SECRET RULE Real DATABASE_URL, DIRECT_URL and SHADOW_DATABASE_URL values belong only in .env or a secure deployment secret store. They never belong in screenshots, documentation, Git commits or NEXT_PUBLIC_* variables.
Checkpoint • prisma.config.ts exists.
• prisma/schema.prisma exists.
• .env exists locally and is ignored.
• .env.example documents variable names but contains no credentials.
Prisma improves developer ergonomics, but migrations and generated queries still change a real relational database. You should be able to inspect both sides.
Restate the goal of “Prisma Init and File Anatomy” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: domain intent → Prisma Client → generated SQL → PostgreSQL → mapped result. 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.
const tasks = await prisma.task.findMany({
where: { workspaceId },
orderBy: [{ createdAt: "desc" }, { id: "desc" }],
take: 20,
});Do 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.
Verify connection string, host, port, SSL/pooler mode, network reachability, and which environment file the process loaded.
Read the generated SQL before applying it and compare the change against existing production-shaped data.
Without copying the final source, create a second small scenario that applies “Prisma Init and File Anatomy” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Model one entity, create the first migration, and inspect the SQL before applying it.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Using db push as a substitute for migration history in team environments
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.