ideal-auth

Provide modular auth primitives for JavaScript apps with sessions, hashing, tokens, and 2FA.

11|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/ramonmalcolm10/ideal-auth --skill ideal-auth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideal-auth
Source: https://github.com/ramonmalcolm10/ideal-auth/tree/main/skills/ideal-auth
Command: npx skills add https://github.com/ramonmalcolm10/ideal-auth --skill ideal-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auth primitives for modern JS apps, delivering secure, per-request sessions and password handling without framework dependencies.

Core Features & Use Cases

  • Stateless, encrypted cookies for sessions with optional remember-me support.
  • Hashing, token signing, and TOTP-based 2FA with recovery codes.
  • Framework-agnostic integration across Next.js, SvelteKit, Express, Hono, Nuxt, and more.

Quick Start

Install ideal-auth and wire it into your framework by providing a secret, a cookie bridge, and user resolvers, then create an Auth instance per request.

Frequently Asked Questions about ideal-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add framework-agnostic authentication to a modern JS app?

Framework-agnostic authentication is implemented by providing modular auth primitives including per-request sessions, password hashing, and token-based flows without requiring external framework dependencies.

Can I use ideal-auth for stateless cookie sessions with 2FA in SvelteKit?

Stateless encrypted cookie sessions and TOTP-based 2FA with recovery codes are fully supported across SvelteKit, Next.js, Express, Hono, and Nuxt through modular framework integration.

What do I need to configure to set up per-request authentication instances?

Per-request authentication instances require configuring a secret, a cookie bridge, a hash instance, and user resolvers to wire the framework-agnostic auth primitives into your application.

What is the best way to handle password hashing and token signing without external dependencies?

Password hashing and token signing without external dependencies is achieved using zero-dependency auth primitives that deliver secure password handling and stateless token flows directly within your JS application.

Does this authentication approach support stateless sessions and remember-me functionality?

Stateless sessions utilize encrypted cookies for secure authentication and include optional remember-me support, ensuring per-request session validity without relying on server-side session storage.