Ext Ops Panel
Open dashboard
Comparison

anti-slop-ui vs Superdesign

anti-slop-ui is a plugin bundle for AI coding tools published by awaken7050dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Superdesign is a plugin bundle for AI coding tools published by superdesigndev. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceanti-slop-uiSuperdesign
Claude Code: claude-plugins-community Listed
Version: 4d80235
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-official Not listed Listed
Version: 0.6.0
Forks (GitHub): 66
Stars (GitHub): 840
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

anti-slop-ui vs Superdesign
Factanti-slop-uiSuperdesign
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub840
Forks (GitHub) (differs)No figure on GitHub66
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not published1
Licence (differs)Not statedMIT
Repository (differs)github.com/awaken7050dev/anti-slop-uigithub.com/superdesigndev/superdesign-skill
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

anti-slop-ui

In its own words, on Claude Code: claude-plugins-community:

Eliminates the AI-generated look from any frontend. Identifies the specific patterns that make sites look AI-generated and provides concrete fixes for each one. Includes design tokens by impression level, a mobile adaptation pass, and a pre-ship checklist.

Superdesign

In its own words, on Claude Code: claude-plugins-official:

Design or redesign frontend UI and marketing graphics on the Superdesign infinite canvas. Reads your codebase for context, sets up a design system, and generates branchable design drafts you refine.

How to run each

anti-slop-ui As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install anti-slop-ui@claude-community

Superdesign As a Claude Code plugin

Claude Code
/plugin install superdesign@claude-plugins-official

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: anti-slop-ui · What it can do: Superdesign · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built