ShipSwift is an AI-native SwiftUI component library with full-stack recipes and MCP integration, providing production-ready components and recipes for SwiftUI apps.
Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).
What it is
ShipSwift is an AI-native SwiftUI component library that provides production-ready SwiftUI components, full-stack recipes, and context to build real apps. It emphasizes live recipe access and MCP-backed backends, aiming to serve as a codebase that can be used by AI to generate apps.
How it works
The project bundles multiple subdirectories:
- SWAnimation, SWChart, SWComponent for UI elements
- SWModule for multi-file frameworks (auth, camera, chat, paywall, settings, etc.)
- SWUtil for utilities Recipes are exposed via Skills with free and pro tiers, enabling retrieval of SwiftUI source code, implementation steps, and best practices. It supports connecting an MCP server to fetch recipes and backend guidance.
Dependency rules indicate modules may depend on SWUtil, with higher-level modules (SWModule) depending on SWUtil and SWComponent. The repository documents a naming convention using SW prefix and .sw modifiers for View modifiers.
Getting started
Key setup steps in the README include:
- Install ShipSwift Skills:
npx skills add signerlabs/shipswift-skills
- Connect the recipe server for MCP access:
# Claude Code
claude mcp add --transport http shipswift https://api.shipswift.app/mcp
# Gemini CLI
gemini mcp add --transport http shipswift https://api.shipswift.app/mcp
- Alternatively, install local skills to read source files directly:
npx skills add signerlabs/ShipSwift
- Run the showcase app setup instructions:
git clone https://github.com/signerlabs/ShipSwift.git
cd ShipSwift
open ShipSwift.xcodeproj
Recent releases
The releases section for the latest version lists as: - none
Traction
The repository has 2862 stars and 169 forks, with 5 open issues. Last push was 2026-08-02.
Behind the repo
Not provided in the README snippet.
Caveats
License is MIT. The README references that iOS client code is open-source under MIT and Pro recipes add backend and compliance templates, but no explicit licensing caveats beyond that are shown in the provided content.