What problem does it solve? ASP.NET Core applications without request throttling are vulnerable to abuse, traffic spikes, and cascading failures. This Skill provides production-ready patterns for protecting endpoints with fixed window, sliding window, token bucket, and distributed rate limiting. ## Core Features & Use Cases - Built-in Middleware Configuration: Set up Microsoft.AspNetCore.RateLimiting with global limiters, named policies, and custom 429 rejection responses. - Per-Endpoint and User-Based Policies: Apply different limits to login, API, and Razor Pages endpoints, including tier-based limits keyed by authenticated user identity. - Distributed Rate Limiting with Redis: Coordinate limits across multiple servers using atomic Lua scripts, with graceful fail-open degradation when Redis is unavailable. - Use Case: You are deploying a multi-instance API behind a load balancer and need login attempts capped at 5 per 5 minutes while general API calls allow 1000 per minute, tracked consistently across all servers. ## Quick Start Ask the AI to add rate limiting to your ASP.NET Core app with a strict login policy and a Redis-backed distributed limiter for API endpoints.