Rate Limiter Designer Skill
SkillMediaDesign and implement rate limiting strategies
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the Rate Limiter Designer Skill skill
What this skill tells your AI
The instructions your AI receives, as published by a5c-ai/babysitter in library/specializations/sdk-platform-development/skills/rate-limiter-designer/SKILL.md and read by ahel’s review.
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
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
- Use sliding window for accuracy
- Include burst allowances
- Return standard rate limit headers
- Provide clear Retry-After values
- Implement distributed limiting
- Design fair quota systems
Signals
- GitHub stars
- 2k
- Forks
- 112
- Last commit
- Sep 2026
Advanced
- Item type
- skill
- Key
rate-limiter-designer- Source
- github.com/a5c-ai/babysitter