auth-personalization

maneeshanif's avatarfrom maneeshanif

Add Better Auth signup/signin, personalize chapter content, and persist user preferences. Use when implementing authentication, user sessions, or personalized content delivery.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 7, 2025
[Developer Tools]

When & Why to Use This Skill

This Claude skill streamlines the integration of secure authentication and tailored user experiences in modern web applications. It provides a comprehensive framework for implementing Better Auth for session management, configuring Neon databases for persistent storage, and enhancing RAG-driven systems with user-specific context to deliver highly personalized AI responses.

Use Cases

  • Implementing secure signup and sign-in workflows using Better Auth with FastAPI backends and Docusaurus frontends.
  • Developing personalized AI tutoring or content platforms that adjust response tone and complexity based on stored user difficulty preferences.
  • Building persistent user profile systems that track reading history and focus tags to provide 'resume' suggestions and reranked search results.
  • Securing API endpoints and managing cross-site request forgery (CSRF) and cookie settings for full-stack developer projects.
nameauth-personalization
descriptionAdd Better Auth signup/signin, personalize chapter content, and persist user preferences. Use when implementing authentication, user sessions, or personalized content delivery.

Auth Personalization Skill

Instructions

  1. Auth plumbing

    • Install Better Auth client/server SDKs
    • Configure redirect URIs and cookie/CSRF settings
    • In FastAPI, add auth dependency to protect endpoints
    • Verify tokens server-side

  2. Data model

    • Neon tables:
      • users(id, email, name, role)
      • preferences(user_id, difficulty, focus_tags, lang)
    • Reuse sessions table if present from RAG service

  3. UX

    • Docusaurus: add login/logout buttons
    • Display session state in header
    • Guard personalization features behind login
    • Provide preferences UI (dropdowns/tags) saved via backend

  4. Personalization logic

    • Pass user prefs into RAG prompt context:
      • difficulty → adjust answer tone
      • focus_tags → rerank payload
    • Store last chapters read for resume suggestions

Examples

// Better Auth client setup
import { createAuthClient } from "better-auth/client";

export const authClient = createAuthClient({
  baseURL: process.env.NEXT_PUBLIC_API_URL,
});

# FastAPI auth dependency
from fastapi import Depends, HTTPException

async def get_current_user(token: str = Depends(oauth2_scheme)):
    # Verify Better Auth token
    # Return user or raise 401
    pass

Definition of Done

  • Users can sign up/sign in via Better Auth; session recognized by backend
  • Preferences persisted in Neon; API to update/fetch works
  • RAG responses reflect preferences (tone/focus) when provided
  • Basic UI for login + prefs exists in Docusaurus