get-design-done vs AppLaunchFlow
get-design-done is a plugin bundle for AI coding tools published by hegemonart. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). AppLaunchFlow is an MCP server published by ynnickw. 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
| Marketplace |  get-design-done |  AppLaunchFlow |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.14.5 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.9 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | get-design-done | AppLaunchFlow |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.applaunchflow.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 5 | Not published |
| Parts of the bundle (differs) | 95 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hegemonart/get-design-done | github.com/ynnickw/applaunchflow-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour ago, requires a key |
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
get-design-done
Agent-orchestrated design pipeline for Claude Code. Five stages (brief → discover → plan → design → verify), 33 specialized agents, 12 tool connections including Figma, shadcn/ui, and Magic MCP. Takes a design brief from vague idea to verified, shipped code — with explicit decisions, pattern-mapped plans, and goal-backward audits. Solves the "Claude made it look fine but nothing ties together" problem: every token, component, and copy choice is decided, applied, and verified against the original goals.
AppLaunchFlow
Create app-store screenshots, social graphics, promo videos, and animated device mockups.
How to run each
get-design-done As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install get-design-done@claude-communityAppLaunchFlow As a remote MCP server
claude mcp add --transport http applaunchflow https://mcp.applaunchflow.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only AppLaunchFlow has a remote endpoint we check. How we check endpoints
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: get-design-done · What it can do: AppLaunchFlow · 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.