New Claude Skill: Stop Slop
AI experiments
AI writing has tells. “Here’s the thing.” “Let that sink in.” “The uncomfortable truth is.” Once you notice them, you see them everywhere.
I built Stop Slop to fix this. It’s a skill file that teaches Claude to avoid these patterns.
Download the skill: Stop Slop
Catching slop in content
Here's the thing: building great products is hard. It turns out that most teams struggle with alignment, communication, and execution. Not because they lack talent. Because they lack clarity. The best teams lean into discomfort and navigate the complex landscape of product development with purpose. Let that sink in.
The uncomfortable truth is that most product advice is generic. People tell you to "move fast" and "talk to users" without unpacking what that actually means. Let me be clear: speed without direction is just chaos. And that's okay. Every team goes through this phase. What matters is recognizing it early. This matters because your competition isn't waiting around.
So what's the answer? Focus on three things: clarity, speed, and trust. Clarity. That's it. That's the foundation. When your team knows exactly what they're building and why, everything else follows. The real unlock is getting everyone aligned before you write a single line of code. I'm going to be honest — most teams skip this step. Full stop.
The uncomfortable truth is that most product advice is generic. People tell you to "move fast" and "talk to users" without unpacking what that actually means. Let me be clear: speed without direction is just chaos. And that's okay. Every team goes through this phase. What matters is recognizing it early. This matters because your competition isn't waiting around.
So what's the answer? Focus on three things: clarity, speed, and trust. Clarity. That's it. That's the foundation. When your team knows exactly what they're building and why, everything else follows. The real unlock is getting everyone aligned before you write a single line of code. I'm going to be honest — most teams skip this step. Full stop.
Content with slop · Content with slop highlighted
Here’s how to use it
- Claude Code: Add
stop-slop.mdas a skill file. - Claude Projects: Upload it to your project knowledge.
- Cursor: Add the rules to your
.cursorrulesfile or paste into the system prompt.
What it catches
- Phrases like “Here’s the thing:”, “Let that sink in.”, “This matters because”, “Navigate” (for challenges), “Unpack” (before analysis).
- Structures like “Not because X. Because Y.”, “[Noun]. That’s it. That’s the [thing].”, “And that’s okay.”
- Habits like tripling (always three examples), answering questions right after asking them, starting with “So” or “Look,”, ending every section with a punchy one-liner.
Scoring
- Score your draft 1-10 on directness, rhythm, trust, authenticity, and density.
- Below 35/50 means revise.
MIT licensed.