Repository Guidelines

Project Structure & Module Organization

backend/ contains the Go API server, WebSocket hub, migrations, and Swagger docs.
frontend/ contains the React + TypeScript web app (Vite).
docs/ holds planning and architecture notes.
mobile/ is referenced in docs but not present yet; iOS work is planned for later phases.

Backend (run from backend/):

make run to start the API server.
make test or go test ./... to run all backend tests.
make test-cover to generate coverage.html.
make swagger to regenerate OpenAPI docs in backend/docs/.
make migrate-up / make migrate-down for database migrations (needs DATABASE_URL).

Frontend (run from frontend/):

Go: standard gofmt formatting, golangci-lint if available.
TypeScript: ESLint + Prettier, strict TS config.
Branch names: feature/, bugfix/, or hotfix/ prefixes.
Commit messages: clear, descriptive, imperative mood (e.g., "Add user auth endpoints").

Backend: Go testing package; unit and integration tests required for API endpoints.
Frontend: tests planned (Vitest + React Testing Library per project guidelines).
Coverage target: aim for 80%+ when tests exist; update as the test suite grows.

When creating issues, always add them to Project 3: https://github.com/users/matdemers1/projects/3.
Default new issue metadata (unless specified otherwise): milestone MVP - Phase 1, labels backend, enhancement, priority:medium, MVP.
Always update Swagger (make swagger in backend/) after backend changes.
Commit message format: multi-section, bullet-heavy template like the provided example; omit any Co-Authored-By footer.
Workflow for issues: set to In Progress → implement changes → run lint → fix lint issues → run tests → fix test failures → provide testing steps → wait for user verification → then commit/push and close issue.
After committing, push to origin main and close the related issue with a brief summary comment.