eetr-auth
Contributing

Overview

Conventions every contributor (human or agent) follows when changing eetr-auth.

These are the canonical conventions for changing the apps/auth codebase. They are the single source of truth for both human contributors and coding agents — keep new decisions here rather than letting them live only in chat.

Layer conventions

Entry points → services → repositories. Where new code goes, and the worker.ts OpenNext rule.

UX guidelines

Component library, destructive-action confirmations, buttons, banners, icons, theming, and state management for the admin/sign-in UI.

Releasing

How release-please cuts a release, and what it ships: the docs site and the npm client.

Also authoritative

Database schema mechanics are documented in Database (and db/README.md next to the schema files). Feature behavior and config live under Features and Reference.

Configuration

Wrangler vars and secrets — what each controls and where to set it.

Layer conventions

The strict separation between entry points, business logic, and persistence in apps/auth — and where new code goes.