prisma-conventions

Enforce Prisma schema conventions for IDs, timestamps, and migration naming.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/feraudet/ssii --skill prisma-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prisma-conventions
Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/prisma-conventions
Command: npx skills add https://github.com/feraudet/ssii --skill prisma-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prisma conventions mitigate drift by standardizing schema design, migrations, and client usage across projects, ensuring consistent data access patterns.

Core Features & Use Cases

  • Enforce UUID IDs, automatic timestamps, and safe nullable fields in Prisma models.
  • Standardize migration naming and index strategy for reliability and performance.
  • Provide concrete examples of queries, transactions, and seed data to promote best practices.

Quick Start

Apply the repository's Prisma conventions to your schema and migrations to ensure consistency and reliability.

Frequently Asked Questions about prisma-conventions

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

FAQPage Schema
What are the best conventions for structuring Prisma models in TypeScript?

Standard Prisma conventions enforce UUID IDs, automatic timestamps, and safe nullable fields in your TypeScript models to standardize schema design and prevent data drift across backend projects.

How do I standardize Prisma migration naming and index strategy?

To standardize Prisma migrations, apply explicit naming conventions and standardized index strategies to your schema, ensuring consistent schema design and reliable data access patterns across your projects.

Can I use Prisma conventions to enforce UUID IDs and automatic timestamps?

Yes, Prisma conventions specifically enforce UUID IDs and automatic timestamps within your data models, mitigating drift by standardizing schema design and backend data access patterns reliably across projects.

What's the best way to write Prisma queries, transactions, and seed data?

The best way to write Prisma queries, transactions, and seed data is by following documented conventions that provide concrete examples, promoting consistent and reliable backend data access patterns across projects.

Why does Prisma schema drift happen and how do I prevent it?

Prisma schema drift happens due to inconsistent model design, migrations, and client usage; you prevent it by standardizing schema conventions, migration naming, and index strategies across all backend projects.

Do I need TypeScript to use these Prisma schema and migration conventions?

TypeScript is highly recommended as these Prisma conventions target TypeScript backend environments, standardizing data models, relations, indexes, seed data, and Prisma client usage across your projects.