Implement Supabase rate limiting, backoff, and idempotency patterns.
Use when handling rate limit errors, implementing retry logic,
or optimizing API request throughput for Supabase.
Trigger with phrases like "supabase rate limit", "supabase throttling",
"supabase 429", "supabase retry", "supabase backoff".
Installs into .claude/skills of the current project.
Are you the author of Supabase Rate Limits?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/micsapp-supabase-rate-limits)
---
name: supabase-rate-limits
description: |
Implement Supabase rate limiting, backoff, and idempotency patterns.
Use when handling rate limit errors, implementing retry logic,
or optimizing API request throughput for Supabase.
Trigger with phrases like "supabase rate limit", "supabase throttling",
"supabase 429", "supabase retry", "supabase backoff".
allowed-tools: Read, Write, Edit
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Supabase Rate Limits
## Prerequisites
- Supabase SDK installed
- Understanding of async/await patterns
- Access to rate limit headers
See `${CLAUDE_SKILL_DIR}/references/implementation.md` for detailed implementation guide.
## Output
- Reliable API calls with automatic retry
- Idempotent requests preventing duplicates
- Rate limit headers properly handled
## Error Handling
See `${CLAUDE_SKILL_DIR}/references/errors.md` for comprehensive error handling.
## Examples
See `${CLAUDE_SKILL_DIR}/references/examples.md` for detailed examples.
## Resources
- [Supabase Rate Limits](https://supabase.com/docs/rate-limits)
- [p-queue Documentation](https://github.com/sindresorhus/p-queue)
## Overview
Implement Supabase rate limiting, backoff, and idempotency patterns.
## Instructions
1. Assess the current state of the API configuration
2. Identify the specific requirements and constraints
3. Apply the recommended patterns from this skill
4. Validate the changes against expected behavior
5. Document the configuration for team reference