rate-limiter-designer
覆盖算法选型与分布式落地，适合多租户与第三方限流场景。
设计并实现分布式限流与配额系统，保护 API 免受滥用与过载。
帮你设计并实现分布式限流和配额系统（比如 token bucket、滑动窗口、GCRA），含 Redis 等分布式强制方案、按租户或端点的限额设计以及标准 429 返回头。什么时候用：API 被刷、某租户把资源占光、登录注册需防暴力或要遵守第三方限速。特点是兼顾公平性与可用性，避免成为单点瓶颈并给客户端明确重试指引。
▸ 展开 SKILL.md 英文原文
Design and implement rate limiting and quota systems - algorithm selection (token bucket, sliding window, GCRA), distributed enforcement with Redis, per-tenant and per-endpoint limits, 429 response contracts with standard headers, and outbound limiting against third-party APIs. Use when an API needs throttling or quotas, endpoints are being hammered by clients or scrapers, one tenant is starving others (noisy neighbor), login or signup needs brute-force protection, or the system must respect a third-party provider's rate limits without getting banned.
帮我安装这个 skill：https://raw.githubusercontent.com/tamasbege/staff-engineer-skills/main/plugins/staff-engineer-skills/skills/rate-limiter-designer/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/tamasbege/staff-engineer-skills/main/plugins/staff-engineer-skills/skills/rate-limiter-designer/SKILL.md"# Rate Limiter Designer
You are a senior API platform engineer. Your job is to design a rate limiting system that protects the service from overload and abuse, enforces fair use across tenants, and tells clients exactly how to behave — without throttling legitimate traffic or becoming a single point of failure itself.
## When To Use
Trigger this skill when you observe these symptoms:
- An endpoint is being hammered by a runaway client, scraper, or bot
- One tenant's traffic degrades service for everyone else (noisy neighbor)
- Login, signup, or password-reset endpoints have no brute-force protection
- Business plans promise quotas ("1,000 API calls/month on Free") with no enforcement
- D