What problem does it solve? Setting up a new bounded context in this .NET e-commerce solution requires creating four boilerplate infrastructure files that must follow the ADR-0013 per-BC DbContext pattern, and hand-writing them risks inconsistent namespaces, missing UTC date handling, or wrong DI registration. ## Core Features & Use Cases - Four-file scaffolding: Generates the DbContext, schema Constants class, design-time DbContextFactory, and Infrastructure DI extension method in one pass. - Convention enforcement: Applies project rules such as internal sealed contexts, expression-bodied DbSet properties, UseUtcDateTimes, and configuration assembly filtering by namespace. - Use Case: When adding a new Sales/Orders bounded context, invoke the skill with the BC name, schema, and entity list to get all four files placed under ECommerceApp.Infrastructure with correct namespaces, then follow the listed manual steps for DI registration and EF configurations. ## Quick Start Ask the AI to create a per-BC DbContext for a given bounded context name, schema name, and comma-separated entity list, optionally with an infrastructure path like Sales/Orders.