latitude-dev/latitude-llm · Archived

authentication

Sessions, sign-in/sign-up flows, OAuth, magic links, or organization context on the session.

First seen May 10, 2026

Installation

$ npx skills add latitude-dev/latitude-llm --skill authentication

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from latitude-dev/latitude-llm · top by installs.

npx skills add latitude-dev/latitude-llm

Browse all from latitude-dev/latitude-llm

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4.6K
License LICENSE
Default branch development
Open issues 26
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,218 B
  • docs SUMMARY.md 114 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

Authentication (Better Auth)

When to use: Sessions, sign-in/sign-up flows, OAuth, magic links, or organization context on the session.

Stack

  • @platform/db-postgres exposes createBetterAuth() in packages/platform/db-postgres/src/create-better-auth.ts, wiring better-auth with the Drizzle adapter against the shared Postgres client.
  • Sessions: auth.api.getSession({ headers }){ user, session } with typed fields.
  • User includes id, email, name — use those fields directly (no assertions).

Web app helpers

  • Session helpers: apps/web/src/domains/sessions/session.functions.ts (getSession, ensureSession, etc.).
  • Organization context is added via the customSession plugin (multi-tenant product behavior).

Domain alignment

  • Auth intent flows (login/signup completion) use use-cases from @domain/auth composed with Postgres repositories — keep policy in domain, wiring in apps.

For HTTP boundary rules (who may call what), see [architecture-boundaries](../architecture-boundaries/SKILL.md).