unslop: Fix AI-Looking UI With One Command

A Claude Code skill called unslop, built by designer Damir Sokolovsky (@heydamir), reached over 6,500 GitHub stars in five days and hit number one on JavaScript trending on October 31. The skill audits a screen for 16 catalogued AI design tells — such as purple-to-blue gradients, emoji labels, and Inter typography — before proposing a design direction, then fixes them across nine sequential passes covering spacing, color, icons, copy, typography, layout, details, visuals, and motion. A 2026 Developers Digest study found 22% of surveyed AI-built pages triggered four or more of those 16 patterns, and unslop works with Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and Copilot across React, Next.js, Vue, Svelte, Tailwind, and plain HTML/CSS.

A Claude Code skill called unslop accumulated over 6,500 GitHub stars in five days — hitting number one on JavaScript trending on October 31. The reason it blew up is simple: every developer who has shipped a vibecoded project knows the feeling. The app works, the features are solid, and the UI unmistakably looks like AI built it. The Slop Problem Has 16 Known Tells The AI aesthetic is not random. It converged on a specific visual language because the training data was dominated by Notion, Linear, Vercel, and the hundreds of startups that cloned their aesthetic. When you ask a coding agent to “make it look good,” it reaches for what “forward-looking and technical” meant in its training data. That means purple-to-blue gradients, glowing card borders, gradient text, emoji in labels, pulsing animated elements, and Inter at every type scale. A 2026 study by Developers Digest catalogued 16 recurring patterns — what they call AI design slop https://www.developersdigest.tech/blog/ai-design-slop-and-how-to-spot-it — and found that 22% of surveyed AI-built pages triggered four or more of them. The problem is not that individual developers have bad taste. It is that every coding agent reaches for the same defaults, and the web is starting to look like it was designed by committee. What unslop Does Differently The skill was built by Damir Sokolovsky @heydamir https://x.com/heydamir/status/2116158176336970008 , a designer who spent months sharing UI teardowns in his “Unslopping” series on X. The original vibecoded dashboard post hit roughly one million views before he packaged the process as a Claude Code skill. The critical design decision in unslop is that it audits before it edits . Most “polish my UI” prompts go straight to rewriting code, and you end up with something that looks different but still generic. unslop reads your existing screen, lists every slop tell with where it lives, and then proposes a design direction — not a generic redesign, but a direction derived from what is already in your product. You approve the direction before it touches a single component. If the screen is already well-designed, it says so and suggests small refinements only. Nine Passes, Strict Order The actual fixing happens across nine sequential passes. Order matters — fixing color before spacing means you redo color when spacing shifts the layout. 1. Spacing — padding, margin, and alignment consistency 2. Color — eliminate gradient defaults, normalize the palette 3. Icons — replace emoji labels, normalize the icon system 4. Copy — remove generic placeholder text 5. Typography — fix the Inter monoculture, normalize the type scale 6. Layout — restructure grid, hierarchy, and visual flow 7. Details — borders, shadows, and border-radius consistency 8. Visuals — show the actual product, not a glossy marketing blob 9. Motion — remove pulsing glow effects Each pass runs across the whole screen before the next one starts. This is not “describe what you want and hope.” It is a system. Installation and Usage Installation is two commands. Clone the repo and copy the skill folder into your Claude skills directory: git clone https://github.com/heydamir/unslop mkdir -p ~/.claude/skills && cp -r unslop/skills/unslop ~/.claude/skills/ For a single project, copy into .claude/skills/ inside that project directory instead. Then invoke it from Claude Code: /unslop this dashboard You can also pass a live URL — unslop will screenshot and audit the deployed site without needing code access. The official heydamir/unslop repository https://github.com/heydamir/unslop has full installation and usage documentation. Not Just Claude Code unslop works with Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and Copilot. Frameworks covered include React, Next.js, Vue, Svelte, Tailwind, and plain HTML/CSS. A Codex-specific port shipped within days of the original. The skill has already been merged into NousResearch/hermes-agent as an optional upstream stub, which signals it is heading toward becoming a default part of agentic UI workflows. The Broader Point Vibecoding solved the “I cannot build it” problem. What it created is the “I built it but it looks AI-made” problem — and that problem compounds as every developer ships with the same defaults. unslop is the first tool that automates the polish pass without requiring a pre-built design system, a Figma file, or a designer on the team. It derives the design direction from what you already have, it is free you pay only for the AI tokens , and the growth trajectory https://trendshift.io/repositories/327085 suggests it is going to be the standard pre-ship step for anyone using a coding agent. If you ship any UI with a coding agent, run this before you ship the next one.