frontend-slop-auditlisted

# frontend-slop-audit Audit an already-built page for the patterns that mark it as machine-generated. This is a review pass, not a design pass: it takes existing output and returns a list of specific, located defects. Two kinds of finding. **Hard rules** are countable or measurable -- a wrapped CTA, a two-line nav, five eyebrows across seven sections -- and failing one means the page is broken, not merely unfashionable. **Tells** are patterns that are individually defensible but appear so reliably in generated output that their presence identifies the author. Both are empirical, mined from repeated production failures rather than derived from principle, which is also why they need re-verification over time. ## What You Get - A catalog of AI-generated visual, copy, and structural tells with concrete replacements - Mechanically checkable layout rules (hero fit, eyebrow ratio, bento cell count, CTA discipline) - An 8-group pre-flight checklist ordered cheapest-check-first - Contrast and consistency-lock verification steps that catch defects static review misses - A reporting format that produces located, actionable findings ## When to Use - Auditing a generated landing page, portfolio, or marketing site before shipping - Diagnosing why a page "looks AI-generated" or "looks templated" - Running a final pre-flight pass over frontend output - Reviewing a redesign against the page it replaced - Establishing ship criteria for machine-generated UI ## When NOT to Use - **Design