From sage
Provides integration seams for Next.js App Router + Supabase: dual-client auth (browser/server), middleware token refresh, RLS policies, typed queries, real-time subscriptions. Use for stack composition.
npx claudepluginhub xoai/sageThis skill uses the workspace's default tool permissions.
**Layer 3 — Stack Composition**
Implements Supabase Auth in Next.js App Router with browser/server clients, middleware for route protection and session refresh, and OAuth callback routes.
Integrates Supabase Auth with Next.js App Router using @supabase/ssr, middleware for protected routes, server actions, and cookie-based session management.
Implements Supabase clients for Next.js SSR server/client components, React/Vue SPAs, React Native mobile, serverless Edge Functions, and multi-tenant RLS/schema isolation.
Share bugs, ideas, or general feedback.
Layer 3 — Stack Composition
Integration seams for Next.js App Router + Supabase. Covers the five critical integration points that neither Next.js docs nor Supabase docs adequately address together.
| Seam | What Goes Wrong |
|---|---|
| Dual Clients | Agents create one client — auth silently breaks across server/client boundary |
| Middleware Token Refresh | Agents skip middleware — users randomly get logged out on expired tokens |
| RLS as Authorization | Agents rely on Next.js middleware for auth — database is still publicly accessible |
| Typed Queries | Agents use untyped select('*') — typos are silent runtime errors |
| Server Actions | Agents build REST API routes for same-app mutations instead of using Server Actions |
L1: web (domain) + baas (backend domain)
L2: nextjs (framework) + react (framework)
L3: stack-nextjs-supabase (this pack — integration seams)