pols.dev · Tool Guide

Slop.md as a design checklist: inspect the rules before using them

The original pols.dev Markdown was unavailable during this review. This article examines how an external design rulebook should be scoped, tested, and kept current.

July 15, 2026 · ~10 min · pols.dev + slop.md + demo video

AI-generated pages often repeat familiar fonts, gradients, card layouts, and vague copy. Earlier public guides describe Slop.md as a Markdown checklist addressing those defaults. The original download currently fails in this review, so its exact rules and install command must be checked before use.

ScopeTry rules in one project before applying them globally
ReviewInspect the source file and conflicts with your design system
TestCheck a real page, task, and mobile layout after applying rules
01Backstory

First, the Impeccable piece on this site

We recently covered Impeccable: a frontend design skill for Cursor, Claude Code, Codex, and more. It ships 23 commands (/typeset, /critique, and the like), can run npx impeccable detect to block slop in PRs, and recognizes your project's tokens and components.

Primary source and reference