Repository navigation
Engineering Standards
Ankit Upadhyay edited this page Aug 25, 2026
·
2 revisions
Repository-wide quality standards. docs/engineering-standards.md is canonical; this page mirrors it and adds the cross-references.
-
Node.js 22 -
.nvmrcis the authoritative source for the Node version (the canonical doc above still says 20.x; the repo's.nvmrcwins) -
pnpm workspace package manager (
pnpm@8.15.6— nevernpm/yarn) - Turborepo task orchestration
- Small, focused PRs with clear user impact.
- Conventional commit format is mandatory; PR title follows
<type>(<scope>): <subject>— see Contributing and Governance. - Every PR includes: a summary of changes, validation steps performed, and screenshots/video for UI changes.
Before merging, changes should satisfy:
pnpm run lint
pnpm run type-check
pnpm run test
pnpm run build...plus updated docs for any changed behavior, setup, or workflow, and a clean pre-push Sonar gate.
- Add or update tests for all behavioral changes.
- Prefer fast, deterministic tests; don't merge known-flaky tests without a tracking issue.
- Keep coverage reports available for Sonar analysis.
- New code = new tests — any new file must hit ≥ 90% statements/branches/functions on first commit. The frontend carries a stricter ≥ 95% coverage mandate. Full matrix and per-artifact test requirements: Testing Strategy.
- Never commit secrets or production credentials; use
.env.example/template files. - Suspected secret leak → rotate immediately, then follow the SECURITY.md process.
- Prefer secure defaults and explicit validation at boundaries. See Security.
- Keep the root
README.md, workspace READMEs, and this wiki accurate. - Avoid stale command names and outdated paths; keep docs opinionated and executable.
- Behavior/contract change → update docs in the same PR.
- Prefer strict typing; avoid
anyunless unavoidable. Keep PRs focused and reversible. -
Never expose backend enums/acronyms in user-facing text (e.g.
PAYMENT_AT_CLINIC,VET) — map to plain language before rendering. Don't useActoras a UI label (preferLead,Support, orUpdated by). - SonarQube rules are enforced on every PR — see Code Quality Gates.
Follow AGENTS.md: state assumptions and unresolved risks, and never claim checks were run unless they were.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki