04-ENRICH-schema

Enforce Supabase schema conventions by validating table and column naming, foreign key constraints, boolean prefixes, enum types, and unique constraints during database migrations. This ensures adherence to established PostgreSQL standards for maintainability and security.

Audit Row Level Security policies by checking for proper RLS implementation on all PostgreSQL tables. This validates that RLS policy definitions enforce correct access controls and meet established security standards.

Proper foreign key constraint validation includes checking constraint definitions against established Supabase PostgreSQL standards. This process verifies naming conventions, indexing strategies, and relational integrity to prevent common schema design errors.

Yes, the schema review process checks PostgreSQL function and trigger definitions. It validates these definitions alongside view completeness and indexing strategies to ensure full compliance with established database conventions.

Validate migration file sequencing for Supabase before deploying new features that modify the database. Verifying the organization and structure of SQL migration files catches potential schema issues early in the development cycle.

The best way to review Supabase schema changes is validating table naming, columns, foreign keys, and RLS policies against project standards. This catches missing indexes or incorrect policies early before deployment.