2505b27437
- Add before-user-created hook function for server-side duplicate email detection - Implement fallback detection using identities array check (Supabase limitation) - Update signUpWithPassword to detect duplicate emails via hook errors or empty identities - Add error handling in login page to show duplicate email errors and auto-switch to login mode - Add auth hook setup documentation and test scripts - Add password reset and update password flows - Add email templates for signup confirmation and password reset
2.8 KiB
2.8 KiB
Repository Guidelines
Project Structure & Module Organization
app/: Next.js app router pages, routes, and layout shell; start edits inapp/page.tsx.components/: Shared UI building blocks (React + Tailwind variants) used across routes.lib/: Utilities and integrations (e.g., Supabase client/types inlib/supabase/).content/,docs/: Markdown/docs assets; update here before hardcoding copies inapp/.public/: Static assets served at/; keep optimized exports here.scripts/: Maintenance helpers (e.g.,scripts/test-contrast.ts).supabase/: Database config and migrations (supabase/migrations/*.sql).
Build, Test, and Development Commands
pnpm dev(ornpm run dev): Start local server athttp://localhost:3000with hot reload.pnpm build: Production bundle; fails on type errors for app and server components.pnpm start: Run the built app locally.pnpm lint: Run ESLint with Next.js rules overapp/,components/,lib/.pnpm types:generate: Regenerate Supabase TS types intolib/supabase/types.ts(requires project access).
Coding Style & Naming Conventions
- Language: TypeScript + React Server/Client Components; follow Next.js app router patterns.
- Formatting: 2-space indentation; prefer single quotes where lint allows; keep imports sorted logically.
- Styling: Tailwind-first; compose variants via
class-variance-authorityandtailwind-merge. - Naming: PascalCase for components, camelCase for helpers,
useXfor hooks,types.tsfor shared types. - Keep client components marked with
"use client"when needed; avoid client code in server contexts.
Testing Guidelines
- No dedicated automated test harness yet; rely on
pnpm lintand manual flows in the browser. - For data paths, validate Supabase connections with
lib/supabase/test-connection.tsor local SQL migrations. - Add route- or component-level checks (e.g., contrast checks via
scripts/test-contrast.ts) before shipping UI tweaks.
Commit & Pull Request Guidelines
- Git history mixes short feature phrases and imperative summaries; keep new commits concise and action-led (e.g.,
feat: add login heroorfix: align tab spacing). - Prefer scoped, single-purpose commits; include why when the change is non-obvious.
- PRs: describe user-facing impact, screenshots for UI changes, reproduction steps for bugs, and link issues/tasks when available.
- Note any Supabase schema changes and the migration file touched; mention if
types:generatewas rerun.
Security & Configuration Tips
- Environment: keep secrets in
.env.local; never commit them. Required keys follow Next.js/Supabase conventions (NEXT_PUBLIC_for client-safe values). - When testing auth/DB flows, ensure Supabase policies (
supabase/migrations/*_policies.sql) are applied and reviewed.