YosemiteCrew/Yosemite-Crew

---

name: backend-patterns

description: Use when working in apps/backend — new endpoints, controllers, services, models, queues/workers, or integrations. Covers the Router to Controller to Service to Model architecture, Zod validation, Prisma/PostgreSQL data access, Winston logging, BullMQ jobs, and FHIR/IDEXX/Merck integrations.

---

name: code-review

description: Use when reviewing code, auditing a PR, or doing an adversarial review of a change. Runs quality, security, accessibility, and convention checks specific to this codebase.

---

name: desktop-sonar

description: Use when fixing SonarCloud issues in apps/desktop or writing Sonar-clean Electron and renderer code. Covers the enforced rule categories, the accepted role=dialog deferral, CSP and page-asset rules, and links the live SonarCloud project.

---

name: frontend-design

description: Use when building or changing UI in apps/frontend. Covers the custom design system, component library (Button, Card, Badge, and more), design tokens, and styling conventions so UI stays consistent and on-brand.

---

name: frontend-sonar

description: Use when fixing SonarQube issues in apps/frontend or writing Sonar-clean code. Contains the full enforced rule set with examples and quick fixes.

---

name: frontend-testing

description: Use when writing or fixing tests in apps/frontend. Covers Jest and React Testing Library conventions, targeted test runs, the coverage mandate, Zustand mocking, and common pitfalls.

---

name: mobile-patterns

description: Use when working in apps/mobileAppYC. Covers React Native architecture, navigation, Redux Toolkit state management, and mobile-specific conventions.

---

name: monorepo-ops

description: Use for monorepo-level work — running pnpm and turbo scripts, adding dependencies, changing shared packages, or cross-app changes. Covers workspace layout, filters, and build and validation order.

---

name: react-doctor

description: Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.

---

name: yosemite-client-communications

description: Draft and adapt veterinary practice messages for reminders, estimates, follow-ups, complaints, and approved care instructions. Use for client-facing email, SMS, call scripts, and translations. Preserves supplied clinical facts; does not diagnose, prescribe, interpret results, or send messages without authorization.

---

name: yosemite-data-migration-audit

description: Audit veterinary software exports and migration samples for missing records, duplicate identifiers, broken relationships, attachment gaps, and balance differences. Use before switching systems or accepting an import. Performs read-only analysis and acceptance planning, not live migration, automatic deduplication, or record repair.

---

name: yosemite-inventory-planning

description: Review veterinary stock sheets for expiry exposure, count discrepancies, and replenishment needs using confirmed units, demand, and lead times. Use for inventory reviews, cycle-count plans, and draft reorder lists. Does not prescribe, substitute medicines, authorize disposal, or place orders.

---

name: yosemite-practice-workflow-audit

description: Map veterinary practice workflows, identify evidence-backed bottlenecks, and design small measurable improvements. Use for booking, check-in, handovers, results follow-up, discharge, and administrative delays. Reviews processes rather than diagnosing patients, ranking employees, or defaulting to software purchases.

---

name: yosemite-staff-onboarding

description: Create role-specific onboarding plans, competency checklists, and operational SOPs for veterinary practices using their approved policies. Use for new hires, cross-training, handovers, and documenting practice procedures. Does not invent clinical protocols, certify competence, or determine employment law.

---

name: yosemite-vet-software-buyer

description: Help veterinary software buyers define requirements, evaluate any software category, compare quotes, uncover hidden contract terms, and plan a safe purchase or exit. Use for questions about what to buy, what to ask in demos, full costs, renewals, data rights, integrations, AI tools, or reviewing a veterinary software agreement. Provides impartial guidance under Yosemite Crew; does not promote a supplier or provide clinical advice.

---

name: yosemite-vet-visit-prep

description: Help pet owners organize observations, history, medication information, and questions into a concise veterinary appointment brief. Use for routine visits, new concerns, rechecks, or referrals. Preparation only, not diagnosis, treatment, dosing, or a substitute for urgent veterinary care.

---

name: backend-patterns

description: Use when working in apps/backend — new endpoints, controllers, services, models, queues/workers, or integrations. Covers the Router to Controller to Service to Model architecture, Zod validation, Prisma/PostgreSQL data access, Winston logging, BullMQ jobs, and FHIR/IDEXX/Merck integrations.

---

name: code-review

description: Use when reviewing code, auditing a PR, or doing an adversarial review of a change. Runs quality, security, accessibility, and convention checks specific to this codebase.

---

name: desktop-sonar

description: Use when fixing SonarCloud issues in apps/desktop or writing Sonar-clean Electron and renderer code. Covers the enforced rule categories, the accepted role=dialog deferral, CSP and page-asset rules, and links the live SonarCloud project.

---

name: frontend-design

description: Use when building or changing UI in apps/frontend. Covers the custom design system, component library (Button, Card, Badge, and more), design tokens, and styling conventions so UI stays consistent and on-brand.

---

name: frontend-sonar

description: Use when fixing SonarQube issues in apps/frontend or writing Sonar-clean code. Contains the full enforced rule set with examples and quick fixes.

---

name: frontend-testing

description: Use when writing or fixing tests in apps/frontend. Covers Jest and React Testing Library conventions, targeted test runs, the coverage mandate, Zustand mocking, and common pitfalls.

---

name: mobile-patterns

description: Use when working in apps/mobileAppYC. Covers React Native architecture, navigation, Redux Toolkit state management, and mobile-specific conventions.

---

name: monorepo-ops

description: Use for monorepo-level work — running pnpm and turbo scripts, adding dependencies, changing shared packages, or cross-app changes. Covers workspace layout, filters, and build and validation order.

---

name: react-doctor

description: Use when finishing a feature, fixing a bug, before committing React code, or when the user types `/doctor`, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.

---

name: yosemite-client-communications

description: Draft and adapt veterinary practice messages for reminders, estimates, follow-ups, complaints, and approved care instructions. Use for client-facing email, SMS, call scripts, and translations. Preserves supplied clinical facts; does not diagnose, prescribe, interpret results, or send messages without authorization.

---

name: yosemite-data-migration-audit

description: Audit veterinary software exports and migration samples for missing records, duplicate identifiers, broken relationships, attachment gaps, and balance differences. Use before switching systems or accepting an import. Performs read-only analysis and acceptance planning, not live migration, automatic deduplication, or record repair.

---

name: yosemite-inventory-planning

description: Review veterinary stock sheets for expiry exposure, count discrepancies, and replenishment needs using confirmed units, demand, and lead times. Use for inventory reviews, cycle-count plans, and draft reorder lists. Does not prescribe, substitute medicines, authorize disposal, or place orders.

---

name: yosemite-practice-workflow-audit

description: Map veterinary practice workflows, identify evidence-backed bottlenecks, and design small measurable improvements. Use for booking, check-in, handovers, results follow-up, discharge, and administrative delays. Reviews processes rather than diagnosing patients, ranking employees, or defaulting to software purchases.

---

name: yosemite-staff-onboarding

description: Create role-specific onboarding plans, competency checklists, and operational SOPs for veterinary practices using their approved policies. Use for new hires, cross-training, handovers, and documenting practice procedures. Does not invent clinical protocols, certify competence, or determine employment law.