supabase-migration-deep-dive
Execute Supabase major re-architecture and migration strategies with strangler fig pattern.Use when migrating to or from Supabase, performing major version upgrades,or re-platforming existing integrations to Supabase.Trigger with phrases like "migrate supabase", "supabase migration","switch to supabase", "supabase replatform", "supabase upgrade major".
When & Why to Use This Skill
This Claude skill facilitates seamless Supabase re-architecture and migration using the industry-standard Strangler Fig pattern. It provides a structured framework for migrating to or from Supabase, performing major version upgrades, and re-platforming existing integrations. By guiding the agent through assessment, adapter layer implementation, and incremental traffic shifting, it minimizes downtime and technical risk during complex database transitions.
Use Cases
- Legacy to Supabase Migration: Gradually replacing legacy database components with Supabase services to ensure zero-downtime transitions and data integrity.
- Major Version Upgrades: Executing high-stakes Supabase version updates by running parallel environments and shifting traffic incrementally to mitigate breaking changes.
- System Re-platforming: Moving existing backend infrastructures and third-party integrations to the Supabase ecosystem while maintaining service continuity.
- Database Re-architecture: Implementing the Strangler Fig pattern to modernize monolithic database schemas into a scalable, modern Supabase architecture.
| name | supabase-migration-deep-dive |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(node:*), Bash(kubectl:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Supabase Migration Deep Dive
Prerequisites
- Current system documentation
- Supabase SDK installed
- Feature flag infrastructure
- Rollback strategy tested
Instructions
Step 1: Assess Current State
Document existing implementation and data inventory.
Step 2: Build Adapter Layer
Create abstraction layer for gradual migration.
Step 3: Migrate Data
Run batch data migration with error handling.
Step 4: Shift Traffic
Gradually route traffic to new Supabase integration.
Output
- Migration assessment complete
- Adapter layer implemented
- Data migrated successfully
- Traffic fully shifted to Supabase
Error Handling
See {baseDir}/references/errors.md for comprehensive error handling.
Examples
See {baseDir}/references/examples.md for detailed examples.