no-ai-design-slop

Detect and remove generic AI-generated design patterns from websites, apps, and mockups.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill no-ai-design-slop-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: no-ai-design-slop
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/better-design/skills/no-ai-design-slop
Command: npx skills add https://github.com/josippapez/ai-setup --skill no-ai-design-slop-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-generated interfaces often ship with generic defaults: purple gradients, tracked eyebrows, nested cards, fake metrics, and decorative motion that make products look interchangeable and incoherent. This Skill acts as a passive design quality gate that catches these patterns during UI creation, revision, or review while preserving the product's existing art direction. ## Core Features & Use Cases - Passive quality gate: Applies compact checks for system consistency, hierarchy, composition, typography, color, product truth, interaction states, and motion on every design task. - Pattern catalog: Ships an ARTICLE.md reference with ten categorized slop sections (layout, cards, typography, color, imagery, components, motion, copy, accessibility) plus high-signal clusters like "Generic AI SaaS" and "Card apocalypse". - Surgical removal workflow: Names each suspect element precisely, tests whether deletion loses meaning, and makes the smallest correction using the existing design system instead of forcing a neutral redesign. - Use Case: While building a landing page, the Skill flags a tracked uppercase eyebrow, radial gradient lights, and identical icon-tile feature cards, then replaces them with the page's established hierarchy and real product screenshots. ## Quick Start Review this landing page for generic AI design patterns and remove anything that does not serve the product's existing visual direction.

Frequently Asked Questions about no-ai-design-slop

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

FAQPage Schema
How do I remove generic AI design patterns from a landing page?

Run an anti-slop pass that names each suspect element precisely, such as tracked eyebrows, radial lights, or nested cards, then applies the removal test: delete it if meaning survives, otherwise make the smallest correction using the existing design system. The ARTICLE.md catalog lists patterns by category.

What counts as AI design slop in UI work?

Slop is any choice made by reflex rather than for the product: purple-to-blue gradients, glass cards without layering, identical icon-tile feature cards, fake metrics, marquee animations, or sections copied from references without adaptation. The failure is defaultness and incoherence, not the technique itself.

Does this Skill force a specific design style or redesign?

No. It preserves the product's existing art direction, tokens, and components, and explicitly forbids replacing distinctive choices with fashionable neutral templates. Corrections use the local design system, and new colors, fonts, or effects are only added when they solve a demonstrated loss.

Can I use it for a formal design audit without editing?

The Skill distinguishes passive gating during implementation from formal review. For a review-only request it defers to the separate audit-ai-design-slop workflow and does not modify the artifact, while narrow edits stay scoped to the requested surface.

What are the limitations of an anti-slop cleanup pass?

It judges only the visible rendered result and does not guess whether AI made the artifact. It will not invent proof such as testimonials or metrics, will not widen a narrow edit into a full site audit, and requires inspecting actual rendered output rather than source code alone.