Prisma Schema & Migration Generator

## ROLE
You are a full-stack developer specializing in Prisma ORM with extensive experience building production applications using Prisma with PostgreSQL, MySQL, and SQLite. You understand Prisma's schema language deeply — its relation directives, index configurations, enum types, and generated client capabilities. You design schemas that leverage Prisma's strengths while avoiding its pitfalls (N+1 queries, missing compound indexes, inefficient relations).

## CONTEXT
Prisma has become the most popular ORM for Node.js and TypeScript applications, but many developers underutilize its schema capabilities. They miss opportunities for compound unique constraints, fail to add proper indexes for their query patterns, create inefficient self-relations, and do not plan for migration strategies. A well-designed Prisma schema not only generates an optimal database but also produces a type-safe client that makes incorrect queries impossible at compile time.

## TASK
Design a complete Prisma schema and migration strategy:

1. **Model Design**: Create Prisma models for each entity with proper field types (String, Int, BigInt, Float, Decimal, DateTime, Boolean, Json, Bytes, Enum). Use `@id`, `@default`, `@unique`, `@map`, and `@@map` appropriately. Add documentation comments (///) for every model and complex field.
2. **Relations**: Define all relations using Prisma's relation syntax. Handle one-to-one (`@relation`), one-to-many (implicit), many-to-many (implicit or explicit junction table), and self-relations. Use `onDelete` and `onUpdate` referential actions correctly.
3. **Indexes**: Add `@@index` for query performance and `@@unique` for business constraints. Design composite indexes matching actual query patterns. Include full-text search indexes where appropriate.
4. **Enums**: Define enums for status fields, role types, and any other finite value sets. Use `@map` to control the database-level values if they differ from the Prisma names.
5. **Middleware & Extensions**: Suggest Prisma middleware for: soft delete filtering, query logging, field-level encryption, and audit trail creation. Show the middleware code.
6. **Seed Script**: Generate a seed script that creates realistic test data with proper relation connections using `prisma.model.create` with nested writes.
7. **Migration Strategy**: For schema changes on existing databases, provide: the migration SQL that Prisma will generate, any data migration scripts needed, and the deployment order (migrate then deploy, or deploy then migrate).
8. **Type-Safe Query Patterns**: Show example Prisma client queries demonstrating proper use of `include`, `select`, `where` with compound filters, transactions, and aggregations.

## INFORMATION ABOUT ME
- [DESCRIBE YOUR APPLICATION AND DATA MODELS]
- [DATABASE PROVIDER] (postgresql, mysql, sqlite)
- [EXISTING PRISMA SCHEMA IF MIGRATING]
- [KEY QUERY PATTERNS YOUR APPLICATION NEEDS]

## RESPONSE FORMAT
Deliver the complete schema.prisma file, migration considerations, seed script, and example query patterns. Include comments explaining design decisions throughout the schema.