---
name: remove-ai-slop
description: Remove generic AI residue, awkward generated patterns, default aesthetics, unnecessary complexity, and unearned polish from writing, interfaces, visual creative, prompts, code, and technical systems. Use when the user asks to de-slop, de-AI, humanize, simplify, remove AI tells or cliches, reduce generated clutter, or preserve the idea while making the execution more specific and intentional. Do not claim to detect AI authorship.
---

# Remove AI Slop

Remove choices that feel generated by default rather than chosen for this particular work. The result should feel more specific and intentional, not merely shorter, rougher, or less polished.

## Establish The Contract

Identify:

- what the artifact is trying to accomplish;
- who will use or experience it;
- its intended voice and level of formality or density;
- facts, behavior, constraints, disclosures, and distinctive choices that must survive;
- whether the user wants an audit, a revision, or an implemented change.

If the source is already strong, make few or no changes.

## Shared Slop Signals

Treat these as evidence to investigate, not proof of AI authorship:

- language or styling that could move unchanged to many unrelated artifacts;
- unnecessary structure, containers, qualifiers, features, or abstraction;
- simulated sophistication, personality, empathy, or cinematic prestige;
- symmetry or comprehensiveness that feels templated rather than useful;
- default metaphors, icons, gradients, layouts, naming, or architecture with no local reason;
- polish that flattens voice, texture, asymmetry, product character, or domain specificity.

## Workflow

1. Mark the specific choices that weaken the artifact.
2. Separate necessary complexity from generated-looking residue.
3. Delete what carries no meaning, behavior, evidence, or character.
4. Clarify, merge, demote, or replace what has a real job but a generic execution.
5. Strengthen concrete nouns, direct actions, local conventions, hierarchy, and context-specific detail.
6. Preserve deliberate oddness, useful density, and authored texture when they serve the work.
7. Recheck the whole artifact so local fixes do not create a new generic style.

Prefer the smallest coherent pass. Do not expand scope into a general rewrite, redesign, or refactor unless the user asks.

## Preserve Truth And Trust

Do not change facts, claims, identifiers, APIs, contracts, disclosures, accessibility, or system behavior casually. Do not invent experience, evidence, capability, or emotional texture. Do not conceal automation in a misleading way. Surface substantive changes separately instead of smuggling them into cleanup.

## Verify In The Native Medium

Read prose as a whole. Render and operate interfaces. Inspect visual creative at delivery size. Run focused checks for code. Passing code checks are not visual proof.

## Final Test

- Could this choice appear unchanged in a thousand unrelated generated artifacts?
- Does it have a present-tense job here?
- Is the result more specific to this author, product, audience, and situation?
- Did the pass preserve truth, capability, voice, and useful character?

If a choice is generic and expendable, remove it. If it has a real job, make it belong.