Database Management

Manage PostgreSQL schema evolution with Prisma migrations and seed scripts for the SEProjeect VLEAGUE project.

1|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/daithang-organization/SE104_VLEAGUE --skill database-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Database Management
Source: https://github.com/daithang-organization/SE104_VLEAGUE/tree/main/.agent/skills/database-management
Command: npx skills add https://github.com/daithang-organization/SE104_VLEAGUE --skill database-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured guide for managing a PostgreSQL database for the SE104_VLEAGUE project using Prisma migrations, seeding, and schema evolution, ensuring reliable schema changes and data consistency.

Core Features & Use Cases

  • Schema evolution workflow: Safely evolve Prisma schemas with versioned migrations and updated models.
  • Migration & seeding operations: Create and apply migrations, seed initial data, and maintain a reproducible database state across environments.
  • Use Case: When advancing project features that require database changes (adding tables, fields, or relationships), this skill guides you through applying migrations and seeds without data loss.

Quick Start

Run the Prisma migration workflow after changing the Prisma schema to apply new migrations and seed data for local development.

Frequently Asked Questions about Database Management

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

FAQPage Schema
How do I apply Prisma migrations and seed data without losing existing PostgreSQL records?

To apply Prisma migrations safely, you evolve the schema with versioned migrations and execute seed scripts to maintain a reproducible database state without data loss.

What is the best way to manage PostgreSQL schema evolution for a growing project?

Managing PostgreSQL schema evolution involves tracking Prisma schema changes with versioned migrations, ensuring a trackable history of modifications across development and production environments.

How does Prisma seeding maintain a reproducible database state across environments?

Prisma seeding maintains a reproducible database state by applying scripted initial data after migrations, ensuring consistent baseline data across local development and production workflows.

Can I use this Prisma migration workflow for both development and production deployments?

Yes, this Prisma migration workflow applies to both development and production environments, enforcing best practices for schema location, migration workflows, and safe deployment practices.

Why do my Prisma schema changes fail to sync with my PostgreSQL database?

Prisma schema changes fail to sync when best practices for schema location and migration workflows are not followed, requiring versioned migrations to track and apply changes safely.

Do I need to version my Prisma migrations for a PostgreSQL-backed application?

Yes, versioning Prisma migrations is required to ensure a trackable history of schema changes, enabling safe database lifecycle management and reproducible deployments for PostgreSQL.