Design and implement rate limiting strategies
Scanned 9/2/2026
Install to Claude Code
npx -y skills add a5c-ai/babysitter --skill rate-limiter-designer --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Rate Limiter Designer?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/a5c-ai-rate-limiter-designer-babysitter)More formats (shields.io, HTML) on the badges page.
---
name: rate-limiter-designer
description: Design and implement rate limiting strategies
allowed-tools:
- Read
- Write
- Edit
- Glob
- Grep
- Bash
graph:
domains: [domain:software-engineering]
specializations: [specialization:sdk-platform-development]
skillAreas: [skill-area:rate-limiting, skill-area:api-design]
roles: [role:platform-engineer]
topics: [topic:api-design, topic:developer-experience]
---
# Rate Limiter Designer Skill
## Overview
This skill designs and implements rate limiting strategies including token bucket, sliding window, and quota systems to protect APIs while providing fair access.
## Capabilities
- Implement token bucket and leaky bucket algorithms
- Configure per-key and per-user limits
- Design quota and usage systems
- Generate rate limit HTTP headers
- Implement distributed rate limiting
- Configure burst allowances
- Design rate limit tiers
- Handle rate limit exceeded responses
## Target Processes
- Platform API Gateway Design
- Authentication and Authorization Patterns
- Developer Portal Implementation
## Integration Points
- Redis for distributed state
- Rate limiting middleware
- API gateway plugins
- CDN rate limiting
- Database-backed quotas
## Input Requirements
- Rate limit requirements
- Tier definitions
- Burst allowances
- Distribution strategy
- Header conventions
## Output Artifacts
- Rate limiting implementation
- Quota management system
- Rate limit headers
- Tier configuration
- Admin management API
- Usage tracking
## Usage Example
```yaml
skill:
name: rate-limiter-designer
context:
algorithm: sliding-window
storage: redis
tiers:
- name: free
requests: 100
window: 1h
burst: 10
- name: pro
requests: 10000
window: 1h
burst: 100
headers:
limit: X-RateLimit-Limit
remaining: X-RateLimit-Remaining
reset: X-RateLimit-Reset
responses:
exceeded:
status: 429
retryAfter: true
```
## Best Practices
1. Use sliding window for accuracy
2. Include burst allowances
3. Return standard rate limit headers
4. Provide clear Retry-After values
5. Implement distributed limiting
6. Design fair quota systems
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!