Ext Ops Panel
Open dashboard
Comparison

consistent-ui vs io.github.jmshinhwa/bem-class-extractor-html

consistent-ui is a plugin bundle for AI coding tools published by thevrus. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.jmshinhwa/bem-class-extractor-html is an MCP server published by jmshinhwa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplaceconsistent-uiio.github.jmshinhwa/bem-class-extractor-html
Claude Code: claude-plugins-community Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 1 291
Downloads/week (npm): 50
Forks (GitHub): 1
Stars (GitHub): 1
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

consistent-ui vs io.github.jmshinhwa/bem-class-extractor-html
Factconsistent-uiio.github.jmshinhwa/bem-class-extractor-html
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@readystack/bem-class-extractor-html)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/thevrus/consistent-uigithub.com/jmshinhwa/readystack-themes
Changes in the last 7 days00
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

consistent-ui

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

Enforce UI consistency across an entire codebase — detects drift in spacing, typography, colors, components, iconography, and interaction patterns across web, native mobile, and server-rendered templates. Generates a P0-P3 report and remediation plan.

io.github.jmshinhwa/bem-class-extractor-html

In its own words, on Official MCP Registry:

16 BEM naming rules read the HTML file you have open and 22 markup and SCSS skeletons write the styl

How to run each

consistent-ui As a Claude Code plugin

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

io.github.jmshinhwa/bem-class-extractor-html As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio bem-class-extractor-html -- npx -y @readystack/bem-class-extractor-html --mcp

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: consistent-ui · What it can do: io.github.jmshinhwa/bem-class-extractor-html · 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 Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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