# Randroid Clean Slop

> Diagnose and remove generic AI-generated visual and copy patterns from an existing interface through screenshot-led iteration. Use when the user asks to de-slop, make a UI feel less AI-generated, clean up generic vibe-coded design, or perform a final visual-polish pass. Do not use as a substitute for implementing missing product functionality.

- Skill: `randroids-dojo/randroid-clean-slop` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds add randroids-dojo/randroid-clean-slop`
- Raw SKILL.md: https://api.skillmd.com/api/skills/randroids-dojo/randroid-clean-slop/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: randroids-dojo (https://skillmd.com/u/randroids-dojo)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/randroids-dojo/randroid-clean-slop

---


# Clean Slop

Improve an existing interface by finding concrete generic-design tells, fixing the affected elements, and visually checking the result.

## Workflow

1. Read [references/rules.md](references/rules.md) before making design changes.
2. Inspect the running interface or supplied screenshot first. If neither exists, inspect the relevant frontend code and state that visual confirmation remains pending.
3. Identify specific visible problems rather than applying a wholesale style preset.
4. Fix one coherent group of issues at a time while preserving the product's established brand, information hierarchy, and functional behavior.
5. Re-run the interface at relevant desktop and narrow widths, capture a fresh screenshot, and repeat until the identified tells are gone or a product decision is required.
6. Check interaction states, text wrapping, contrast, layout shift, reduced motion where relevant, and browser-console errors.
7. Do not replace real content, photography, icons, fonts, or brand assets without user authorization when that choice materially changes the product.
8. Offer to encode durable, project-specific prevention rules only after the visual result is accepted.

Finish with the exact elements changed, visual verification performed, and any remaining design decisions.


