---

name: rate-limiting description: > Comprehensive skill definitions for rate-limiting. Includes multiple references and diagrams. version: "2.0.0" author: "j4flmao" license: "MIT" type: skill compatibility: claude-code: true cursor: true codex: true windsurf: true tags: [rate-limiting, backend, engineering]

rate-limiting

Purpose

Comprehensive description for rate-limiting providing detailed architectures and best practices.

Core Principles

1. First principle - Reliability
2. Second principle - Scalability
3. Third principle - Maintainability
4. Fourth principle - Security
5. Fifth principle - Observability

Agent Protocol

Triggers: Code execution Input Context Required: Repository context Output Artifact: System design document Response Formats:

{ "status": "ok", "action": "completed" }

Decision Matrix

[Start] -> (Condition Check) -> [End]
               |
               v
          [Alternative]

Detailed Architectural Overview

[Client] ---> [API Gateway] ---> [Microservice]
                                     |
                                     v
                                 [Database]

Workflow Steps

Phase 1

1. Initialization step 1
2. Initialization step 2
3. Initialization step 3
4. Initialization step 4 Phase 2
5. Processing step 1
6. Processing step 2
7. Processing step 3
8. Processing step 4 Phase 3
9. Storage step 1
10. Storage step 2
11. Storage step 3
12. Storage step 4 Phase 4
13. Retrieval step 1
14. Retrieval step 2
15. Retrieval step 3
16. Retrieval step 4 Phase 5
17. Optimization step 1
18. Optimization step 2
19. Optimization step 3
20. Optimization step 4 Phase 6
21. Cleanup step 1
22. Cleanup step 2
23. Cleanup step 3
24. Cleanup step 4

Extended Troubleshooting Guide

Symptom	Primary Cause	Mitigation Action
High Latency	Network Congestion	Scale up resources
Data Loss	Database Failure	Restore from backup
Connection Refused	Service Down	Restart service
Unauthorized Access	Invalid Token	Renew token
Out of Memory	Memory Leak	Optimize code
Disk Full	Log Overload	Rotate logs

Complete Execution Scenario

[Trigger] -> [Analysis] -> [Action] -> [Result Verification]

Rules and Guidelines

1. Always validate inputs.
2. Ensure backward compatibility.
3. Keep logs structured.
4. Fail gracefully.
5. Apply rate limiting where appropriate.

Reference Guides

• Reference 0
• Reference 1
• Reference 2
• Reference 3
• Reference 4
• Reference 5
• Reference 6
• Reference 7

Handoff

Refer to other standard skills if specialized logic is required.