auth-locked

What problem does it solve?

This Skill provides a locked authentication and authorization pattern for coverage-nextjs, ensuring consistent AuthContext usage, a single source of truth, and enforcing reuse of existing auth helpers. It prevents duplication of auth routes or custom role logic.

Core Features & Use Cases

• Reuse of AuthContext and withAuth: All API routes and client-side checks must rely on the established context and middleware.
• Server-side & Client-side consistency: Authentication order and role resolution are derived from existing implementations and the profiles table.
• Hard rules enforced: Never create new auth routes, never invent roles, always reuse withAuth and the provided helpers.

Quick Start

Follow the guidelines to adopt the locked auth pattern in a Next.js project: verify existing AuthContext.tsx, use withAuth in API routes as shown, and avoid introducing new authentication logic.