/anti-slop

name: anti-slop
description: Comprehensive toolkit for detecting and eliminating "AI slop" - generic, low-quality AI-generated patterns in natural language, code, and design. Use when reviewing or improving content quality, preventing generic AI patterns, cleaning up existing content, or enforcing quality standards in writing, code, or design work.

Anti-Slop Skill

Detect and eliminate generic AI-generated patterns ("slop") across natural language, code, and design.

What is AI Slop?

AI slop refers to telltale patterns that signal low-quality, generic AI-generated content:

• **Text**: Overused phrases like "delve into," excessive buzzwords, meta-commentary
• **Code**: Generic variable names, obvious comments, unnecessary abstraction
• **Design**: Cookie-cutter layouts, generic gradients, overused visual patterns

This skill helps identify and remove these patterns to create authentic, high-quality content.

When to Use This Skill

Apply anti-slop techniques when:

• Reviewing AI-generated content before delivery
• Creating original content and want to avoid generic patterns
• Cleaning up existing content that feels generic
• Establishing quality standards for a project
• User explicitly requests slop detection or cleanup
• Content has telltale signs of generic AI generation

Core Workflow

1. Detect Slop

**For text files:**

python scripts/detect_slop.py <file> [--verbose]

This analyzes text and provides:

• Slop score (0-100, higher is worse)
• Specific pattern findings
• Actionable recommendations

**Manual detection:** Read the appropriate reference file for detailed patterns:

• `references/text-patterns.md` - Natural language slop patterns
• `references/code-patterns.md` - Programming slop patterns
• `references/design-patterns.md` - Visual/UX design slop patterns

2. Clean Slop

**Automated cleanup (text only):**

# Preview changes
python scripts/clean_slop.py <file>

# Apply changes (creates backup)
python scripts/clean_slop.py <file> --save

# Aggressive mode (may slightly change meaning)
python scripts/clean_slop.py <file> --save --aggressive

**Manual cleanup:** Apply strategies from the reference files based on detected patterns.

Text Slop Detection & Cleanup

High-Priority Targets

**Remove immediately:**

• "delve into" → delete or replace with "examine"
• "navigate the complexities" → "handle" or delete
• "in today's fast-paced world" → delete
• "it's important to note that" → delete
• Meta-commentary about the document itself

**Simplify wordy phrases:**

• "in order to" → "to"
• "due to the fact that" → "because"
• "has the ability to" → "can"

**Replace buzzwords:**

• "leverage" → "use"
• "synergistic" → "cooperative"
• "paradigm shift" → "major change"

Quality Principles

**Be direct:**

• Skip preambles and meta-commentary
• Lead with the actual point
• Cut transition words that don't add meaning

**Be specific:**

• Replace generic terms with concrete examples
• Name specific things instead of "items," "things," "data"
• Use precise verbs instead of vague action words

**Be authentic:**

• Vary sentence structure and length
• Use active voice predominantly
• Write in a voice appropriate to context, not corporate-generic

Code Slop Detection & Cleanup

High-Priority Targets

**Rename generic variables:**

• `data` → name what data it represents
• `result` → name what the result contains
• `temp` → name what you're temporarily storing
• `item` → name what kind of item

**Remove obvious comments:**

# Bad
# Create a user
user = User()

# Better - let code speak
user = User()

**Simplify over-engineered code:**

• Remove unnecessary abstraction layers
• Replace design patterns used without purpose
• Simplify complex implementations of simple tasks

**Improve function names:**

• `handleData()` → what are you doing with data?
• `processItems()` → what processing specifically?
• `manageUsers()` → what management action?

Quality Principles

**Clarity over cleverness:**

• Write code that's easy to understand
• Optimize only when profiling shows need
• Prefer simple solutions to complex ones

**Meaningful names:**

• Variable names should describe content
• Function names should describe action + object
• Class names should describe responsibility

**Appropriate documentation:**

• Document why, not what
• Skip documentation for self-evident code
• Focus documentation on public APIs and complex logic

Design Slop Detection & Cleanup

High-Priority Targets

**Visual slop:**

• Generic gradient backgrounds (purple/pink/cyan)
• Overuse of glassmorphism or neumorphism
• Floating 3D shapes without purpose
• Every element using same design treatment

**Layout slop:**

• Template-driven layouts ignoring content needs
• Everything in cards regardless of content type
• Excessive whitespace without hierarchy
• Center-alignment of all elements

**Copy slop:**

• "Empower your business" type headlines
• Generic CTAs like "Get Started" without context
• Buzzword-heavy descriptions
• Stock photo aesthetics

Quality Principles

**Content-first design:**

• Design around actual content needs
• Create hierarchy based on importance
• Let content determine layout, not templates

**Intentional choices:**

• Every design decision should be justifiable
• Use patterns because they serve users, not because they're trendy
• Vary visual treatment based on element importance

**Authentic voice:**

• Copy should reflect brand personality
• Avoid generic marketing speak
• Be specific about value proposition

Reference Files

Consult these comprehensive guides when working on specific domains:

• **[text-patterns.md](references/text-patterns.md)** - Complete catalog of natural language slop patterns with detection rules and cleanup strategies

• **[code-patterns.md](references/code-patterns.md)** - Programming antipatterns across languages with refactoring guidance

• **[design-patterns.md](references/design-patterns.md