What problem does it solve? Backend developers repeatedly hand-write CQRS read operations (GetList with pagination, GetById) across microservices, risking inconsistent naming, missed soft-delete filters, and incorrect async handling of IQueryable sources. ## Core Features & Use Cases - Standardized Query Structure: Enforces the Application/Queries/{Entity}Get{Scope} folder layout with matching Query and QueryHandler class naming conventions. - GetList with Pagination: Builds filtered, ordered, paginated queries over IQueryable from GetAllAsync, wrapping results in PaginationResponse with total counts. - GetById with Includes: Loads a single entity with optional navigation properties via Include, returning a not-found response when missing. - Use Case: When adding a new read endpoint for the Battery entity in a .NET 9 microservice, generate the BatteryGetListQuery, its handler with search/status filters, and the BatteryGetByIdQuery handler following the project's exact conventions. ## Quick Start Ask the AI to create a CQRS GetList and GetById query with handlers for a specific entity following the cqrs-query pattern.