# Supabase Auth Designer

> Use when the team needs sign-in methods, profiles, sessions, invitations, memberships, or auth-related architecture for a Supabase app. Trigger on requests to design authentication and authorization using Supabase Auth.

- Skill: `saranskumar/supabase-auth-designer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add saranskumar/supabase-auth-designer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saranskumar/supabase-auth-designer/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: saranskumar (https://skillmd.com/u/saranskumar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/saranskumar/supabase-auth-designer

---


# Goal
Design a Supabase auth model that fits the product, tenant structure, and permission rules.

# When to Use
- The app uses Supabase Auth.
- Workspace membership, invite flows, or profiles need planning.
- Auth and RLS must align.

# Instructions
1. Define actors, user record strategy, and profile ownership.
2. Pick sign-in methods and invitation model.
3. Decide how users join teams or workspaces.
4. Map auth events to schema and policy implications.
5. Identify which authorization checks live in RLS and which need backend logic.

# Constraints
- Do not confuse authentication with authorization.
- Avoid custom auth unless Supabase Auth clearly cannot meet the need.
- Keep role design tied to actual actions.

# Output Format
- Identity model
- Session/invite design
- Membership model
- RLS/backend enforcement notes

# Examples
- "Design Supabase auth for a B2B SaaS."
- "How should invite-only workspace access work with Supabase?"