antislop
Anti Slop: Rules for AI Coding Agents. The core filter. Load always to stop generic AI slop.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Anti Slop: Rules for AI Coding Agents
A rulebook that stops an AI coding agent shipping generic UI, text, and AI-shaped code.
A filter, not a style guide. No prescribed colors, fonts, or layouts, and direction stays yours.
Before and after · Install · What it does · Skills · FAQ
npx antislop-ai
Before and after
Each pair below is one brief, run twice, so the difference is visible side by side.
UI
With /antislop-ui. antislop alone is not the after. It removes the slop and stops there; direction comes from DESIGN.md. For UI work you intend to ship, that file is mandatory: without it the result is labelled a draft without direction. The pair below is the result.
| Before: without antislop | After: antislop + DESIGN.md |
|---|---|
| This is what most AI output looks like: slop everywhere once you take a closer look. | Much better. antislop kills the slop, and DESIGN.md gives it a real visual direction. |
The two partial states are worth seeing, because each one shows why the other half matters:
| Partial: antislop alone | Partial: DESIGN.md alone |
|---|---|
The slop is gone, but so is the direction. That is why antislop needs a DESIGN.md. | The direction is there, but honestly it is still far from good: the slop still shows. |
Copywriting
With /antislop-copywriting. One prompt, run twice.
Accessibility
With /antislop-human. One sign-in form, run twice.
Mobile layout
With /antislop-layoutmobile. One dashboard on a phone, run twice.
Code
With /antislop-code. One file, run twice.
Every image here opens full size if you click it.
Install
antislop ships as standard agent skills: one folder per skill, holding a SKILL.md. Installation differs per agent, so pick the section for the one you use. Each route is walked through from zero, with update and removal, in GUIDE.md.
The installer (recommended)
One command, then answer the prompts. It asks which skills you want, where to install them (this project or everywhere), and which agents you use, then copies the folders and writes the pointer that reloads antislop every session.
npx antislop-ai
The skills directory
antislop is listed on skills.sh, the open directory for agent skills. This copies the same folders as the installer and nothing else, so antislop reloads by description alone.
npx skills add miqdadbadjuber/anti-slop
Claude Code - Plugin
/plugin marketplace add https://github.com/miqdadbadjuber/anti-slop
/plugin install antislop@anti-slop
Antigravity - Plugin
agy plugin install https://github.com/miqdadbadjuber/anti-slop
Codex - Plugin
codex plugin marketplace add miqdadbadjuber/anti-slop
codex plugin add antislop@anti-slop
Cursor - Plugin
agent plugin marketplace add https://github.com/miqdadbadjuber/anti-slop
Then open Customize, find antislop, and select Install.
Kimi Code - Plugin
/plugins install https://github.com/miqdadbadjuber/anti-slop
DeepSeek Harness - Plugin
Open Plugins, choose Add plugin, paste this package name, and select Install:
antislop-ai
That is the desktop route. From a terminal instead, name the profile you use:
dsh plugin --profile desktop add antislop-ai
Cline - Plugin
cline plugin install https://github.com/miqdadbadjuber/anti-slop.git
This door covers the Cline CLI. For the VS Code or JetBrains extension, use the installer.
Muse Code - Plugin
Muse Code keeps its plugin system behind an opt-in flag, so set it first. On macOS and Linux:
export MUSE_EXPERIMENTAL_PLUGINS=1
muse plugins marketplace add anti-slop miqdadbadjuber/anti-slop
muse plugins install antislop@anti-slop
On Windows, set $env:MUSE_EXPERIMENTAL_PLUGINS = "1" in PowerShell first, then run the two muse lines unchanged.
Skills load without anoth
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/antislop/SKILL.md7.8 KBupstream ↗
--- name: antislop description: "Anti Slop: Rules for AI Coding Agents. The core filter. Load always to stop generic AI slop." allowed-tools: Read Write Edit Glob Grep --- # antislop > Anti Slop: Rules for AI Coding Agents > Follow these rules whenever generating or building UI for a website, web app, or any interface. > The goal: the design should feel **crafted by a designer**, not generated by AI. > Before applying antislop, resolve its mode using "Two Usage Modes" below. By default, ask during or after. For a saved preference or explicit session choice, instead announce `antislop active: <mode> (<source>).` once, including whether the source is `global preference` or `session override`. --- ## First-Run Install Wizard antislop is a system: this core file plus optional **skills**, one per concern (`antislop-ui`, `antislop-copywriting`, and so on, each a folder with a `SKILL.md`). This section installs them once. It is an **offer, not a requirement**: if the user prefers, this file alone remains a complete filter. **Skip this section** if the project's entry file (`AGENTS.md`, `CLAUDE.md`, `GEMINI.md`, or the equivalent the running tool reads at session start) already contains an antislop pointer block. That means antislop is already installed. Come back only when the user asks to add or remove a skill. If no antislop pointer exists and this file is being read for the first time, run the wizard: > The steps below are the manual install for setups where only this file is present. No network is used: missing skills are fetched by the user, never by the agent. 1. **Declare the setup before doing anything.** Tell the user you will (a) get the chosen skill(s) in place in `skills/<name>/` subfolders next to this file (the user fetches them; the agent never downloads from the network, see step 4), and (b) append an antislop pointer block at the end of the project's entry file. Get approval. Never modify the entry file silently. 2. **Ask which skills to install** (multi-select, in the user's chat language). List only the skills that exist in this version of antislop: - **1. All** (recommended): install every available skill. Choose this when the work spans UI, copy, people, or mobile layout. - **2. `antislop-ui`** (UI / visual): pick this for building or editing a website, web app, or interface: color, layout, components, decoration, motion. - **3. `antislop-copywriting`** (copy & text): pick this for writing or editing copy: headlines, CTAs, value propositions, tone, landing-page text, product prose. - **4. `antislop-human`** (people): pick this for making sure a UI works for people with different eyes, hands, and setups: contrast, keyboard, focus, states. - **5. `antislop-layoutmobile`** (mobile / responsive): pick this for layouts that have to reflow across screen sizes, phone to desktop: breakpoints, scale, grids, overflow, tap targets. - **6. `antislop-code`** (code comments): pick this for writing or editing code comments: remove generic AI-slop comments, keep the valuable ones, never touch the code. - New skills appear here as they ship; never offer a skill that does not exist in this version. If the user declines or says "core only", stop here and use this file alone as the filter. Do not install anything. 3. **Resolve direction** (only if a UI skill was selected). Check for `DESIGN.md` or explicit brand/style direction. If none exists, be honest that antislop is a **filter, not a beautifier**: without direction the output tends toward monotonous. Recommend having a `DESIGN.md`, then offer these paths: - **1. The user supplies direction (recommended).** They write their own `DESIGN.md`, or answer a few direction questions (identity, personality, palette, typography, mood) and the agent transcribes their answers into `DESIGN.md`. The user is the author; the agent only formats. Never invent example content for `DESIGN.md`. - **2. The agent supplies direction, with an honest warning.** The agent writes the direction itself, stating explicitly that agent-generated style tends toward default AI taste, which is the slop antislop filters, so the result is likely monotonous. If chosen, still ask a minimal brief (product, audience, mood) before building. - **3. The user skips direction for now.** Proceed without a `DESIGN.md`. Any UI built this way must be labeled *"draft without direction"* with dials ENERGY 1 / RHYTHM 1 / MOTION 1 (R-37), and is not a shippable deliverable. 4. **Get the chosen skill(s) in place; the user does the fetching, never the agent.** A `SKILL.md` is instructions the agent will obey, so an agent that downloads one at runtime is fetching its own next prompt: do not do it, and do not ask for network access here. The skills ship as folders in the release (`skills/<name>/SKILL.md`). If a chosen skill folder is missing next to this file, tell the user which ones are missing and that they come with the release matching this core, so a newer skill never mixes with an older one. `antislop-human` also needs `contrast-check.py` from that same folder. 5. **Append the pointer block at the END of the project's entry file** (the file the running tool reads at session start: `CLAUDE.md` for Claude Code, `AGENTS.md` for Codex, `GEMINI.md` for Gemini CLI, and so on). If that file does not exist, create it. Never modify existing content: ```md <!-- antislop:start --> ## antislop For UI, copy, people, mobile layout, or code comments work, read `antislop.md` (core) and then the skill for the task: - UI / visual: `skills/antislop-ui/SKILL.md` - Copy & text: `skills/antislop-copywriting/SKILL.md` - People: `skills/antislop-human/SKILL.md` - Mobile / responsive: `skills/antislop-layoutmobile/SKILL.md` - Code comments: `skills/antislop-code/SKILL.md` Before starting, follow the core's "Two Usage Modes" section in strict order: explicit session instruction first, then global preference, then ask. A session instruction always wins. For a resolved mode, say `antislop active: <mode> (session override).` or `antislop active: <mode> (global preference).` once before presenting findings or making edits, using the actual mode and source. Acknowledging the user's request without naming the source does not replace this notice. Only an explicit choice of antislop during or after selects a session mode. A request to review, audit, or avoid file edits does not select a mode; read the global preference in that case. Another skill's mode does not select antislop's mode. If the mode is unresolved, ask during/after and end the response; wait for the answer before any UI review, planning, or concept. For read-only tasks, put the active-mode notice only at the start of the final answer, never in progress messages. For editing tasks, announce before the first edit and omit it from the final answer. To update antislop later: download `antislop.md` again, or run `npx antislop-ai --update` if it was installed as skill folders. <!-- antislop:end --> ``` The packaged installers write the same two markers, so whichever install path runs last replaces the block instead of adding a second one. If an older antislop block exists (even without the markers), replace just that block instead of appending a duplicate. 6. **Resolve and announce the usage mode** (see "Two Usage Modes"), then proceed with the work. Notes: - The entry file is read at the start of a session, so a newly written pointer takes effect from the **next** session. - The wizard needs file-write access for step 5 (the pointer block) and nothing else to install; the user approves once. A `DESIGN.md` in step 3 and an audit report in Mode 2 are written separately, only when the work calls for them. It never needs network access. - The pointer block is the source of truth for which skills are installed. To add or remove a skill later, update the block to match (add or remove the file and its line). ### Already installed, and the uREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/miqdadbadjuber-anti-slop-skills-antislop.md