antislop-ui

Detects and corrects generic AI-generated UI patterns in color, layout, components, and motion.

Updated Dec 15, 2025
One-click install
npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-ui-zeeforc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: antislop-ui
Source: https://github.com/zeeforc/website-lpkpaiton/tree/main/.agents/skills/antislop-ui
Command: npx skills add https://github.com/zeeforc/website-lpkpaiton --skill antislop-ui-zeeforc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding agents produce interfaces full of recognizable defaults: blue-purple gradients, glassmorphism everywhere, bento grids, fake terminal windows, and invented dashboard metrics. This Skill provides a rule-based checklist to identify and replace those patterns with deliberate, brand-driven design decisions. ## Core Features & Use Cases - Visual pattern detection: Flags default color treatments, excessive glass, glow, shadows, border radius, and generic typography, each with a Tell, Why, and Fix tied to numbered core rules. - Layout and component review: Catches template structures like three-step "How It Works" sections, "Most Popular" pricing cards, logo bars, and uniform feature card grids. - App and dashboard auditing: Covers sidebar-plus-stat-cards shells, invented metrics, filler activity feeds, fake placeholder data, and empty or loading states that say nothing. - Use Case: After an agent generates a landing page or dashboard, run this Skill's UI checklist alongside the core Delivery Gate to verify the palette comes from a written brand identity, every control has real behavior, and all data is real or clearly labeled as placeholder. ## Quick Start Review the interface I just built against the antislop-ui checklist and fix every default AI pattern you find.

Frequently Asked Questions about antislop-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI-generated websites from looking generic?▼

Run a pattern checklist against the output: flag default gradients, glassmorphism on every surface, bento grids, fake terminal windows, and emoji in copy. Replace each with decisions derived from a written brand identity, and cap decorative effects to one or two elements.

What UI patterns signal a page was made by AI?▼

Common tells include blue-to-purple gradients, pill-shaped everything, glow on multiple elements, three-column pricing with a highlighted middle tier, "How It Works" in exactly three steps, generic logo bars, and capsule badges reading "AI Powered".

How should dashboards handle placeholder or empty data?▼

Show real numbers or none at all; never invent metrics, deltas, or activity feed entries. Empty states should name the cause and the next action, and form fields should use honest placeholders like "Your Name" instead of fake data like "John Doe".

When is it acceptable to use gradients or glassmorphism in UI design?▼

Only when the choice serves a documented purpose tied to brand identity or hierarchy, such as separating one level from another. Dose caps apply: glass on at most one or two elements, and gradients only where the reason is written down.

Does this Skill work without the antislop core file?▼

No. It is designed to load together with the core antislop.md, which holds the purpose test, the three tiers, and the Delivery Gate. This Skill adds UI-specific depth and references core rules by number without duplicating them.