swiftui-guidance-for-macos vs ShipSwift
swiftui-guidance-for-macos is a plugin bundle for AI coding tools published by kageroumado. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ShipSwift is an MCP server published by signerlabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  swiftui-guidance-for-macos |  ShipSwift |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 185 Stars (GitHub): 3 244 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 | swiftui-guidance-for-macos | ShipSwift |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 (worse) | 3 244 (better) |
| Forks (GitHub) (differs) | 1 (worse) | 185 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.shipswift.app/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/kageroumado/swiftui-macos-skill | github.com/signerlabs/shipswift |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 31 h ago |
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
swiftui-guidance-for-macos
Runtime-level SwiftUI guidance for macOS apps. Covers observation internals, concurrency scheduling, view identity, performance, AppKit bridging, SwiftData, and accessibility — with deep explanations of why patterns work, not just what to do. Built from developing a production macOS browser with SwiftUI and from reading the Swift runtime source. Targets macOS 26+, Swift 6.2 with strict concurrency. Designed for frontier models: skips basics, focuses on non-obvious traps and mechanisms that even experienced developers get wrong.
ShipSwift
40+ production-ready SwiftUI recipes for building full-stack iOS apps via MCP.
How to run each
swiftui-guidance-for-macos As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install swiftui-guidance-for-macos@claude-communityShipSwift As a remote MCP server
claude mcp add --transport http shipswift https://api.shipswift.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ShipSwift 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: swiftui-guidance-for-macos · What it can do: ShipSwift · 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.