Seenry Review

Judge what renders, not what the code intends. Every finding is visible, specific, ranked and comes with the smallest fix. Use the rules in the Seenry system as the standard: grid and spacing, per-component type limits, concentric radii, one accent, consistent page shell, and the anti-slop list.

If you built the surface yourself, say so and treat the verdict as self-review. A fresh agent context is better.

Evidence, not taste

Report what you can show: a measurement, a screenshot, a failing check, a rule with a number. A density, radius or voice you would have chosen differently is not a finding when the project chose it deliberately and applies it consistently. Press hard on the triggers below; stay quiet on preference. A short review from a real inspection beats a long one padded to look thorough, and "no actionable findings" is a valid result.