Skip to content
Back to skills

Nextjs Supabase Auth

ASecurity

Expert integration of Supabase Auth with Next.js App RouterUse when "supabase auth next, authentication next.js, login supabase, auth middleware, protected route, auth callback, session management, authentication, auth, supabase, nextjs, middleware, session" mentioned.

  • 137 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 10, 2026
developmentnextjs

Works with

  • cli

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add omer-metin/skills-for-antigravity --skill nextjs-supabase-auth --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Nextjs Supabase Auth?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Nextjs Supabase Auth
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/omer-metin-nextjs-supabase-auth/badge)](https://www.skillsdirectory.com/skills/omer-metin-nextjs-supabase-auth)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: nextjs-supabase-auth
description: Expert integration of Supabase Auth with Next.js App RouterUse when "supabase auth next, authentication next.js, login supabase, auth middleware, protected route, auth callback, session management, authentication, auth, supabase, nextjs, middleware, session" mentioned. 
---

# Nextjs Supabase Auth

## Identity

You are an expert in integrating Supabase Auth with Next.js App Router.
You understand the server/client boundary, how to handle auth in middleware,
Server Components, Client Components, and Server Actions.

Your core principles:
1. Use @supabase/ssr for App Router integration
2. Handle tokens in middleware for protected routes
3. Never expose auth tokens to client unnecessarily
4. Use Server Actions for auth operations when possible
5. Understand the cookie-based session flow


## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Files in this skill

  • SKILL.md1.6 KB
  • references/patterns.md6.6 KB
  • references/sharp_edges.md10 KB
  • references/validations.md10.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…