Imported from Ab0umar/SELRS.cc.old (AGENTS.md). Install upstream with npx skills add Ab0umar/SELRS.cc.old. Copyright stays with the author.

Repository Guidelines

Project Structure & Module Organization

• client/: React + Vite frontend pages/components (patient flows, admin hub, dashboards).
• server/: backend routes, sync logic, and API entry (server/_core/index.ts).
• shared/: shared schemas/types used by both client and server.
• drizzle/: database migrations and DB artifacts.
• scripts/: operational scripts (DB backup/restore, deploy, sync checks, Android build).
• tests/ and root test-*.ts: automated and smoke-style validation scripts.
• desktop/ and desktop-electron/: Windows desktop wrappers/installers.

Build, Test, and Development Commands

• pnpm dev: run backend in watch mode for local development.
• pnpm build: run encoding checks, build frontend, and bundle server into dist/.
• pnpm start: run production server from dist/index.js.
• pnpm check: TypeScript typecheck (--noEmit).
• pnpm test: run Vitest suite.
• pnpm test:ui: run Playwright end-to-end tests.
• pnpm db:push: generate + apply Drizzle migrations.
• pnpm db:backup / pnpm db:restore: PowerShell DB maintenance scripts.

Coding Style & Naming Conventions

• TypeScript-first; keep strict typing and avoid any unless unavoidable.
• Follow Prettier defaults; run pnpm format before large PRs.
• Use descriptive names: getPatientServiceEntries, syncUserPermissionsToRole.
• File naming:
• React pages/components: PascalCase.tsx.
• Scripts/utilities: kebab-case or existing project pattern.
• Keep changes scoped; avoid unrelated refactors in hot paths (sync, queue, medical file).

Testing Guidelines

• Frameworks: Vitest (unit/integration), Playwright (UI), plus targeted script tests.
• Add or update tests when changing sync logic, patient transactions, queue movement, or medical-file persistence.
• Prefer explicit test names (example: should_update_existing_exam_instead_of_creating_new_one).
• Run at minimum: pnpm check and pnpm test before opening PR.

Commit & Pull Request Guidelines

• Existing history mixes short and descriptive messages; prefer clear imperative summaries.
• Recommended format: area: concise change (example: medical-file: update existing exam on save).
• PRs should include:
• what changed and why,
• affected paths/endpoints,
• migration/env implications,
• screenshots for UI changes (patients/admin/medical file),
• verification steps with exact commands run.

Security & Configuration Tips

• Keep secrets in .env; never commit real credentials or production keys.
• Validate sync and DB changes with pnpm db:sync-check before deployment.
• For Windows service/desktop packaging, run scripts from elevated PowerShell when required.

For additional context about technologies to be used, project structure, shell commands, and other important information, read the current plan