What problem does it solve? Building data-access repositories in a CoreEx-based .NET solution involves many framework-specific conventions — EfDb accessors, BiDirectionMapper rules, QueryArgsConfig filtering, and Result<T> pipelines — that are easy to get wrong without deep knowledge of the framework. ## Core Features & Use Cases - Repository Scaffolding: Generate a new repository class with [ScopedService] DI registration, EfDb accessors, and a bidirectional Contract ↔ Persistence mapper. - CRUD & Query Operations: Add Get/Create/Update/Delete methods using EfDb delegate shortcuts, or build dynamic filtered/ordered queries with QueryArgsConfig<TSelf>. - Result<T> Pipelines: Implement railway-oriented *WithResultAsync variants for projects using explicit failure propagation. - Use Case: Ask the assistant to add a Product repository with a query supporting case-insensitive SKU filtering and default ordering, and it produces the repository, mapper, EfDb accessor, and query config following CoreEx conventions. ## Quick Start Ask the assistant to create a new CoreEx repository for your entity, specifying the database type and which CRUD or query operations you need.