---
name: remove-ai-slops
description: Cleanup workflow for AI-generated bloat, vague wording, fake certainty, overbroad abstractions, and unsupported claims in LazyClaude code and docs.
---

# Remove AI Slops

Use this skill when output feels padded, generic, or less precise than the
system it describes. The cleanup must be behavior-preserving unless paired with
a test for a behavior change.

## Slop Signals

- Grand claims without an observable command.
- "Seamless", "robust", or "powerful" without concrete behavior.
- Repeated caveats in every section.
- Large abstractions with only one caller.
- Tests that assert exact prose but not policy.
- Docs that say a feature exists when the runtime only has guidance.
- Placeholder-like skills that omit the actual workflow.

## Cleanup Rules

- Replace hype with commands, paths, and expectations.
- Replace vague "verify it works" with exact test and QA scenario.
- Delete duplicate warnings once the actionable warning remains.
- Keep constraints that protect users from publish, destructive commands, and
  secret exposure.
- Do not remove useful nuance about Claude Code vs source runtime surfaces.

## LazyClaude Hotspots

Check:

- `README.md` and `README_ko-KR.md` for version drift.
- `docs/hooks.md` for noisy fallback wording.
- `plugins/lazyclaude/skills/*/SKILL.md` for shallow placeholders.
- `plugins/lazyclaude/commands/*.md` for broken `$ARGUMENTS`.
- `bin/lazyclaude-ai.js` for one-off helper bloat.
- `test/*.test.mjs` for brittle prose pins.

## Verification

Run tests after cleanup. For docs-only cleanup, docs tests are enough for
automated evidence, but a package dry-run is useful when the README command or
published package surface changed.

## Output Style

Summarize removed slop by category, not by every sentence. If a section was
intentionally left verbose because it encodes a workflow, say so.

