programming-philosophy

Check intent-revealing names, single responsibility, exception-based error handling, and absence of symptom-hiding guards. Every review finding gets investigated and resolved as fix or reject with factual grounding, never skipped.

Vertical slicing means every PR cuts through all layers (model, logic, UI) and delivers a complete usable increment of the core job. Horizontal slices like 'all models first, views last' are forbidden because each layer is worthless until the final merge.

Only for genuine trade-offs between user goals such as scope, priority, or taste. Technical choices with one clear winner after research should be built or announced directly, not offered as a multiple-choice menu.

A correlated proxy reads a downstream symptom instead of the source fact, so it fails in state combinations you did not test. The rule requires asking the owner of the fact directly, following Tell-Don't-Ask and single source of truth.

Treat red tests as an active blocker regardless of who caused them. Fix or report them as your first action before continuing feature work, because a red suite removes the safety net for detecting what your change breaks.