auth-builder

Implements authentication systems with OAuth providers, session management, and role-based access control.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill auth-builder-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auth-builder
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/auth-builder
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill auth-builder-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building authentication and user management from scratch involves many decisions—provider selection, social login integration, session security, and regional identity verification—that are easy to get wrong. This Skill guides the implementation of a complete auth system with concrete schemas, flows, and security checklists. ## Core Features & Use Cases - Provider Selection Guidance: Decision tree for choosing Clerk, Auth.js (NextAuth v5), Supabase Auth, Firebase Auth, Keycloak, or no-code options based on your framework and needs. - Social Login & Verification Flows: Implementation priorities for Google, Apple, Kakao, Naver, magic links, Passkeys, and phone OTP, plus Korea CI/DI identity verification via PASS and NICE. - Database Schema & Security: Ready-to-use SQL schemas for users, auth_providers, and sessions, plus security requirements like Argon2id hashing, CSRF tokens, rate limiting, and token rotation. - Use Case: You are building a Next.js SaaS targeting Korean users. Use this Skill to scaffold Supabase Auth with Google and Kakao login, set up the users/sessions schema, enforce rate limiting, and wire in PASS identity verification before payment. ## Quick Start Ask the AI to implement login and signup for your app, for example by saying "implement Google and Kakao social login with session management for my Next.js app".

Frequently Asked Questions about auth-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement social login with Google and Kakao?

Social login follows an OAuth redirect flow: the client sends the user to the provider, the callback returns a provider_user_id, and the server looks up auth_providers to either log in an existing user or create a new one. Google and Kakao are low-complexity, high-conversion options to implement first.

Clerk vs NextAuth vs Supabase Auth, which should I use?

For Next.js, choose Clerk for fast implementation with prebuilt UI and organization management, Auth.js (NextAuth v5) for custom UI control, or Supabase Auth if you already use Supabase. Mobile apps typically use Firebase Auth or Supabase Auth depending on the existing ecosystem.

How do I add Korean identity verification (CI/DI) to my app?

Korean identity verification uses PASS (SKT/KT/LGU+) for age gating and one-account-per-person enforcement, or NICE for real-name and demographic confirmation. Trigger it at payment, sensitive data access, or legal requirement points rather than at initial signup.

What password hashing and session security should I use?

Use Argon2id for password hashing, with bcrypt as the minimum acceptable fallback. Sessions require expiration with refresh token rotation, CSRF tokens on state-changing APIs, OAuth state parameters, and rate limiting of 5 login attempts per minute.

How do I handle account linking across multiple OAuth providers?

Store providers in a separate auth_providers table keyed by (provider, provider_user_id) with a foreign key to users. When a returning user authenticates with a new provider sharing the same email, link the new provider row to the existing user account.