Ext Ops Panel
Open dashboard
Comparison

architecture-docs vs design-is-code

architecture-docs is a plugin bundle for AI coding tools published by barnburner121. Marketplaces we read that list it: 1 (Community GitHub marketplaces). design-is-code is a plugin bundle for AI coding tools published by mossgreen. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
Marketplacearchitecture-docsdesign-is-code
Community marketplace barnburner121/claude-plugin-marketplace Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 0.11.2
Forks (GitHub): 0
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

architecture-docs vs design-is-code
Factarchitecture-docsdesign-is-code
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)1 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)Installs as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)21
LicenceMITMIT
Repository (differs)github.com/barnburner121/claude-plugin-marketplacegithub.com/mossgreen/design-is-code-plugin
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-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

architecture-docs

In its own words, on Community GitHub marketplaces:

Generate architecture documentation with diagrams

design-is-code

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

Transform UML sequence diagrams and decision tables into Java tests and code. The DisC methodology applies London-school TDD to AI code generation: every design arrow becomes a verify test and every decision-table row becomes one leaf test, so mockist tests pin call structure, order, and arguments — leaving no room for AI interpretation. Phase 1 generates tests from the design; Phase 2 derives the implementation from the tests alone. Currently supports Java + Spring Boot with PlantUML sequence diagrams and Markdown decision tables.

How to run each

architecture-docs As a Claude Code plugin

Claude Code
/plugin marketplace add barnburner121/claude-plugin-marketplace
/plugin install architecture-docs@barnburner121-plugins

design-is-code As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install design-is-code@claude-community

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: architecture-docs · What it can do: design-is-code · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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