agentleFS
sonorateksonoratek/legiox/skills/authjs-specialist/SKILL.md

authjs-specialist

Skill0 starsChanged 45 days agoMITView on GitHub

authentication flows

The file

Files
SKILL.md

Auth.js v5 Specialist

Summary

Auth.js v5 requires split-config: auth.config.ts (edge-safe, NO providers, <50KB) for middleware, auth.ts (full server, all providers + adapter) for everything else. Ring deploys 5 providers (Resend, Google, Google One Tap GIS, Apple, Crypto Wallet via viem). JWT-only strategy. Importing auth.ts in middleware CRASHES edge runtime.

Instructions

  1. Split config: auth.config.ts (edge) vs auth.ts (server)
  2. Google One Tap: CredentialsProvider + google-auth-library verifyIdToken()
  3. Crypto wallet: generateNonce + viem verifyMessage()
  4. Module augmentation for custom session fields

Deeper fields

jq -r '.mission, .expertise, .keywords' "mcp/AI-LEGIOX/legiox-truth-lens/authjs-specialist.nodus.json"

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.