What problem does it solve? Connecting a Next.js frontend to a FastAPI backend with secure authentication is error-prone: developers must wire JWT token generation, verification, user data isolation, and rate limiting across two stacks. This Skill provides complete, working patterns for integrating Better Auth so every API call is authenticated and users can only access their own data. ## Core Features & Use Cases - JWT Authentication Flow: Generate JWT tokens via Better Auth on the frontend and verify them in FastAPI endpoints using dependency injection. - User Isolation: Enforce server-side data isolation so users can only read and modify their own records in database queries and API routes. - Rate Limiting: Apply IP-based and user-based rate limits with slowapi in FastAPI and middleware in Next.js, including tiered limits per user role. - Use Case: Build a task management app where each logged-in user sees only their own tasks, with all API calls carrying JWT tokens and abuse prevented by per-user rate limits. ## Quick Start Set up secure authentication between my Next.js 16 frontend and FastAPI backend using Better Auth with JWT tokens on every API call.
