mralexsaavedra/spotiarr/spotiarr-prisma

Activation Contract

Load when editing Prisma schema, writing repository code, running migrations, or handling DB errors.

Hard Rules

• Prisma calls belong in apps/backend/src/infrastructure/database/ only. Never in domain/ or presentation/.
• Singleton: apps/backend/src/infrastructure/setup/prisma.ts → import from there, never instantiate PrismaClient elsewhere.
• Always validate input with Zod before passing to Prisma. Flow: HTTP request → Zod parse → typed DTO → repository → Prisma.
• Map Prisma errors to application errors — never let raw DB errors reach the presentation layer.
• Use transactions when multiple writes must succeed/fail atomically. Keep transaction scope tight.

Decision Gates

const isPrismaNotFoundError = (e: unknown): e is { code: string } =>
  e instanceof Error && "code" in e && e.code === "P2025";

Execution Steps

After schema changes:

pnpm --filter backend run prisma:generate          # regenerate client
pnpm --filter backend run prisma:migrate:deploy    # apply migrations

References

• Schema: apps/backend/prisma/schema.prisma
• Singleton: apps/backend/src/infrastructure/setup/prisma.ts
• Repository example: apps/backend/src/infrastructure/database/