Filter AI Slop Out of Your Agent's UI, Copy, and Code

Ask an agent for a landing page and you get the purple gradient, the "It's not just X, it's Y" headline, and a wall of comment noise. antislop is a 6k-star rulebook that stops this at the source: a filter your agent loads, not a style guide it obeys.

Why This Skill Matters

AI coding agents default to a recognizable house style — generic layouts, filler copy, and redundant code comments — and asking them to "write naturally" rarely holds for a whole session. antislop turns the rejection of those patterns into 38 mandatory rules (R-01 to R-38) organized in three tiers: Hard Gate, Purpose-Gate, and Quality Locks. It is opinionated by design; the README frames it as "a filter, not a style guide" — no prescribed colors, fonts, or layouts, and creative direction stays yours.

Installation

The installer asks which skills you want, where to install them, and which agents you use:

npx antislop-ai

In Claude Code you can alternatively use the plugin route:

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

The README lists Claude Code, Codex, Antigravity, OpenCode, Cursor, Cline, Amp, Gemini CLI, Hermes, GitHub Copilot, Kimi Code, Pi, and Oh My Pi as supported agents, with the installer covering twelve of them. If you want the rules without any packaging, the README also offers a single-file route: antislop.md on its own is a complete filter you can paste into any chat window.

Real Workflow: Build a Pricing Page in During Mode

antislop runs in one of two modes. In During mode it guides the work while it is built:

1. Install as above and start a session in your project.
2. Write a short DESIGN.md with your direction — audience, tone, visual references. The core filter prevents slop but cannot invent direction; the README is explicit that a sterile result means the direction was missing, not that the filter failed (R-37).
3. Ask for the work:

按照 DESIGN.md 里的方向，为我的开发者工具做一个定价页。
三档套餐，支持月付和年付，带一个 FAQ 板块。

4. The agent builds under the rules — no decoration without purpose, no fake stats in the copy, no slop comments — and the session closes with the Delivery Gate: a mandatory PASS/FAIL report in four blocks that runs before anything ships.

The After mode is the second workflow, for output that already exists: it audits the work into a numbered findings list, you approve which items to fix, and a follow-up report confirms the result. Use it to clean up a page or a codebase an agent produced without antislop.

By default the agent asks which mode you want at the start of every session. Save a preference once and it stops asking:

npx antislop-ai --mode during

The setting lives in ~/.config/antislop/settings.json on Linux and macOS (%APPDATA%\antislop\settings.json on Windows) and is shared across agents and projects. An explicit choice in the current chat always wins for that session.

Tips

• Install skills per concern. Beyond the core antislop skill there are five add-ons, each owning one area: antislop-ui (layout, color, motion), antislop-copywriting (headlines, CTAs, fake stats), antislop-human (accessibility: contrast, keyboard, focus), antislop-layoutmobile (reflow, breakpoints, tap targets), and antislop-code (which AI-slop comments to remove and which to keep).
• The Liveliness Toolkit — three dials named ENERGY, RHYTHM, and MOTION, plus a Design Read — is how the rules push output past merely clean into something with life.
• To update an installer-based setup, run npx antislop-ai --update. Plugin installs update through their own plugin commands.
• When a saved preference applies, the skill announces it once ("antislop active: during (global preference)"), so you always know which rules are watching.

When Not to Use This

antislop rejects technique without purpose but supplies no look of its own — if you want a prescribed design system, this is not it, and DESIGN.md remains your job. It also runs inside your agent sessions rather than as a standalone linter in CI, so it will not police a repository your agent never touches. And it is deliberately opinionated: if your team disagrees with specific rules, the vendored rules are yours to read and change.

See the leaderboard for more skills.