Antislop gives coding agents a filter for generic output

Landing pages generated by Claude Code, Cursor, or Codex often converge on the same details: sparkle logos, beta pills, decorative terminals, implausible latency figures, and invented ROI claims. The open-source antislop project targets those defaults through a reusable set of agent instructions. Its GitHub repository has attracted roughly 3,500 stars.

The project instructs agents to reject common patterns in generated interfaces, marketing copy, accessibility work, mobile layouts, and code comments. Teams provide their own visual direction through a DESIGN.md file. Because antislop operates as an instruction layer, compliance depends on the agent following the loaded rules.

Inside the filter

The core file defines 38 mandatory rules, numbered R-01 through R-38, across three enforcement tiers:

• Hard Gate: absolute prohibitions.
• Purpose Gate: techniques that require an explicit reason.
• Quality Locks: checks for consistency across the result.

Several supporting components extend those rules:

• Liveliness Toolkit: three controls named ENERGY, RHYTHM, and MOTION, plus a Design Read intended to prevent sterile results.
• Delivery Gate: a required four-part PASS/FAIL report that the agent completes before delivery.
• Optional skills: focused instruction sets for UI, copywriting, accessibility, mobile layout, and code comments.

Separating the skills keeps prompts smaller and lets teams load only the relevant rules. A marketing repository can use