Damir Sokolovsky’s Unslop is a design-review skill for Claude Code and Codex. It audits an interface, proposes a direction based on the product, and guides the agent through specific changes.

The workflow

  • Audit the actual screen. Identify generic decoration, inconsistent spacing, weak hierarchy, and unclear copy, with locations for each finding.
  • Agree on a direction before editing. Describe the product, its character, a visual world, one or two focal moments, and a signature detail. The skill asks for approval unless the user has already authorized an autonomous pass.
  • Work through nine passes: spacing, color, icons, copy, typography, layout, details, visuals, and motion.
  • Scale the intervention. Light problems get a polish pass that keeps the existing brand. A good screen gets small suggestions rather than a forced redesign.
  • Keep the product intact. Preserve features, content, and section order unless the user asks for broader changes.

What comes with it

  • Reference material covers design tokens, common problems, visual direction, and effects, alongside two example screens.
  • Claude Code uses /unslop; Codex uses $unslop. The README describes user-level and project-local installation.
  • A live-page snapshot workflow creates an editable copy when source code is unavailable. It produces a redesign to hand over, not a change to the original site.
  • Optional before-and-after story videos use Playwright and ffmpeg. Generated hero images require a connected image service; the README says paid generations need prompt approval.
  • Licence: CC BY 4.0 permits commercial reuse and adaptation with attribution. Credit Damir Sokolovsky, link the repository and licence, and indicate modifications when sharing adapted material.

Design direction still needs judgment

The skill makes concrete choices: restrained surfaces, limited accents, line icons, and less decorative motion. Those choices can improve consistency, but they can also become another template when applied mechanically.

The r/BestGitHubRepos discussion includes both interest and criticism. Some readers argue that deliberate human direction matters more than replacing one set of defaults with another.

Caveat: the repository documents a workflow and examples; it does not establish improved usability through user testing.