supabase-migration

Plan and execute Supabase migrations between DreamCore-V2 and DreamCore-V2-sandbox.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill supabase-migration-neighbor-game-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supabase-migration
Source: https://github.com/neighbor-game-ai/DreamCore-V2-sandbox/tree/main/.claude/skills/supabase-migration
Command: npx skills add https://github.com/neighbor-game-ai/DreamCore-V2-sandbox --skill supabase-migration-neighbor-game-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supabase migration guidance ensures that DreamCore-V2-sandbox uses the same Supabase project as DreamCore-V2, with migrations managed in the core repository and not executed directly in the sandbox, preventing drift and data loss during deployment.

Core Features & Use Cases

  • Migration planning and execution guidance for schema changes in DreamCore-V2
  • Reference to shared project docs and migration standards
  • Safe-handling practices for applying migrations across environments

Quick Start

Explain how to start a Supabase migration workflow for DreamCore-V2 using the shared project, including referencing the migration guidance in the repository.

Frequently Asked Questions about supabase-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely execute Supabase schema migrations between DreamCore-V2 and its sandbox?▼

To safely execute Supabase schema migrations, manage and apply migrations exclusively within the DreamCore-V2 repository, preventing drift and data loss by never running them directly in the sandbox environment.

What is the correct workflow for Supabase migration planning in DreamCore-V2?▼

Supabase migration planning involves referencing the shared project docs at .claude/docs/database-schema.md and following step-by-step guidance for SQL patterns and RLS considerations before execution.

Why should database migrations not be executed directly in the DreamCore-V2-sandbox?▼

Database migrations should not be executed in the sandbox because both environments share a single Supabase project; running them in the sandbox causes schema drift and potential data loss during deployment.

Can I apply Row Level Security changes when migrating Supabase assets across DreamCore projects?▼

Yes, you can apply Row Level Security changes during Supabase migration by following the RLS considerations and SQL migration patterns outlined in the shared DreamCore-V2 project documentation.

What's the best way to prevent schema drift when using a shared Supabase project across environments?▼

The best way to prevent schema drift is to centralize all Supabase migrations in the core DreamCore-V2 repository and strictly avoid executing migration scripts in the sandbox environment.