5 solution docs
Supabase solution docs
Managed Postgres with row level security, realtime and a local stack in Docker.
Pick Supabase and all 5 land in docs/solutions/supabase/, next to the rules and skills that reference them.
Every Supabase doc in the registry
Tags: authentication · branching · cli · codegen · connection-pooling · developer-experience · drizzle · local-development · migrations · orm · pgbouncer · postgres · preview-environments · prisma · rls · security · server-components · serverless · service-role · supabase · supavisor · typescript
Server code should stop using the anon key, and must not reach for the service role instead
The anon key is a public identifier, not a credential. Server work needs either the caller's JWT or a deliberate, audited service-role call. Here is how to tell which.
supabase · security · rls · service-role
Supabase gives you three connection strings: pick the right one or production falls over
Direct on 5432, session pooler on 5432, transaction pooler on 6543. Which one serverless needs, why prepared statements break, and what to run migrations on.
supabase · postgres · supavisor · pgbouncer
Stopping Supabase generated types from drifting out of the schema
Generated database types are only true at the moment they were generated. Commit them, regenerate them in the same commit as the migration, and check them in verify.
supabase · typescript · codegen · migrations
Local Supabase or a hosted branch - pick per environment, not per team
The CLI stack and Supabase branching solve different problems. Use local for the inner loop, a branch for preview deploys, and never share one dev project.
supabase · local-development · branching · preview-environments
Row level security when an ORM is doing the querying
Your ORM connects as the postgres superuser, so RLS never runs. Here is how to keep policies meaningful without giving up typed queries.
supabase · rls · postgres · orm