**TL;DR** - Describe your data, get a schema. Skip the drawing tools.
1. Describe your data model in plain English
2. Review the generated schema and adjust constraints
3. Export migration files for your ORM
**Example Prompt:**
Design a schema for a multi-tenant SaaS with users, orgs, subscriptions, and audit logs.
| Pros | Cons |
|---|---|
| Speeds up initial schema design | Generated schemas need review by someone who knows access patterns |
| Catches common anti-patterns before production | Doesn't know your specific performance requirements |
|---|
| Migration output is immediately usable | The "right" schema is often workload-dependent |
|---|