← Back to archive

Repo of the Day

miqdadbadjuber/anti-slop: Design rules to stop AI coding agents from generating generic "AI slop" UI.

Published: Sep 16, 2026

Open repository ↗

Design rules to stop AI coding agents from generating generic "AI slop" UI. - miqdadbadjuber/anti-slop

Summary

anti-slop is a rulebook for AI coding agents that filters out generic AI-generated output (UI, copy, and code) without prescribing any visual style. It ships as six focused "skills" covering 38 mandatory rules (R-01 to R-38) across three tiers (Hard Gate, Purpose-Gate, Quality Locks), a Liveliness Toolkit with three dials, and a mandatory Delivery Gate report the agent runs before shipping. The project is MIT-licensed and works with thirteen coding agents, including Claude Code, Codex, Cursor, and Cline.

What it is useful for

anti-slop is useful when an AI agent produces output that looks correct but feels generic: landing pages with invented statistics and "NEXT-GEN AI 2.0 beta" pills above the headline, Discord launch posts with emoji bullets and "NEW DROP" in capitals, or Python files decorated with box-drawing section banners and restated-everywhere comments. The Hard Gate bans things like fake metrics and fictitious testimonials; Purpose-Gate requires every element to justify its existence; Quality Locks cover accessibility and motion.

Six skills let an agent load only what a task needs: antislop-ui for layout, color, and components; antislop-copywriting for headlines, CTAs, and tone; antislop-human for contrast, keyboard, and focus; antislop-layoutmobile for responsive reflow; and antislop-code for trimming AI-shaped comments.

The filter is deliberately not a style guide. R-37 states that a sterile result means the user's DESIGN.md was missing, not that the filter failed. Direction stays with the engineer.

How engineers can use it

The README documents several install routes. The recommended one is the installer, which prompts for which skills, where, and which agents:

npx antislop-ai

For Claude Code, the documented plugin route is:

/plugin marketplace add https://github.com/miqdadbadjuber/anti-slop
/plugin install antislop@anti-slop

For agents without a plugin door, or for a no-folder drop into any chat window, the single-file route is:

curl -o antislop.md https://raw.githubusercontent.com/miqdadbadjuber/anti-slop/main/antislop.md

Once installed, the agent asks per session whether to run during (guide while building, close with the Delivery Gate report) or after (audit existing work, present a numbered findings list, then fix what the engineer approves). To persist a preference, the README documents:

npx antislop-ai --mode during

A shared settings file at ~/.config/antislop/settings.json (or %APPDATA%\antislop\settings.json on Windows) applies the mode to every agent and project.

Documented limitations: anti-slop does not auto-update. Each plugin route updates through its own command, the Pi package through Pi, and the installer via npx antislop-ai --update. The full install, update, and removal walkthrough for every agent lives in GUIDE.md, which the README points to as the from-zero guide.