# kill-ai-slop — an Agent Skill

Scan a web project for **AI slop**, the generic machine-default visual and copy
tics of vibe-coded products, and strip it out. This skill turns the catalogue at
**[killaislop.com](https://killaislop.com)** into action: it detects 35 tells
from their code-level signals, explains why each reads as machine-made, and
proposes or applies the clean fix.

It covers indigo→violet gradients, gradient-clip headlines, the default semantic
palette, one-hue status boxes, atmospheric background gradients, serif-italic
emphasis, decorative strikes/highlights, highlighted keywords, AI copywriting
voice, emoji spam, glowing status dots, colored-left-border callouts, pastel
icon tiles, glassmorphism and over-rounding, oversized drop shadows, corners
that don't nest, borders that die at rounded corners, badge & pill spam,
AI-drawn SVG icons, icon-in-a-tint-of-itself
tiles, kickers over every heading, full-sentence display headlines, flat type
hierarchies, springy hover effects, wobbling off-centre spinners, all-caps
stat-card grids, invented stat
rows, 01/02/03 section markers, cards nested in cards, monotone one-gap
spacing, the default Inter/Space Grotesk look, the "tasteful terminal"
default, and the editorial-serif dashboard costume. It works across
HTML/CSS, React/Vue/Svelte/Astro, Tailwind, PHP/Twig
templates (WordPress themes and plugins included), and Markdown copy.

## Install — just ask your agent

This is an [Agent Skill](https://docs.claude.com/en/docs/agents-and-tools/agent-skills/overview).
You don't need to configure anything by hand. Tell your coding agent, in plain
language, to fetch it from this repo and install it wherever that agent keeps
its skills. Paste something like this:

```
Install the kill-ai-slop skill from
https://github.com/yetone/kill-ai-slop/tree/main/skill

Copy everything in that directory into a kill-ai-slop/ folder
inside your agent's skills directory, then confirm it's registered.
```

You don't have to name the files or spell out the path. Your agent knows where
its own skills live and copies the whole directory in as it is. (Claude Code,
for example, reads `.claude/skills/` in the project, or `~/.claude/skills/` to
have it everywhere; other agents have their own location.) The agent reads
`SKILL.md`, installs the skill, and registers it.

## Install — manually

If you'd rather do it yourself, clone the repo and copy the whole `skill`
directory into wherever your agent reads skills from, under the name
`kill-ai-slop`:

```bash
git clone https://github.com/yetone/kill-ai-slop

# copy the entire directory; for example, with Claude Code:
cp -r kill-ai-slop/skill ~/your-project/.claude/skills/kill-ai-slop   # this project only
cp -r kill-ai-slop/skill ~/.claude/skills/kill-ai-slop                # every project
```

Copy the directory whole; the skill is self-contained, with no packages and no
build step. Swap the destination for your own agent's skills folder if it isn't
Claude Code.

## Use it

Once installed, ask your agent:

> Kill the AI slop in this project.

(or "de-slop this", "remove the AI look", "make this not look AI-generated"). It
will **scan** the code for each tell, **triage** slop vs. a real chosen design,
**report** a grouped summary before touching anything, and **fix** only the
groups you approve, with the smallest diff that removes the tell without
changing intent.

You can also run the scanner on its own; it only reads, never edits:

```bash
node scripts/scan.mjs path/to/src          # human-readable report
node scripts/scan.mjs path/to/src --json   # machine-readable
```

Every hit is a lead to confirm by reading the code, not a verdict. A gradient, a
serif, or an emoji can be a real, defended choice. The skill flags defaults and
keeps anything you clearly decided.

For hits you've confirmed as intentional, and for narrower scans, the scanner
supports:

```bash
node scripts/scan.mjs src --only=01,06        # scan just these tells
node scripts/scan.mjs src --skip=19,26        # everything but these
node scripts/scan.mjs src --exclude=legacy    # drop paths (substring match)
node scripts/scan.mjs src --rules=my.mjs      # load extra project/language tells
```

and comment directives in source: `deslop-ignore` (this line),
`deslop-ignore-next-line`, and `deslop-ignore-file` — each optionally scoped to
tell ids, e.g. `/* deslop-ignore-next-line 06 */`. Prefer the id-scoped forms so
new tells still surface. `scripts/rules.ru.mjs` ships as a working example of a
`--rules` module (Russian AI-copywriting tells) and the template for your own
language- or stack-specific rules.

## What's inside

| File | |
|---|---|
| `SKILL.md` | The skill definition, workflow, and guardrails. |
| `references/taxonomy.md` | The 35 tells: what each is, why it's slop, the fix. |
| `references/detection.md` | The code patterns per tell, and their false positives. |
| `references/fixes.md` | Before→after remediation patterns. |
| `scripts/scan.mjs` | The dependency-free scanner. |
| `scripts/rules.ru.mjs` | Example `--rules` module: Russian copy tells. |