prisma-cli-migrate-diff
prisma migrate diff. Reference when using this Prisma feature.
prisma migrate diff. Reference when using this Prisma feature.
Integrate Advanced Alchemy with Flask using sync or async configs, Flask session access helpers, multiple binds, FlaskServiceMixin, JSON serialization helpers, and Flask CLI database commands. Use when adding Advanced Alchemy persistence to Flask applications or refactoring Flask SQLAlchemy code toward repository and service patterns. Do not use for framework-agnostic repository or model work.
Seed databases and load fixtures with Advanced Alchemy using JSON fixture files, sync or async helpers, repository bulk operations, and framework startup hooks. Use when creating development or test seed data, loading initial reference data, or dumping and restoring fixture-backed tables. Do not use for schema migrations or general runtime CRUD handling.
prisma db seed. Reference when using this Prisma feature.
Use Advanced Alchemy's CLI for migrations, revision management, inspection, branching, fixture dumping, and framework CLI integration. Use when setting up or operating Alembic migrations through `alchemy`, `litestar database`, or `flask database`, or when embedding the commands into Click or Typer applications. Do not use for runtime repository or service logic.
Database design patterns, SQL best practices, ORM usage (Prisma/Drizzle), and migration strategies. Use when designing schemas, writing queries, or optimizing database operations.
Update openmls native library version. Use when checking for updates, upgrading openmls, bumping version, or updating native dependencies.
Add a new database migration to EncryptedDb. Use when changing storage schema, data format, or serialization in the native library.
Use when working with JPA/Hibernate entities, repositories, or database operations to avoid N+1 queries, manage lazy loading, transactions, and entity relationships.
Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution. Українською: Оптимізуй базу, повільний запит, план виконання, індекси, N+1, кешування запитів, профілювання, блокування, партиціювання, перепиши запит, аналіз продуктивності.
Safely handle Prisma migration drift on existing databases without data loss. Use when: (1) "prisma migrate dev" shows "Drift detected: Your database schema is not in sync", (2) Prisma asks "We need to reset the schema. All data will be lost. Do you want to continue?", (3) Database was created via Supabase, direct SQL, or another ORM before adopting Prisma, (4) Adding schema changes to a production database that wasn't initialized with Prisma migrations. Covers baselining existing databases and applying incremental changes safely.
ALWAYS trigger for ANY task involving Supabase, Supabase Auth, Supabase Database, Supabase Storage, Supabase Edge Functions, Supabase Realtime, Row Level Security (RLS), PostgreSQL policies, Supabase CLI, self-hosted Supabase, database migrations, or Firebase-to-Supabase migration. This includes schema design, RLS policies, Edge Functions (Deno), auth flows, file uploads, and realtime subscriptions.
Use when continuing the active migration or rewrite after `docs/progress/MASTER.md` already exists and execution should resume from the current phase instead of recreating the planning workflow.
Use tauri-plugin-libsql for SQLite database access in Tauri apps with Drizzle ORM, browser-safe migrations, optional AES-256-CBC encryption, and Turso embedded replica sync. Use when working on this plugin's source, writing apps that consume it, adding schema changes, debugging migration or query errors, configuring encryption, or setting up Turso remote sync.
Repo cleanup workflow for dead code removal, stale comment cleanup, naming consistency, redundant code reduction, and safe maintainability improvements. USE FOR: requests like "clean up", maintenance passes, removing unused imports or variables, pruning TODOs, and replacing inappropriate production print statements. DO NOT USE FOR: speculative rewrites, major architecture changes, or broad dependency upgrades.
This skill should be used when the user asks to "add server action", "implement Supabase query", "connect to backend", "add database integration", "implement RLS", "use server actions", "add data mutation", "implement CRUD operations", "revalidate path", "add authentication check", or needs guidance on server-side integration, defense-in-depth security, or type-safe database queries with Supabase.
This skill should be used when the user asks to "start supabase locally", "set up local supabase", "run supabase dev", "initialize supabase project", "configure local database", "start local postgres", "use supabase CLI", "generate database types", or needs guidance on local Supabase development, Docker setup, environment configuration, or database migrations.
Manage database migrations and schema versioning. Use when planning migrations, version control, rollback strategies, or data transformations for any database paradigm.
Add a Layer 3 service-layer guard to an existing service. The guard reads the DB and throws before any mutation. Arguments: "<ServiceName> <operation-method> <precondition-description>"