Unslop Brings Staged UI Review to Claude Code and Codex
Unslop is a GitHub-hosted skill for Claude Code and Codex that targets what its author describes as “vibecoded, AI-looking” interfaces. For developers, the concrete change is an ordered review process: the skill audits a
Unslop is a GitHub-hosted skill for Claude Code and Codex that targets what its author describes as “vibecoded, AI-looking” interfaces. For developers, the concrete change is an ordered review process: the skill audits a screen and proposes a design direction before it begins editing. The project documents the workflow and installation steps on GitHub.
From audit to ordered revisions
The audit identifies patterns including purple gradients, glows, emoji labels, forceful copy and uneven spacing. Unslop then derives a direction from the product, covering its character, visual world, limited uses of color and a signature detail. Its edits proceed through spacing, color, icons, copy, type, layout, details, visuals and motion, in that order. Those stages are specified in the project README.
The README says the skill can work on dashboards, applications and landing pages built with Next.js, React, Vue, Svelte, Tailwind, or plain HTML and CSS. It can also inspect a live-site URL. Users invoke it with /unslop in Claude Code or $unslop in Codex, although the repository says an agent can also select the skill from a request written in ordinary language. The supported inputs, stacks and commands are documented here.
If the initial screen is already satisfactory, the intended behavior is to suggest limited refinements instead of carrying out a full redesign. The proposed direction appears before edits, giving the user an opportunity to steer it early, but the documentation does not describe a mandatory approval gate. The README states both behaviors.
Optional media features add dependencies
For hero visuals, Unslop can use image services such as fal, Replicate, OpenAI Images or Higgsfield. If no service is connected, it can offer to connect one as an MCP server; the project says it displays the prompt and asks before each paid generation. The image-generation workflow is described in the repository.
The skill can also create a square story video, lasting under 10 seconds, that shows the interface changing. Live-site snapshots and story videos require Playwright and its Chromium browser, while video output additionally requires ffmpeg on the system path. The repository lists these dependencies.
Unslop uses the CC BY 4.0 license. The README permits modification, sharing and commercial use provided users credit creator Damir Sokolovsky and link to the repository. The licensing conditions are published with the project.
Analysis: a review rubric, not evidence of better design
Analysis: Unslop’s more consequential idea is not automated CSS editing but the conversion of a subjective critique into an inspectable sequence. Surfacing the audit and proposed direction before the ordered passes gives developers a clearer point at which to challenge the agent’s assumptions. That interpretation follows from the workflow documented by the project.
The unresolved trade-off is that a repeatable rubric can also standardize one author’s aesthetic preferences. The project page defines recognizable visual clichés and provides examples, but it does not report usability testing, product metrics or comparative evaluation establishing that removing those patterns improves an interface. Developers still need an independent review of whether the proposed direction suits the product and its users. The repository shows the project’s documented scope and evidence.
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.