← ClaudeAtlas

slop-checklisted

Ship-gate checklist that catches AI-generated design slop before you call a page done. Use when building or reviewing a landing page, hero, card, button or section; when a design "looks basic" and you can't say why; or right after a design gets rejected.
systemonster/slop-check · ★ 1 · Web & Frontend · score 74
Install: claude install-skill systemonster/slop-check
# Slop check A design that is *technically fine* and still reads as machine-made fails for a small number of repeatable reasons. This is the list of them. Run it before you call anything done. **One "yes" means the page is not finished.** Provenance: distilled from the banned-pattern and sacred-pattern rules of an abandoned design-intelligence project that had ingested ~2,600 Awwwards Site-of-the-Day winners, plus lessons from real client rejections. See CREDITS. --- ## Order matters — do these first Skipping a step here comes back later as slop you can't name. 1. **Typography before decoration.** Establish hierarchy — heading/body/label scale, weight contrast, line length — before you touch color, shadow or radius. A page decorated on top of flat hierarchy cannot be rescued by styling. 2. **Layout comes from the content's logic, not from a card grid.** If "card grid" was the reflex answer, the layout was not designed. Ask what shape the content actually is. 3. **Spacing should be rhythmic and uneven.** Giving every section the same vertical padding is the quietest source of template-feel. Build a rhythm: places that breathe, places that compress. 4. **Motion needs a doctrine.** Motion must express hierarchy, time, or spatial logic. "It looks nice" does not pass. If removing an animation costs the reader nothing, remove it. --- ## A. Composition — most failures are here 1. **Template hero?** Hero → features → pricing, assembled by default rather than because the con