DeSlop

Make your app stop looking AI-generated. A Claude skill that audits a UI for the tells of genAI slop — stock purple gradients, template landing pages, "Effortlessly unleash 🚀" copy — then restyles the app around a real design direction until it feels hand-crafted by someone with taste.

Built by @the.jacked.dev. Free. MIT.

The premise

Slop isn't ugliness. It's the statistical average of every app: defaults with no decisions behind them, recognizable at a glance because you've seen it a thousand times. DeSlop's core rule is that removal is not the product — intent is. Swapping the purple gradient for a teal one is new slop; the fix is a written design direction that every choice traces back to.

How it works

Five phases:

1. Absorb — runs and screenshots the app if it can, maps screens and the token layer, reads any taste doc or brand guidance you have, and figures out what the product is (a ledger and a recipe app shouldn't converge on the same look).
2. Audit — sweeps three catalogs and collects findings with file:line: visual (gradient text, glassmorphism-everywhere, elevation soup, emoji-as-icons, no type scale), copy ("Supercharge", exclamation-mark UI, fabricated testimonials, copy-pasted empty states), structure (the hero→features→testimonials→pricing template, the four-stat-tile dashboard, cards-in-cards, everything-centered).
3. Direction — writes a half-page design brief: three character words derived from the product, one bold move everything else stays quiet around, and a full token spec. This is the checkpoint — you approve the direction before anything changes. Or skip the invention entirely: hand it a theme pack (a token file + rules doc + exemplar screen) and that becomes the pre-decided direction — DeSlop maps the pack onto your app, flags conflicts with existing brand equity, and the pass becomes theme application.
4. Restyle — tokens first, then shared components, then screen by screen. Style-only diffs; nothing bypasses the token system.
5. Verify — re-runs the audit on the result, before/after screenshots, a cohesion pass across all screens, and the squint test: if the result could be any app in its category, it goes back to the brief.

On bigger apps it orchestrates subagents — parallel visual/copy/structure auditors, per-screen restylers working from the shared brief, and a fresh-eyes cohesion reviewer at the end. Taste itself is never delegated: one mind writes the brief.

What it won't do

• Redesign your information architecture or touch functionality — the diff is reviewable as "same app, different hands."
• Erase real brand equity. An existing logo color or typeface is a constraint to design around, often the seed of the bold move.
• Apply its own house style. The direction comes from your product and taste docs; DeSlop brings the method.

Install

git clone https://github.com/nate-zz/DeSlop.git ~/.claude/skills/deslop

Or add it to a single project at .claude/skills/deslop/.

Then, in Claude Code:

/deslop

…or just ask: "this looks AI-generated, fix it," "deslop this app," "make the UI feel hand-crafted."

Layout

SKILL.md               the method (absorb → audit → direction → restyle → verify) + subagent orchestration
references/
  visual.md            visual slop catalog — color, effects, shape, type, icons, motion
  copy.md              copy slop catalog — hype vocabulary, tone tells, microcopy craft
  structure.md         layout slop catalog — template pages, component overuse, hierarchy
  craft.md             the playbook for what "hand-crafted" concretely means

The one rule

A crafted UI is a small number of strong decisions applied everywhere. Slop is a large number of defaults applied inconsistently. DeSlop moves an app from the second category to the first.