What problem does it solve? It enforces consistent, tenant-safe, and migration-disciplined EF Core data access in a .NET solution, preventing common mistakes like leaking IQueryable from repositories, disabling tenant filters accidentally, or hand-editing generated migrations. ## Core Features & Use Cases - Persistence Rules: Repositories return entities (never DTOs or IQueryable), read-only paths use AsNoTracking, and named SoftDelete/Tenant query filters stay enabled by default. - Migration Discipline: Covers dotnet ef commands for creating, scripting, removing, and verifying migrations, with rules against editing applied migrations and guidance for multi-provider SQL generation. - Lookup Seeding & Constraints: Defines stable lookup ID/code seeding via LookupTableSeeder, portable semantic constraints, and preflight checks for MariaDB/MySQL non-transactional DDL. - Use Case: When adding a new entity with tenant isolation and soft delete, follow the workflow to lock domain semantics with failing tests, update the IEntityTypeConfiguration, generate per-provider migrations, and verify with architecture and integration tests. ## Quick Start Ask the AI to review or implement an EF Core entity configuration, repository, or migration following the dotnet-efcore-guidelines rules for this project.