postgres-prisma

Enforce safe Prisma schema design and migration practices for PostgreSQL.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/anicdh/agstack --skill postgres-prisma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgres-prisma
Source: https://github.com/anicdh/agstack/tree/main/.claude/skills/postgres
Command: npx skills add https://github.com/anicdh/agstack --skill postgres-prisma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces safe Prisma schema design and migration practices to prevent faulty migrations and inconsistent data models.

Core Features & Use Cases

  • Enforces explicit relations, required fields, and explicit table mappings to ensure data integrity.
  • Provides a guideline for migration discipline, including naming, backfills, and safety checks.
  • Offers patterns for common Prisma+PostgreSQL tasks like indexing, soft deletes, and safe data migrations.

Quick Start

Review the current api/prisma/schema.prisma and api/prisma/migrations before making changes.

Frequently Asked Questions about postgres-prisma

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to prevent faulty Prisma migrations with PostgreSQL?

To prevent faulty Prisma migrations, enforce safe schema design by using explicit relations, mandatory fields, and explicit table mappings. Disciplined migration rules including proper naming, backfills, and safety checks ensure consistent data models.

How do I design a Prisma schema for data integrity in large teams?

Design a Prisma schema for data integrity by enforcing explicit relations, required fields, and explicit table mappings. These patterns prevent inconsistent data models and ensure safe collaboration across large backend teams.

How to implement soft delete patterns in a Prisma PostgreSQL schema?

Implement soft delete patterns in a Prisma PostgreSQL schema by following disciplined schema design guidelines. This Skill provides specific patterns for indexing, soft deletes, and safe data migrations to maintain data integrity.

Do I need explicit table mappings for PostgreSQL with Prisma?

Yes, explicit table mappings are a core requirement for PostgreSQL with Prisma. Enforcing explicit relations, mandatory fields, and explicit table mappings ensures safe schema design and prevents inconsistent data models.

What are the limitations of Prisma migrations without explicit schema rules?

Without explicit schema rules, Prisma migrations risk faulty executions and inconsistent data models. Limitations arise from missing mandatory fields, implicit relations, and a lack of disciplined migration safety checks and backfills.