antislop skill
A rule set for coding agents that filters out generic AI look in UI, copy and code comments
- 8,991 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The plugin registers the local antislop-contrast MCP server for contrast checks
- The accessibility module ships contrast-check.py and contrast-mcp.py scripts
- The npx antislop-ai installer copies skills and edits the project entry file
Install
- Works in
Manual install
npx antislop-aiThe installer asks which skills to install, project or global and for which agents, then copies the folders and writes the pointer into the project entry file.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The plugin registers the local antislop-contrast MCP server for contrast checks
- The accessibility module ships contrast-check.py and contrast-mcp.py scripts
- The npx antislop-ai installer copies skills and edits the project entry file
This is third-party code. Review the repository files before installing.
What it does
The skill gives the agent a rule set against a typical AI look and hooks into work on UI, copy or comments. The antislop core is a single filter file usable on its own, with optional skills loaded per concern: UI, copywriting, accessibility for different people, mobile layout, code comments. The accessibility skill checks contrast. The skill is honest that it is a filter, not a style generator, and that without a direction in DESIGN.md the output tends toward monotony.
Who it is for. For designers and developers who build UI and copy with an agent and do not want a template AI result.
Good fit when
- The agent builds UI and it comes out generic
- You need to strip template phrasing from landing copy
- You need to remove typical AI comments from code without touching the logic
Not a fit when
- You have no style direction and do not care: the filter without DESIGN.md yields monotony
- The task is backend logic, not UI look or copy
Example request
Apply antislop to this landing page: remove the template AI look and cliches in the copyLimitations
antislop is a filter, not a source of design: without a DESIGN.md or stated direction it makes the look cleaner but does not set a character. The full set is several skills; the core can be used on its own.
How to disable. Remove the antislop plugin via /plugin or the antislop skill folders from the agent's skills directory, and delete the antislop pointer block from the project entry file.
FAQ
Is the core file enough?
Yes, the antislop.md core works as a full filter on its own; extra skills are added per concern.
Will it invent a style?
No. The skill states plainly that it is a filter, and direction is better set in a DESIGN.md, otherwise the result is monotonous.
How is antislop different from just asking an agent to avoid templates?
It is a rule set against the typical AI look. The core is a single filter file usable alone, and extra modules plug in for interfaces, text and code comments.
How do I install antislop and what does it give an agent?
The command npx antislop-ai plugs the rules into Claude Code, Codex, Cursor, Copilot or OpenCode. The agent applies them while working on interfaces, text or comments and filters out template patterns.
Discussion
No questions or reviews yet.
Related
SkillsA skill for interfaces without the generic AI look: typography, color, motion, component states and a critique of the result.
A skill that strips explanatory copy from interfaces: nine rules, before and after output, precise verbs for generic ones.
Finds AI-look tells in generated frontend, from purple gradients to cream and terracotta, and rewrites the interface
An interface design skill for the agent: diagnosis, four directions to choose, implementation and QA without an AI-template look
A UI design skill: art direction per product, a shared DESIGN.md, tokens, and layout and accessibility checks in a browser.
A skill that bans the stock AI interface with floating cards, gradients and glass and sets plain sizes, radii and shadows like Linear
README in short
The README describes antislop as a set of standard skills, one folder with a SKILL.md per concern, where the core always loads and the rest load on demand. Install runs via the npx antislop-ai installer, the skills directory route npx skills add, or as a plugin for Claude Code, Codex, Cursor, Antigravity and Kimi Code, and the core can be pasted into any chat. It maps project and global paths across agents, with update and remove sections. MIT licensed.
README badge
Original SKILL.md
--- 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 any UI work, ask the user (in their chat language) when antislop applies: during the work, or after it is done. Do not start until they answer. --- ## 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: