database-designer

To design a relational database schema from a PRD, feed your architecture notes or product requirements into the tool to generate entities, relationships, constraints, and a clear migration plan.

The best way to generate reversible database migrations is using ERD-driven modeling that tracks schema evolution, applies normalization rules, and recommends performance-oriented indexes for foreign keys.

Yes, this approach supports ORM-agnostic database modeling by focusing on pure relational schema design, normalization, and ERD structures rather than tying you to a specific framework.

To structure database indexes for frequent query patterns, analyze your schema's foreign keys and query loads, then apply performance best practices to recommend optimal indexing strategies.

You need an ERD for database schema design when starting a project requiring persistent data models, PRD-driven architectures, or when you must map complex business data into normalized relational tables.

Yes, you can use this for an existing database schema migration plan by evaluating current tables and relations to generate reversible migrations and track ongoing schema evolution.