miqdadbadjuber/anti-slop

What it claims

antislop is a filter, not a style guide. It rejects technique used without purpose and requires "liveliness", but it never supplies aesthetic direction. That job belongs to a user-written DESIGN.md. The README demonstrates this with one brief built four ways (with or without antislop, crossed with with or without DESIGN.md). Only the combination of both is described as "clean and directed at the same time." Rule R-37 states the consequence: a sterile result means direction was missing, not that the filter failed. Current release is v3.2.20, licensed MIT.

How it works

Each session runs in one of two modes:

• During guides work as it is built. It ends with the Delivery Gate, a PASS/FAIL report in four blocks. Use it for new builds.
• After audits existing output. It produces a numbered findings list, you approve which items to fix, and it then issues a follow-up report.

The mode is resolved in a strict order:

flowchart TD
  S[Session start] --> A{Mode requested in chat?}
  A -- yes --> M[Use it; saved setting unchanged]
  A -- no --> B{Saved preference?}
  B -- yes --> N[Announce once, use it]
  B -- no --> Q[Ask: during or after]
  M --> D{Mode}
  N --> D
  Q --> D
  D -- during --> G[Build, then Delivery Gate report]
  D -- after --> F[Findings list, approve fixes, follow-up report]

Skills reference the core rules by number rather than duplicating them, so adding a skill leaves the core unchanged. A catalogue of every named pattern is generated from the skills and checked in CI.

How to use it

Interactive installer (it asks which skills, project or global scope, and which agents, and detects installed agents):

npx antislop-ai

Via skills.sh (copies the same folders only):

npx skills add miqdadbadjuber/anti-slop

Plugin routes include:

codex plugin marketplace add miqdadbadjuber/anti-slop
codex plugin add antislop@anti-slop

cline plugin install https://github.com/miqdadbadjuber/anti-slop.git

The Cline command covers the CLI only. For the VS Code and JetBrains extensions, use the installer. There are further routes for /plugin, agy, omp (Oh My Pi) and pi, all listed in GUIDE.md.

For any chat window with no packaging, antislop.md alone is a complete filter:

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

To save a default mode and skip the per-session question:

npx antislop-ai --mode during

Pass after instead of during for audits, or --mode alone to view the current setting. The setting is stored in ~/.config/antislop/settings.json on Linux and macOS, and %APPDATA%\antislop\settings.json on Windows (falling back to ~/.config when %APPDATA% is unset).

To update:

npx antislop-ai --update

This replaces both the project and home-directory installs and prints the release it replaced. Plugin and Pi installs update through their own agents' commands.

Limits

• No self-updating. Skills load at session start, so you must open a new session after any update.
• Older copies keep asking. Installs that predate the mode preference still ask the mode question unconditionally. Installer-managed project pointers need the installer re-run in each project, and plugin users must update the plugin.
• No improvement without direction. It "never beautifies on its own." Without a DESIGN.md, expect clean but sterile output.
• Partial installer coverage. The installer covers twelve agents, while the FAQ lists thirteen (including Oh My Pi), which is installed via its own plugin route.
• No quantitative evaluation. The page offers only the side-by-side image comparisons as evidence.