UnoPim Code Review

REQUIRED BACKGROUND: Use unopim-standards — its reference files (laravel13.md, security.md, performance.md, scale.md, extensibility.md, localization.md, comments.md) are the rulebook. This skill is the checklist that applies them to a diff.

Scope — ratchet, not archaeology

Review the lines the change ADDED or MODIFIED. Legacy violations on untouched lines are at most a remark, never a blocker — whole-file blocking would stall every legacy edit. A newly added violation is always in scope, even when it imitates adjacent legacy code.

Blocking dimensions (any hit = request changes)

1. Comment noise — the #1 developer complaint

• ANY added comment inside a method body, object/array literal, route group, or Blade markup is a blocker — including one-line "why" comments, section dividers (// Views, // ----), and {{-- --}} narration.
• The house baseline is zero: packages/Webkul/Product/src/Repositories/ProductRepository.php (20 methods) and packages/Webkul/Product/src/Type/AbstractType.php (918 lines) ship 0 inline comments.
• A genuinely non-obvious rationale belongs in the class/method PHPDoc or the commit message. Method PHPDoc: one-line imperative summary; @param/@return only where no native type hint exists.
• Mechanical sweep: every git diff -U0 added line matching ^\+\s*(//|/\*|\{\{--) is a finding.

2. Hardcoded colors