/a-unslop-ui

Two years ago you could spot an AI-built site in a second. Purple gradient, glowing hero text, three cards under a centered headline, emoji where the icons should be, the stock shadcn theme untouched.

Then everyone read the same advice about how to avoid that, and moved to a cream background, a serif display face and a sage-green accent. Which is now its own default, arrived at the same way the first one was: nobody chose it.

a-unslop-ui flags both. The 2024 look and the 2026 correction to it get the same treatment, so fixing one tell does not just buy you the newer one.

It prescribes no palette, no font, and no layout. This is the whole point. A skill that told you what to use would be manufacturing the next default, and in about eighteen months somebody would be writing a scanner for it. What it asks instead is whether you can give a reason for the choice, which is the one thing a default can never survive. Where you have a reason, there is an unslop-ignore escape hatch and the scanner stops asking.

The mechanical tells it catches are the ones a regex can reach: hardcoded AI-purple, gradient body text, unprompted neon glow, emoji standing in for icons, an untouched component library theme. It says plainly which ones it cannot catch. Spacing rhythm, layout instinct, whether a page feels made or assembled: those need your eyes, and the reference doc walks through what to look for.

Findings come with file, line and a severity-weighted score, and the scanner exits non-zero on the high ones so it can gate a build.

Ships in the unslop plugin, alongside a-unslop-text and a-unslop-code. Installing the plugin gets you all three.

/plugin marketplace add imisic/claude-marketplace
/plugin install unslop@imisic

Then the command is /a-unslop-ui.

The tell catalog is adapted (MIT) from the vibecoded-design-tells research, a large-scale analysis of what people actually name when they call a site AI-designed.