database-gotchas

Review Supabase and PostgreSQL configurations against curated gotcha checklists.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/dain-agency/mood-tracker --skill database-gotchas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database-gotchas
Source: https://github.com/dain-agency/mood-tracker/tree/main/.claude/skills/database-gotchas
Command: npx skills add https://github.com/dain-agency/mood-tracker --skill database-gotchas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of costly, hard-to-debug errors when working with Supabase, PostgreSQL migrations, RLS policies, and database configurations, saving developers hours of troubleshooting and preventing potential production outages.

Core Features & Use Cases

  • Curated Gotcha Checklists: Structured tables of common pitfalls for security, RLS, partitioning, triggers, migrations, and Supabase platform configuration, organized by task type.
  • Anchor-Linked Deep Dives: Each gotcha links to a specific section in the full GOTCHAS.md reference for detailed context and remediation steps.
  • Use Case: For example, when writing a new RLS policy for a multi-tenant Supabase application, this Skill immediately flags the requirement to use RESTRICTIVE for layered policies and grant EXECUTE to the anon role for helper functions, preventing silent access control failures.

Quick Start

Use the database-gotchas skill to review your planned Supabase RLS policy for multi-tenant access before writing the migration SQL.

Frequently Asked Questions about database-gotchas

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

FAQPage Schema
How do I prevent silent access control failures when writing Supabase RLS policies?

To prevent silent access control failures in Supabase RLS policies, use RESTRICTIVE for layered policies and grant EXECUTE to the anon role for helper functions, ensuring strict multi-tenant access enforcement.

What are common PostgreSQL migration pitfalls that cause production data loss?

Common PostgreSQL migration pitfalls include unsafe schema alterations and missing rollback scripts. Reviewing structured SQL migration checklists before deployment prevents hard-to-debug errors and avoids permanent production data loss.

Does my Supabase database need specific configuration to avoid silent performance degradation?

Supabase database deployments require careful configuration of triggers, table partitioning, and pg_cron jobs to eliminate silent performance degradation and enforce security best practices in production environments.

Why does my multi-tenant Supabase application bypass row level security?

Multi-tenant Supabase applications bypass row level security when policies are not set to RESTRICTIVE or when helper functions lack EXECUTE permissions for the anon role, causing silent access control failures.

What is the best way to check PostgreSQL trigger setup for security best practices?

The best way to check PostgreSQL trigger setup is to use curated gotcha checklists that flag common security misconfigurations and link to detailed remediation steps for production database deployments.

Can I use anchor-linked references to troubleshoot Supabase platform settings issues?

You can use anchor-linked references to troubleshoot Supabase platform settings, jumping directly to specific sections for detailed context on resolving configuration errors and platform integration pitfalls.