Unslop Skill: Turn AI-Looking UI Into a Designed Interface

Install heydamir/unslop in Claude Code, Codex or DeepSeek Harness, then run /unslop on a vibecoded screen: the five passes, the Playwright and ffmpeg extras, and the CC BY 4.0 credit rule.

Last updated: 2026-11-17

Quick answer

unslop is a UI design skill, not a prose skill. Its own repository summary is: "A Claude skill that turns vibecoded, AI-looking UI into a designed interface." It reads a screen, names the slop it finds — the purple gradients, glows, emoji labels, shouty copy, uneven spacing — then sets a direction from your product and fixes the screen pass by pass, the way a designer does a redline review.

The repository is heydamir/unslop by Damir Sokolovsky (@heydamir), who started the "Unslopping series" on X. At the GitHub API snapshot of 2026-11-17 it had 17,340 stars and 1,010 forks, created 2026-10-29 and last pushed 2026-11-15. The license is CC BY 4.0, which is worth reading before you ship anything it touched: reuse is allowed, including commercially, with credit and a link back.

Everything below was checked against the repository and its README on 2026-11-17; commands are copied verbatim. If you arrived here looking for a text de-slopper, this is the wrong page — see humanizer skills for the writing side.

What it changes

The README describes the target plainly: "It finds the slop first, the purple gradients, glows, emoji labels, shouty copy and uneven spacing, then sets a direction from your product and fixes the screen pass by pass like a designer doing a redline review."

It is not tied to one stack. The README says it works in "whatever your screen is built with, like Next.js, React, Vue, Svelte, Tailwind or plain HTML and CSS", on dashboards, apps and landing pages — and on a live site when all you have is a link.

One behaviour is worth knowing before you run it, because it is the difference between a design pass and a slot machine: "It audits the screen and proposes a direction before it edits anything, so you can steer it early. If the screen is already good, it tells you so and suggests a few small refinements instead of redesigning it."

The five passes

The workflow is ordered, and the order is the point — spacing before colour, copy before layout:

StageWhat happens
AuditLists every sign of slop, and where it lives
DirectionCharacter, world, the one or two moments that carry the colour, and a signature detail — taken from your product
PassesSpacing, colour, icons, copy, type, layout, details, visuals and motion, in that order
VisualsShows your product instead of a glossy blob; can generate a hero scene through an image service
Story videoA square video under 10 seconds of your screen unslopping itself

The visual stage is the only one that can cost money. The README says it can generate an image through a service such as fal, Replicate, OpenAI images or Higgsfield; if none is connected it offers to connect one as an MCP server, shows the prompt and asks before every paid generation. Dashboards and apps rarely need one.

Install it

Installs are per agent, and the README spells each one out.

AgentCommand (README verbatim)
Claude Code, every projectclaude plugin install unslop --marketplace heydamir/unslop
Claude Code, older buildclaude plugin marketplace add heydamir/unslop then claude plugin install unslop@heydamir
Claude Code, one projectadd --scope local to the install above
Claude Code, whole teamclaude plugin marketplace add heydamir/unslop then claude plugin install unslop@heydamir --scope project
Codex$skill-installer install https://github.com/heydamir/unslop/tree/main/skills/unslop
Codex, by handgit clone https://github.com/heydamir/unslop then mkdir -p ~/.agents/skills && cp -r unslop/skills/unslop ~/.agents/skills/
Google Antigravitymkdir -p ~/.gemini/config/skills && cp -r unslop/skills/unslop ~/.gemini/config/skills/

Two footnotes from the README that catch people:

  • For the team install, commit .claude/settings.json, and each teammate still runs the marketplace pair once in their own copy.
  • If you previously copied the skill into ~/.claude/skills/ or a project .claude/skills/, delete that copy — otherwise /unslop keeps running the old one instead of the plugin.

After installing, start a new Claude Code session, or run /reload-plugins in an open one. To update: claude plugin update unslop@heydamir, or turn on auto-update for the heydamir marketplace under Marketplaces in /plugin.

Optional extras

Snapshotting a live link, and the story video, need a browser and a video binary:

npm install -D playwright
npx playwright install chromium

The story video also needs ffmpeg installed and available on your PATH.

Use it

In Claude Code, type /unslop with what you want; if another skill already owns that name, use /unslop:unslop. In Codex, type $unslop the same way. Or just ask in your own words and the agent picks the skill up by itself.

/unslop this dashboard
/unslop the hero of https://example.com
/unslop my landing page and make the story video so I can post it

The second example is the one that needs Playwright — a live URL has to be loaded and captured before anything can be reviewed.

Using it with DeepSeek Harness

A dsh skill is the same object as a Claude Code skill: a folder holding a SKILL.md. Project skills live at .dsh/skills/<name>/SKILL.md inside your workspace and dsh re-injects the catalogue on the next prompt, so a copied folder is picked up without a restart — the install-skills walkthrough and skill installation, hands-on cover the step-by-step version.

git clone https://github.com/heydamir/unslop
mkdir -p .dsh/skills && cp -r unslop/skills/unslop .dsh/skills/

The plugin route does not exist for dsh — unslop ships as a Claude Code plugin and a Codex skill, not as a dsh plugin — so the copy is the whole install. If you would rather understand the folder layout first, what a skill is walks through SKILL.md, references/ and scripts, which is exactly the shape this repository uses.

Licence and credit

CC BY 4.0 is not MIT. The README's own wording: "Use it, change it and share it, including commercially, as long as you credit Damir Sokolovsky (@heydamir) and link back to this repository."

If you are auditing licences across a stack of skills, that is a different obligation from the MIT packs covered in pstack skills or the best dsh skills — an attribution line in your README or credits screen is the cheapest way to satisfy it.

When it is the wrong tool

  • You want text rewritten, not a screen. This skill edits UI. The writing equivalent is covered on humanizer skills.
  • You need accessibility or performance work. The five passes are visual and copy-driven. Nothing in the README claims WCAG conformance or a performance budget, so do not treat a finished unslop pass as an audit.
  • You want a guaranteed redesign. The skill is explicit that a screen it judges already good gets small refinements instead. If you need a specific look regardless of its verdict, say so in the prompt.
  • You cannot credit the author. CC BY 4.0 requires attribution; if your product cannot carry it, pick a differently licensed skill.

FAQ

What does the unslop skill actually do? It is a UI design skill, not a writing skill. The repository describes it as "A Claude skill that turns vibecoded, AI-looking UI into a designed interface": it lists the slop on a screen, proposes a direction taken from your product, then fixes the screen pass by pass.

How do I install unslop in Claude Code? Run claude plugin install unslop --marketplace heydamir/unslop in a terminal to get it in every project. On an older Claude Code without --marketplace, run claude plugin marketplace add heydamir/unslop and then claude plugin install unslop@heydamir. Add --scope local for one project.

Can I use unslop in Codex or DeepSeek Harness? Yes. Codex installs it with $skill-installer install https://github.com/heydamir/unslop/tree/main/skills/unslop, or by copying skills/unslop into ~/.agents/skills/. Because a dsh skill is the same object — a folder holding a SKILL.md — you can copy that same folder into .dsh/skills/.

Is unslop free to use? It is licensed CC BY 4.0: use, change and share it, including commercially, as long as you credit Damir Sokolovsky (@heydamir) and link back to the repository.

Do I need Playwright or ffmpeg? Only for snapshotting a live site and for the story video. Auditing and editing a local screen needs neither.

Sources

Every claim above comes from these pages, read on 2026-11-17:

  • github.com/heydamir/unslop — README: the repository summary, the slop list, the five stages, the supported stacks, the three install paths (Claude Code plugin with --marketplace and the two-step fallback, Codex $skill-installer and manual copy, Antigravity), the --scope local / --scope project variants, /reload-plugins and claude plugin update, the Playwright and ffmpeg extras, the image-service and paid-generation consent behaviour, the "tells you so" behaviour on a good screen, and the CC BY 4.0 credit requirement. GitHub API snapshot taken 2026-11-17: CC-BY-4.0, 17,340 stars, 1,010 forks, created 2026-10-29, pushed 2026-11-15 (a snapshot, not a fixed number).
  • x.com/heydamir and the README's link to the Unslopping series — authorship and the series the skill grew out of.

The project is a community skill, not an Anthropic or DeepSeek product, and it is not affiliated with this site. Install commands come from the README at the date shown; re-check it before you run one, because plugin and marketplace names change with releases.

Related reading: humanizer skills, the Impeccable skill, pstack skills, installing skills, the best DeepSeek Harness skills.

DSH Plugins is an independent community directory of DeepSeek Harness plugins. Not affiliated with or endorsed by DeepSeek. Third-party plugins are not security-audited — review the source before installing.

New DeepSeek Harness plugins, weekly. No spam.