How do I install the Backend Prisma Database skill?

Run npx skillmds@latest add xmuhameed/backend-prisma-database in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Backend Prisma Database safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Backend Prisma Database?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Backend Prisma Database free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Backend Prisma Database?

xmuhameed (@xmuhameed) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Backend Prisma Database by xmuhameed

Name: Backend Prisma Database
Author: xmuhameed

Backend Prisma Database

Prisma schema conventions, migrations, soft-delete extensions, BaseService delete pattern, bilingual fields, and PostgreSQL sequence reset. Use when creating Prisma models, migrations, database queries, or soft-delete logic.

xmuhameed Updated Sep 21, 2026

File contents

Prisma & Database

New Apps (Prisma 8)

npm install prisma@latest @prisma/orm-postgres

prisma.config.ts with defineConfig
npx prisma migrate dev --name description
Node.js 22.18+

Model Conventions

model category {
  id        String    @id @default(uuid())   # UUID for catalog
  name_en   String                          # bilingual
  name_ar   String
  slug      String    @unique
  deleted   DateTime?                       # soft delete
  sort      Int       @default(0)
  createdAt DateTime  @default(now())
  updatedAt DateTime  @updatedAt
  @@index([deleted])
}

ID type	Use for
UUID `@default(uuid())`	Catalog entities (category, product, user)
Int `@id @default(autoincrement())`	Orders, junction tables, logs

Soft Delete

PrismaService uses Client Extensions — auto-injects where: { deleted: null } on findMany/count/findFirst.

Setting deleted: new Date() = soft delete.

Delete Pattern

// First delete → soft
await prisma.feature.update({ where: { id }, data: { deleted: new Date() } });

// Second delete on same record → hard + cleanup relations
await prisma.junction.deleteMany({ where: { featureId: id } });
await prisma.feature.delete({ where: { id } });

Or extend BaseService → handleDelete(model, id) handles soft→hard + sequence reset.

Search

where.OR = [
  { name_en: { contains: search, mode: 'insensitive' } },
  { name_ar: { contains: search, mode: 'insensitive' } },
];

Relations

// Connect on create
type: { connect: { id: dto.typeId } }

// Include on read
include: { type: true, ProductCategory: true }

Migrations

New apps: prisma migrate dev only.

Legacy: manual SQL in prisma/migrations/*.sql + edit schema.

Sequence Reset

After hard delete on autoincrement tables: SequenceResetService or POST /maintenance/reset-sequences.

Seed

prisma/seed.ts — npx prisma db seed

---name: backend-prisma-databasedescription: Prisma schema conventions, migrations, soft-delete extensions, BaseService delete pattern, bilingual fields, and PostgreSQL sequence reset. Use when creating Prisma models, migrations, database queries, or soft-delete logic.---# Prisma & Database## New Apps (Prisma 8)```bashnpm install prisma@latest @prisma/orm-postgres```- `prisma.config.ts` with `defineConfig`- `npx prisma migrate dev --name description`- Node.js 22.18+## Model Conventions```prismamodel category { id String @id @default(uuid()) # UUID for catalog name_en String # bilingual name_ar String slug String @unique deleted DateTime? # soft delete sort Int @default(0) createdAt DateTime @default(now()) updatedAt DateTime @updatedAt @@index([deleted])}```| ID type | Use for ||---------|---------|| UUID `@default(uuid())` | Catalog entities (category, product, user) || Int `@id @default(autoincrement())` | Orders, junction tables, logs |## Soft Delete`PrismaService` uses Client Extensions — auto-injects `where: { deleted: null }` on findMany/count/findFirst.Setting `deleted: new Date()` = soft delete.## Delete Pattern```typescript// First delete → softawait prisma.feature.update({ where: { id }, data: { deleted: new Date() } });// Second delete on same record → hard + cleanup relationsawait prisma.junction.deleteMany({ where: { featureId: id } });await prisma.feature.delete({ where: { id } });```Or extend `BaseService` → `handleDelete(model, id)` handles soft→hard + sequence reset.## Search```typescriptwhere.OR = [ { name_en: { contains: search, mode: 'insensitive' } }, { name_ar: { contains: search, mode: 'insensitive' } },];```## Relations```typescript// Connect on createtype: { connect: { id: dto.typeId } }// Include on readinclude: { type: true, ProductCategory: true }```## Migrations**New apps:** `prisma migrate dev` only.**Legacy:** manual SQL in `prisma/migrations/*.sql` + edit schema.## Sequence ResetAfter hard delete on autoincrement tables: `SequenceResetService` or `POST /maintenance/reset-sequences`.## Seed`prisma/seed.ts` — `npx prisma db seed`

Frequently asked questions