prisma

Enforce Prisma schema conventions and guide safe database migrations.

Updated Aug 23, 2026

Search Tags:#database #backend #schema #migration #orm #prisma

Ready to run

npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill prisma-reeinharddd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prisma
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/prisma
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill prisma-reeinharddd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures database schema integrity and migration safety by enforcing conventions and providing clear commands for managing Prisma schemas and migrations.

Core Features & Use Cases

Schema Conventions: Enforces naming conventions for models and fields, and ensures required fields like id, createdAt, and updatedAt are present.
Migration Management: Guides users on creating descriptive migration names, avoiding edits to existing migration files, and reviewing dangerous changes.
Use Case: When a developer needs to add a new field to the Product model, they can use this Skill to ensure the schema adheres to standards and generate a new migration safely.

Quick Start

Use the prisma skill to create a new migration named 'add_product_description'.

Frequently Asked Questions about prisma

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

FAQPage Schema

How do I enforce naming conventions and required fields in a Prisma schema?▼

To enforce Prisma schema conventions, you can use this Skill to check model and field naming rules, ensuring mandatory fields like `id`, `createdAt`, and `updatedAt` are present. It validates schema integrity automatically before migrations.

What is the safest way to create a database migration in a Prisma project?▼

The safest way to create a database migration is to use descriptive names, avoid editing existing migration files, and review dangerous changes. This Skill guides you through generating safe schema evolution steps deterministically.

How do I add a new field to an existing Prisma model without breaking the database?▼

Adding a new field to a Prisma model requires schema validation and a new migration. This Skill ensures your updated schema adheres to required field standards and safely generates the corresponding migration file.

Why should I avoid editing already applied Prisma migration files?▼

Editing applied Prisma migration files breaks database schema integrity and migration history. This Skill prevents unsafe modifications by guiding you to create new, descriptive migration files for every schema evolution instead.

Can I use this Skill to manage schema migrations for any backend database ORM?▼

This Skill specifically manages schema integrity and migration safety for Prisma ORM projects. It enforces Prisma-specific naming conventions and field requirements, so it is not intended for other backend database ORMs.

What Prisma schema standards are checked before applying a new migration?▼

Before applying a Prisma migration, this Skill checks model and field naming conventions and ensures mandatory fields like `id`, `createdAt`, and `updatedAt` are present, maintaining strict schema integrity and deterministic task execution.