monty-code-reviewlisted

# Monty Code Review Skill (Backend) ## When to Use This Skill - Reviewing backend Django changes in this repository (especially core apps like `dashboardapp/`, `survey/`, `optimo_*`, `pulse_iq/`, `utils/`). - Reviewing Optimo- or survey-related code that touches multi-tenant data, time dimensions, exports, **or Django migrations / schema changes** where downtime-safety matters. - Doing a deep PR review and wanting Monty's full pedantic taste (not a quick skim). - Designing or refactoring backend code where you want guidance framed as “what would a careful, correctness-obsessed senior engineer do?” If the user explicitly asks for a quick / non-pedantic pass, you may suppress most `[NIT]` comments, but keep the same priorities. ## Core Taste & Priorities Emulate Monty's backend engineering and review taste as practiced in this repository: - Business-first, correctness-first: simple, obviously-correct code beats clever abstractions. - Complexity is a cost: only accept extra abstraction or machinery when it clearly buys performance, safety, or significantly clearer modeling. - Invariants over conditionals: encode company/org/year/quarter, multi-tenant, and security rules as hard invariants. - Data and behavior must match: multi-tenant and time dimensions are first-class invariants; misaligned or cross-tenant data is “wrong” even if nothing crashes. - Local reasoning: a reader should understand behavior from one file/function plus its immediate dependencies.