DB テーブル追加・変更スキル

To automate Prisma schema changes and database migrations, you can use a workflow that updates the schema, creates and applies migrations, and generates repository artifacts. This ensures backend iterations are synchronized across all layers.

The process for adding a new table in Prisma involves updating the schema.prisma file with proper snake_case mappings and IDs, generating the migration, and scaffolding the domain and repository layers to complete the end-to-end workflow.

Yes, you need an existing Prisma project with a configured schema.prisma file to automate table updates. The automation enforces specific conventions and requires proper project setup before applying schema changes and generating repository code.

Yes, you can generate domain models and repositories when altering database tables. The automation scaffolds these artifacts alongside the Prisma schema updates and migration generation to maintain consistency across the data layer.

The best way to rename fields and update constraints in Prisma is to follow a coordinated sequence: update the schema, create and apply the migration, and regenerate repository artifacts. This prevents errors and ensures all layers reflect the changes.

Automating Prisma migrations reduces errors that occur when manually coordinating schema edits, migrations, and repository scaffolding. It accelerates backend iterations by enforcing a strict sequence for updating schemas and generating domain artifacts.