What problem does it solve?
Writing Prisma schemas that work across multiple database schemas is error-prone, and teams often end up with inconsistent naming, wrong field types (especially for money), broken relations, and migrations that don’t match real query patterns.
Core Features & Use Cases
- Multi-schema modeling by default: Defines
schemas in the datasource and applies @@schema("...") to every model/enum to keep domains separated and portable.
- Production-grade conventions: Enforces PascalCase models, camelCase fields, snake_case DB columns via
@map, and consistent timestamp/soft-delete patterns.
- Safe relational and indexing patterns: Supports cross-schema relations, disambiguates same table names with unique model names +
@@map, and recommends indexes based on actual access patterns.
- High-precision decimals for money: Uses
Decimal @db.Decimal(36, 18) to prevent precision loss from Float for financial/crypto values.
Quick Start
Ask: Create a multi-schema Prisma schema for a billing and inventory domain with UUID primary keys, soft deletes, precise Decimal money fields, cross-schema relations, and the needed indexes for common queries.