Implement passwordless Magic Link authentication with server-side session checks in Next.js 16.
npx skills add https://github.com/atilladeniz/next-go-pg --skill auth-pages
Please help me install this Agent Skill. Skill: auth-pages Source: https://github.com/atilladeniz/next-go-pg/tree/main/.claude/skills/auth-pages Command: npx skills add https://github.com/atilladeniz/next-go-pg --skill auth-pages
This Skill provides a robust, server-side first approach to building authentication pages in Next.js, eliminating common UI flicker issues and ensuring a smooth user experience. It streamlines the implementation of secure login, registration, and protected routes, saving you from complex client-side session management.
broadcast-channel.signIn, signOut) only for user interactions, not session checks./settings, use this skill to implement server-side session checks and ensure a flicker-free user experience by avoiding client-side useSession() and redirecting unauthenticated users instantly.Describe the recommended pattern for creating a new protected page in Next.js using server-side session checks to prevent UI flicker and ensure immediate redirection for unauthenticated users.
High-intent search queries and answers about installing and using this skill.
Server-side session checks using getSession prevent flicker by validating authentication before the page renders, eliminating client-side delays. Redirect unauthenticated users instantly without showing the protected content first, ensuring a seamless user experience on protected routes.
Passwordless Magic Link authentication uses email-based sign-in instead of passwords. Implement it with signIn.magicLink for client actions, backend email delivery via webhooks, and server-side session validation to create secure login and verification pages in Next.js 16 apps.
Cross-tab synchronization uses broadcast-channel to share authentication state changes across multiple tabs instantly. This ensures users remain logged out or in across all browser windows when they sign out or when their session expires.
Yes, server-side session checks eliminate the need for client-side useSession hooks. Use getSession to validate the session before rendering the page, which prevents flicker and removes the requirement for client-side session management on protected routes.
Yes, the implementation covers rate limiting as part of backend email delivery via webhooks, protecting your authentication system from brute-force attacks and abuse during login and verification flows.
The Skill provides UI components architecture for login pages, verification pages, email verification UI, and protected dashboards. These components integrate with server-side session handling and Magic Link flows for complete authentication page implementations.
NikileshReddyTIntegrate Better Auth authentication into TypeScript applications with plugins and adapters.
m13vManage Gmail emails via command-line interface with Google Workspace integration.
oakossSend and manage emails programmatically through the Resend API.
Eng0AIGenerate a Go backend scaffold with Gin, MongoDB, and JWT authentication.