ucdavis

Architecture decisions: layering, design patterns, microservices trade-offs, and domain-driven design

Python architecture: PEP-8, type hints, clean layering, dependency injection, and testing strategy

General code review process: priority ordering, what to block on, how to give actionable feedback

Python data science: notebook structure, data validation, reproducibility, and model documentation

Git workflow: branch naming, conventional commits, PR conventions, and merge strategies

TypeScript refactoring: SOLID principles, DRY, type safety improvements, and eliminating code smells

Security checklist: OWASP top 10, secret scanning, input validation, and auth patterns

Language-agnostic testing principles: boundary assertions, null checks, and behavior-driven test naming

Query and interpret logs from the CAES Elastic Cloud deployment

Use when creating, migrating, replacing, wiring, styling, or testing MJML-based email templates, shared email layouts, MJML partials/components, email view models, render services, send/queue services, or MJML render tests.

Use when a request invokes @devar, mentions DEVAR work, or asks Codex to work on DEVAR-related projects. Scope the work only to Giving, Give, GivingService, GiftModels, and give-terminal unless the user explicitly names another repository or system.

Show a caes-cru team member's pixelated team image by name

caes-cru's process for creating, reviewing, and merging pull requests