Slop Coding: When Vibe Coding Skips Code Quality
Vibe coding is a workflow. Slop coding is that workflow without a bar.
Slop coding is what happens when AI generated code moves faster than code quality. People also search AI slop coding and AI coding slop. The useful name is the workflow failure, not an insult for using an agent.
Vibe coding vs slop coding
Vibe coding: describe the change, let the agent edit, ship if the bar holds. Slop coding: skip the bar. Tests that only assert mocks, no scan for AI slop, a PR too large to read, merge anyway.
The fix is not to ban agents. It is a code quality loop: small contract, tests, deterministic scan, human pass on intent. Longer writeup: vibe coding quality workflow.
A minimum bar
- One requested behavior per patch
- A test that fails if that behavior is removed
npx aislop scan --changesbefore review- CI that fails below your score threshold
That is enough to stop most slop coding without slowing a careful vibe-coding session.
Frequently asked questions
What is slop coding?
Slop coding is generating AI code and merging it without a code quality check for AI slop. The feature may work. The repo still takes on residue.
Is slop coding the same as vibe coding?
No. Vibe coding is prompting an agent to write code. Slop coding is skipping tests, scan, and review after that. You can vibe code without shipping slop.
How do I vibe code without slop coding?
Keep patches small, require tests that prove the request, run npx aislop scan, then review intent. See the vibe coding quality workflow on this site.