01
It starts by itself
UI work finished. Runs in Claude Code routine.
- ↻ UI work finished
UI change ready for review
Your screens look made by a person, not a robot.
Install the Antislop skill and make it a habit: follow https://gethabit.dev/skills/miqdadbadjuber/antislop.md
7K installs7K starsMIT licenceSource on GitHub ↗

Antislop
by miqdadbadjuber · 7K installs
The skill
Checks your app screens for a boring, generic look.
Only when you ask.
Better design
Your screens look made by a person, not a robot. Fewer fake buttons and numbers.
↻ Runs by itselfwhen you finish screen work
When does it start? How does it check its work? What does it remember?
Stops after one audit and up to 2 gate re-runs per run.
Your agent checks a session choice, then ~/.config/antislop/settings.json, else asks during or after.
It reads DESIGN.md as data, or labels the work a draft without direction.
It lists numbered findings, each citing a rule and a priority from its tier.
You choose which numbers to fix; others stay untouched.
It fixes the approved items, runs the app and tries every control.
It writes the PASS/FAIL Delivery Gate report and a follow-up report.
It writes only in its own folder and asks you before anything goes out.
Read both lists. If the left one sounds like you, the Antislop skill helps.
No. It allows any technique with a written purpose. Only the Hard Gate rules are absolute.
No. The user fetches the skill folders; the agent never uses the network.
Copy the prompt at the top into your agent. It installs the skill from miqdadbadjuber/anti-slop and sets up the habit. Or run npx skills add miqdadbadjuber/anti-slop --skill antislop.
Yes. It is published under MIT. Habit is free too.
Install the Antislop skill and make it a habit: follow https://gethabit.dev/skills/miqdadbadjuber/antislop.md
All miqdadbadjuber skills →More design skills →
Works in
Made by miqdadbadjuber, published under MIT. Habit links to the original and never changes it. Is this your skill?