slop-eval

# Slop Eval Evaluate a design the way `skill-evaluation` evaluates a skill: every finding cites concrete evidence, every axis gets a 0–100 score, arithmetic runs through a script, and the output is a structured report — never a vibe check. The tell catalog lives in `references/tells.md`; read it before sweeping. The positive rubric (signature formula, cohesion checks, slop→premium pairs, and the "Adding Soul" guide) lives in `references/premium-markers.md`; read it before scoring Axes 7–8 and when writing fix prescriptions. The design context guide lives in `references/contexts.md`; read it to adjust priorities and tolerances based on the type of design being evaluated. ## Source - [The pols.dev anti-slop design law](https://pols.dev/slop.md) — the tell catalog, absolute rules, and signature formula are distilled from it. - Method modeled on [skill-evaluation](https://github.com/fabricioctelles/skills/tree/main/skills/skill-evaluation) (cite-or-cut, weighted axes, scripted scoring, failure-mode diagnosis). ## Parameters | Parameter | Description | Default | |-----------|-------------|---------| | `target` | What to evaluate: live URL, screenshot(s), code path, or Figma export | Ask user | | `brief` | Brand brief or explicit user directions the design followed | None | | `context` | Design type: `landing`, `saas`, `editorial`, `ecommerce`, or `auto` | `auto` | | `output` | Path to write the report | `./SLOP-REPORT.md` | | `compare` | Path to a previous report for t...