antislop

Anti Slop: Rules for AI Coding Agents. It stops them from generating generic "AI slop" UI and copy, without letting the result turn sterile. It is a filter, not a style guide: no prescribed colors, fonts, or layouts. It is not only for building pages: it also writes and audits copy, so AI text stops reading like AI. And it never beautifies on its own; DESIGN.md (yours) is where beauty and direction come from.

New here? Start with the GUIDE.md. It explains what antislop is and how to install it, from zero.

What it does

• 38 mandatory rules (R-01 to R-38) in three tiers: Hard Gate (absolute), Purpose-Gate (technique allowed, reason required), Quality Locks (consistency)
• A Liveliness Toolkit with three dials (ENERGY / RHYTHM / MOTION) and a Design Read, so the result is alive and specific, not just "clean"
• A Delivery Gate: a mandatory PASS/FAIL report in four blocks, run before anything ships
• Additive skills, one per concern, so an agent only loads what a task needs

The core prevents slop but cannot invent direction. DESIGN.md (yours) supplies it; a sterile result means the direction was missing, not that the filter failed (R-37).

See the difference

The same brief, the same page, generated four times over. antislop filters; DESIGN.md supplies direction. They are two different jobs, and these are the four results. Copy and code follow as before-and-after pairs instead of four separate builds, because nothing else has to supply direction there.

UI

Three of the four builds. The first uses neither tool, the second only antislop, the third only DESIGN.md.

The fourth uses both, and it is the only one of the four that is clean and directed at the same time:

Copy

One prompt, run twice.

Code

One file, run twice.

Every image in this section opens full size if you click it.

Install

antislop ships as a set of standard agent skills (one folder per skill, holding a SKILL.md). The core is always loaded; the other skills load only when the task needs them. This section is the reference: every install command, in one place. GUIDE.md walks through them from zero, and its Update and Remove sections cover every route the same way.

1. The installer (recommended)

One command, then answer the prompts. It asks which extra skills you want, where to install (this project or everywhere), and which agents you use, then copies the folders. It is also the only route that writes the pointer reloading antislop every session on a project install; a global install relies on the skills loading themselves by description.

npx antislop-ai

To update later, run the same command and choose Overwrite them when it finds the existing folders. Choosing Keep what is there installs nothing and leaves you on the old version.

2. The skills directory

antislop is listed on skills.sh, the open directory for agent skills:

npx skills add miqdadbadjuber/anti-slop

This copies the same folders as path 1 and nothing else: no pointer, so antislop reloads by description alone. GUIDE.md covers adding the pointer afterwards, and updating or removing this route.

3. The plugin (Claude Code)

Add the marketplace once, then install the plugin:

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

4. The plugin (Antigravity)

The same repo is an Antigravity plugin. Install it with the Antigravity CLI:

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

5. The plugin (Codex)

The same repo is a Codex plugin and marketplace. Add the marketplace once, then install the plugin:

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

6. The plugin (Cursor)

The same repo is a Cursor plugin. Add it as a plugin marketplace with the Cursor Agent CLI:

agent plugin marketplace add https://github.com/miqdadbadjuber/anti-slop

Then open Customize in Cursor, find antislop, and select Install, choosing project or user scope.

7. The plugin (Kimi Code)

The same repo is a Kimi Code plugin. Install it in a Kimi Code session, then start a new one:

/plugins install https://github.com/miqdadbadjuber/anti-slop

The URL resolves to the latest release. Kimi Code installs plugins per user, so this covers every project.

Where the skills live

Every skill is a folder of the open Agent Skills standard (<name>/SKILL.md), so it drops into any agent that reads the standard. The installer (path 1) installs into whichever of these you use, creating the folder if it is missing:

The Gemini CLI row is legacy support: Antigravity replaced it, but the installer still writes there for existing setups.

Antigravity, Copilot, and Kimi Code share one folder. Copilot also reads .github/skills/ and .claude/skills/, and Kimi Code also reads .kimi-code/skills/, but the installer writes the folder they have in common, so picking them together installs antislop once.

Those are the project paths. A global install writes the same folder under your home directory, with three exceptions: OpenCode writes to ~/.config/opencode/skills/, Antigravity to ~/.gemini/config/skills/, and Codex to ~/.agents/skills/, the user-level folder Codex documents in place of its own ~/.codex/skills/. Copilot, OpenCode, and Kimi Code read that home-level folder too, so it is where a global install reaches them.

Hermes needs one extra step after a project install: it will not load skills out of a cloned repository until you run hermes skills trust once in that project.

Manual (single file, no packaging)

The core antislop.md alone is a complete filter you can paste into any chat window. Download it and tell your agent to read it; the First-Run wizard inside it installs skills the manual way:

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

Skills