Supabase
Stack Pack.

Supabase coverage from a Postgres-first lens: Auth (with MFA + SAML), Storage with image transformations, Realtime channels, Edge Functions on Deno, pgvector for embeddings, RLS as the primary authorization mechanism. Opinionated about when RLS is the right tool vs an application-layer policy.

Why it's in the catalog. Supabase grew into a credible default for SaaS backends in 2025. The pack carries the architectural opinion (RLS-first, pgvector for embeddings, MCP for AI workflows) plus the migration patterns from Firebase / Heroku / Render.

Headline products and features the pack carries opinions on. Each lives as its own canonical page under stacks/supabase/<product>.md in the etyb-skills repo — currency-stamped, sourced, opinionated.

• Postgres + RLS
• Auth (MFA + SAML)
• Storage
• Realtime
• Edge Functions (Deno)
• pgvector
• Supabase MCP
• Branching

When /etyb routes a request to one of these roles AND the Supabase pack is in play, the role's reference is composed with the platform-flavored knowledge from this stack. Same role, sharper answer.

• › system-architect
• › backend-architect
• › database-architect
• › devops-engineer
• › security-engineer

The three things on Supabase that a 2024-cutoff model is most likely to get wrong — and that this pack reflects.

• Supabase MCP: the production MCP server for Postgres-backed AI workflows
• Branching: per-PR ephemeral databases with seed + migration replay
• Auth hooks + MFA: enforced 2FA without leaving the Supabase Auth surface

The Supabase pack comes with /etyb — one install, every pack ready to go. The overlay loads automatically when the work calls for it.

$ npx skills add e-t-y-b/etyb-skills

See the full install guide for Claude Code plugin and manual routes.