← ClaudeAtlas

deslop-uilisted

Anti-slop UI review for generated or generic frontend work. Use after LLM UI output, or for requests to remove AI tells: purple gradients, pill CTAs, default type, centered heroes, three-card grids, glassmorphism, and template sameness.
KyaniteLabs/tastecheck · ★ 8 · Web & Frontend · score 71
Install: claude install-skill KyaniteLabs/tastecheck
# Deslop UI Slop is predictable, uncommitted design, not merely ugly design. Audit surface, structure, and voice against the brief; repair with a specific, verifiable choice. ## Repair order and evidence contract 1. Establish brief, preserved signals, and artifact; separate surface, structural, and verbal findings. 2. Cite selector, section, phrase, screenshot, or browser observation; assign P0–P3. 3. Choose a brief-bound direction, prescribe repairs, and reinspect the same views. `n/a` requires an absent subject. Stop before changing a coherent brief-supported brand choice; ask for direction when brief or acceptance criteria are absent. ## Diagnose cause, then tell Make two passes: **intent** (job, audience, hierarchy, retained signals, signature) and **behavior** (first view, transitions, narrow view; trace code to selector/token or screenshot geometry). Test whether a neutral replacement changes meaning or performance. Preserve a documented functional pill, gradient, table, or system font; repair implementation, not role. Rank P0 meaning/interaction/accessibility/fact, P1 direction/hierarchy, P2 repeated default, then P3 polish. Every P0–P2 packet names subject, observation+brief, mechanism, preserved signal, concrete replacement+owner, and after-state observation (including narrow view). Make one causal structural repair when the skeleton is generic. ## Fast audit and self-check Render before acting; grep is only a lead. Check these detector/decision pairs: | Pl