Execute Supabase production deployment checklist and rollback procedures.
Use when deploying Supabase integrations to production, preparing for launch,
or implementing go-live procedures.
Trigger with phrases like "supabase production", "deploy supabase",
"supabase go-live", "supabase launch checklist".
Installs into .claude/skills of the current project.
Are you the author of Supabase Prod Checklist?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/micsapp-supabase-prod-checklist)
---
name: supabase-prod-checklist
description: |
Execute Supabase production deployment checklist and rollback procedures.
Use when deploying Supabase integrations to production, preparing for launch,
or implementing go-live procedures.
Trigger with phrases like "supabase production", "deploy supabase",
"supabase go-live", "supabase launch checklist".
allowed-tools: Read, Bash(kubectl:*), Bash(curl:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Supabase Prod Checklist
## Prerequisites
- Staging environment tested and verified
- Production API keys available
- Deployment pipeline configured
- Monitoring and alerting ready
See `${CLAUDE_SKILL_DIR}/references/implementation.md` for detailed implementation guide.
## Output
- Deployed Supabase integration
- Health checks passing
- Monitoring active
- Rollback procedure documented
## 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 Status](https://status.supabase.com)
- [Supabase Support](https://supabase.com/docs/support)
## Overview
Execute Supabase production deployment checklist and rollback procedures.
## Instructions
1. Assess the current state of the deployment 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