What problem does it solve? Inconsistent application service interfaces in ASP.NET Zero projects cause broken NSwag client proxies, mismatched permissions, and non-standard DTO usage across features. ## Core Features & Use Cases - Interface Conventions: Standard method signatures for list, get-for-edit, create, update, delete, and combobox operations on IApplicationService interfaces. - HttpPost Rule for Get Methods: Ensures Get* methods with custom input DTOs are decorated with [HttpPost] so NSwag generates typed body DTOs in service-proxies.ts instead of query-string parameters. - DTO Selection Guidance: Maps return types (PagedResultDto, ListResultDto, EntityDto, NullableIdDto) and input base classes (PagedAndSortedResultRequestDto) to specific use cases. - Use Case: When adding a new Product feature, follow the naming and permission table to produce an IProductAppService interface whose methods generate correct Angular service proxies on the first build. ## Quick Start Ask the assistant to design an application service interface for a new feature following the ASP.NET Zero API design patterns.