SOURCE ORGANIZATION
Repository Structure
Use predictable project paths and keep modules isolated, discoverable, and maintainable.
Production stability and security notice
Development changes must preserve working functionality, Provider isolation, role-based access, HIPAA auditability, released Mobile compatibility, and integration stability. Never deploy AI-generated or unreviewed code directly to production.
Primary Projects
| Topic | Standard |
|---|---|
| API | C:\TruecareSystem\API — NestJS, Prisma, PostgreSQL access, integrations, security, and background services. |
| Web | C:\TruecareSystem\Web — Next.js user interface, reports, administration, and documentation portal. |
| Mobile | C:\TruecareSystem\Mobile — React Native / Expo application for workforce and EVV workflows. |
Module Organization
Each backend module should group its controller, service, DTOs, types, guards, tests, and module definition. Shared frameworks such as HIPAA should remain in dedicated folders rather than being scattered across unrelated files.
src/
hipaa/
constants/
decorators/
guards/
interceptors/
middleware/
services/
types/
schedule/
mobile/
billing/
support/File Rules
- Use descriptive names that match the business domain.
- Avoid duplicate implementations of the same business rule.
- Do not place secrets or environment-specific values in source files.
- Keep generated files out of manual editing.
- Store public documentation images under each module's
images/folder.