What problem does it solve? Angular developers working with ASP.NET Zero often manually create service proxy classes or forget to register new NSwag-generated proxies as providers, causing runtime errors like NG0201. This Skill enforces the correct workflow for generating, registering, and consuming auto-generated service proxies. ## Core Features & Use Cases - NSwag Proxy Generation: Guides running npm run nswag against a live Web.Host backend to regenerate service-proxies.ts from Swagger/OpenAPI. - Provider Registration: Ensures every new *ServiceProxy class is added to SERVICE_PROXY_PROVIDERS in service-proxy.providers.ts to avoid Angular DI errors. - Usage Patterns: Provides canonical patterns for list, create/update, and delete calls using DTO constructors, inject() for DI, and finalize() for loading-state cleanup. - Use Case: After adding a new ProductAppService on the backend, regenerate proxies, register ProductServiceProxy as a provider, and call getProducts with a single GetProductsInput DTO bound to PrimeNG table pagination. ## Quick Start Regenerate the NSwag service proxies and wire up the new ProductServiceProxy in my Angular component following the standard patterns.
