When should you use it?
- A coding agent built your dashboard or landing page and it looks like every other AI template
- You want a design review in the code itself, not a mockup someone has to rebuild
- You only have a link to a live page and need a redesigned version to hand to whoever runs the site
Not for: Brands with a design system and a designer who already owns these decisions; Accessibility or compliance audits; check contrast and keyboard use separately; Changing features or page structure; the skill is meant to keep content and section order
What do you need, and what do you get?
You need
- Claude Code or Codex with the skill installed from the heydamir/unslop repository
- The screen's code, or a link to the live page (Playwright is needed to capture it)
- A sentence on what the product does and for whom, if the page does not make it clear
You get
- An audit listing each sign of generic AI styling and where it appears
- A five-line direction (product, character, world, the moments that get color, one signature detail) for you to approve
- The redesigned screen in your existing stack, with a short report per pass
- Optionally, a short video of the screen changing pass by pass, if Playwright and ffmpeg are installed
How does it work, step by step?
- Install the skillCopy the skills/unslop folder into your Claude Code or Codex skills directory, as the repository README explains.
- Point it at one screenAsk it to unslop a specific dashboard, page or URL rather than the whole app at once.
- Approve the directionRead the audit and the five-line direction, and correct anything that misreads your product before it edits.
- Review the passesCheck the result against the audit list and run the app on desktop and mobile.
- Test before shippingConfirm forms, links and states still work, and check text contrast after the color changes.
The prompt
Our adapted version, written to work in Claude Code and Custom agent. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Review the {screen_name} screen in {codebase_or_url} like a product designer doing a redline review. Keep every feature, piece of content and section order. 1. List each sign that it looks machine-generated, for example decorative gradients, glows, emoji in labels, hype badges or inconsistent spacing, and say where each one is. 2. Propose a direction in five short lines: what the product does and for whom, three specific character words, the real-world setting it belongs to, the one or two places that deserve strong color, and one recurring signature detail. Then wait for my approval. 3. After I approve, fix spacing first, then color, icons, copy, typography, layout, details, images and motion. Use a consistent spacing scale and a single accent color. If the screen is already good, say so and suggest no more than three small changes.
The original skill is published by Damir Sokolovsky (@heydamir) on GitHub. Open it there to install or import it; the prompt above is our own adaptation.
What can go wrong?
- The direction step is where the result is decided. A vague product description gives a vague redesign.
- Generated hero images cost money on paid image services. The skill asks first; say no if you do not need one.
- A redesign of a saved copy of a live page is code to hand over, not a change to the live site.
- Visual polish can hide broken behavior. Test the screen, not only the screenshot.
Our take
AI-built interfaces have a recognizable look: purple gradients, glowing cards, emoji in every label and spacing that changes from one card to the next. What makes this skill worth installing is that it treats the fix as design judgment rather than a list of banned styles. It asks the agent to describe the product, its character and the material world it belongs to before touching anything, and to put rich color in only one or two places, which is roughly how a good designer works. The order of the passes is sensible too, with spacing first and imagery last, and it waits for your approval of the direction. Our cautions: it is new, so expect to steer it, and polish is not testing, so check contrast, mobile layouts and every interactive state afterward. In our dry run, with our short prompt on a fictional invoicing dashboard, the audit flagged a gradient headline, emoji labels, four different card paddings and a glowing chart. The approved direction leaned on paper ledgers, and the result kept every feature while moving the only accent color onto the cash-flow chart.
Where the time goes back: You get a designer-style review and fix of a generated screen in one agent session, in the code you already have, instead of commissioning mockups and rebuilding the page by hand.
FAQ
Is it free to use?
Will it redesign a screen that already looks good?
Why is the skill text not shown here?
Source and credit
This playbook is based on work by Damir Sokolovsky (@heydamir). We summarize it and link to it and write our own adapted prompt.
- Original
- unslop skill (heydamir/unslop)
- Creator
- Damir Sokolovsky (@heydamir)
- Published on
- GitHub
- Original date
- Oct 29, 2026
- License
- CC-BY-4.0
- Originally for
- Claude Code
- AI dry run
- Nov 3, 2026: passed. Dry-run tested by our AI test agent on sample input. All seeded signs found, direction waited for approval, passes in order, single accent, features unchanged.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Nov 8, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
The original is licensed under CC BY 4.0 by Damir Sokolovsky (@heydamir). Nothing from it is reproduced here: our summary and adapted prompt are our own wording, and the original is unchanged at the source link.
Are you the creator? Claim or correct this page.