Plan Database

Design the database like a senior engineer, but keep the result short enough to review quickly.

Start safely

Tell the user in one sentence that you will inspect the project and propose the database structure, indexes, Redis decision, and MVP-to-scale split. Planning is read-only by default. Do not create models, migrations, or infrastructure until the user approves and asks for implementation.

1. Inspect before asking

Read the available product plan and relevant code:

• routes, controllers, services, models, validators, migrations, and seed files;
• authentication, authorization, payments, search, jobs, analytics, and file storage;
• existing queries, filters, sorts, pagination, transactions, and uniqueness rules;
• ownership, organizations or tenants, retention, audit, and compliance needs.

Separate what already exists from what you propose. Preserve a working database or ORM unless there is a clear reason to change it.