Anti-Slop Guards

Anti-slop check

You have a deterministic instrument, not just an opinion. The detector below encodes the set of rules professional designers use in production-grade designs, distilled by Gesso: 73 rules, each a detector with a documented condition and threshold, most with an idempotent auto-fix. Simple tells are caught at the regex level; structural tells (a badge floated over the hero headline, ticks sprayed on a gauge) are caught by parsing the markup. Nothing is ever executed. Your job is to run it, report exactly what it found, apply the deterministic fixes, propose concrete edits for what it cannot fix, and only then add your own judgment, clearly labeled as judgment.

"Slop" here means the visual tells that make a screen read as generated rather than designed: the gradient-clipped headline, the indigo accent nobody chose, the puffy triple drop-shadow, the emoji standing in for an icon system, the row of equal dots pretending to be a chart, the $1,842,000 figure that no designer would typeset raw. It also covers a family of genuine LAYOUT BUGS generated code keeps making (a boxless <body>, a 1px divider stranded in a 168px grid track), where the fix is not taste but correctness.

The workflow

1. Run the detector.

   npx -y @gessobuild/anti-slop check <file-or-dir> --json