home / skills / jeremylongshore / claude-code-plugins-plus-skills / api-rate-limiting-config

api-rate-limiting-config skill

safe

/skills/15-api-development/api-rate-limiting-config

This skill guides API rate limiting config with step-by-step, best-practice guidance and production-ready code for reliable API design.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill api-rate-limiting-config

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.2 KB

---
name: "api-rate-limiting-config"
description: |
  Configure api rate limiting config operations. Auto-activating skill for API Development.
  Triggers on: api rate limiting config, api rate limiting config
  Part of the API Development skill category. Use when working with APIs or building integrations. Trigger with phrases like "api rate limiting config", "api config", "api".
allowed-tools: "Read, Write, Edit, Bash(curl:*), Grep"
version: 1.0.0
license: MIT
author: "Jeremy Longshore <[email protected]>"
---

# Api Rate Limiting Config

## Overview

This skill provides automated assistance for api rate limiting config tasks within the API Development domain.

## When to Use

This skill activates automatically when you:
- Mention "api rate limiting config" in your request
- Ask about api rate limiting config patterns or best practices
- Need help with api development skills covering rest, graphql, openapi, authentication, and api design patterns.

## Instructions

1. Provides step-by-step guidance for api rate limiting config
2. Follows industry best practices and patterns
3. Generates production-ready code and configurations
4. Validates outputs against common standards

## Examples

**Example: Basic Usage**
Request: "Help me with api rate limiting config"
Result: Provides step-by-step guidance and generates appropriate configurations


## Prerequisites

- Relevant development environment configured
- Access to necessary tools and services
- Basic understanding of api development concepts


## Output

- Generated configurations and code
- Best practice recommendations
- Validation results


## Error Handling

| Error | Cause | Solution |
|-------|-------|----------|
| Configuration invalid | Missing required fields | Check documentation for required parameters |
| Tool not found | Dependency not installed | Install required tools per prerequisites |
| Permission denied | Insufficient access | Verify credentials and permissions |


## Resources

- Official documentation for related tools
- Best practices guides
- Community examples and tutorials

## Related Skills

Part of the **API Development** skill category.
Tags: api, rest, graphql, openapi, swagger

Overview

This skill automates configuration and guidance for API rate limiting. It helps design, generate, and validate rate limit rules for REST, GraphQL, and OpenAPI-based services. Use it to produce production-ready configs, recommended patterns, and remediation steps for common errors.

How this skill works

The skill inspects your API surface and use cases, then recommends rate limiting strategies (per-user, per-key, global, and burst limits). It can generate configuration snippets for popular gateways and middleware, validate required fields, and surface common misconfigurations. It also provides step-by-step instructions to apply and test the rules in your environment.

When to use it

You are designing or updating API rate limits for new or existing endpoints
You need configuration snippets for API gateways, proxies, or middleware
You want validation and remediation for invalid or missing rate limit fields
You are building integrations that must respect throttling limits
You need to apply best practices for public or internal APIs

Best practices

Start with conservative default limits and use metrics to iterate
Differentiate limits by identity: user, API key, IP, and service-to-service
Combine steady-state limits with short burst windows to handle traffic spikes
Expose rate limit metadata (headers) so clients can react to throttling
Implement graceful failure modes: retry-after headers, exponential backoff, and clear error codes

Example use cases

Generate NGINX/OpenResty rate limit configs for a REST API with per-user quotas
Create Envoy or API gateway rules for GraphQL endpoints with field-specific limits
Validate OpenAPI annotations for rate limiting and fill missing fields
Produce middleware code for Express, Flask, or FastAPI to enforce per-key throttles
Advise on migration strategy from global to fine-grained rate limits

FAQ

What inputs do you need to generate a config?

Provide API endpoints to protect, identity types (user/key/IP), desired limits and burst sizes, and the target gateway or framework.

Can it validate existing configurations?

Yes. It checks for required fields, conflicting rules, and common misconfigurations, and returns remediation steps.