What it does

ShipSwift is a SwiftUI component library with a twist: it’s built to be read and used by AI assistants. You wire it to your LLM via an MCP server, and the model can pull recipes for animations, charts, auth flows, paywalls, or camera capture — complete with source code and implementation steps. There’s also a fallback local mode that reads files directly from the repo, no server required.

The library itself covers 30 animation components (including Metal shader backgrounds), 8 chart types, 20-odd UI primitives, and multi-file modules for auth, chat, and subscriptions. iOS 18+, Swift 5.0+, MIT licensed.

The interesting bit

The “Pro” tier isn’t just more components — it’s backend recipes. The free repo gives you client-side SwiftUI; the paid tier adds Hono routes, database schemas, compliance templates, and a list of pitfalls per feature. The business model is essentially: let AI handle the boilerplate, then sell the last 20% that actually ships to production.

Key highlights

• MCP server integration for Claude Code, Gemini CLI, Cursor, etc.
• Self-contained files: copy a single .swift file from SWAnimation/ or SWChart/ and it works
• Modules include real integrations: Amplify/Cognito auth, StoreKit 2 paywalls, VolcEngine voice recognition, TikTok Events API
• Strict dependency rules: utilities → components → modules, no circular mess
• Live showcase app on the App Store to preview every component

Caveats

• Pro recipes (backend guides, compliance docs) require the MCP server and presumably a paid plan; the README is vague on exact pricing beyond “from $5,000” for custom dev
• Some modules (SWPaywall, SWTikTokTracking) ship the iOS client free but lock the full-stack recipe behind Pro
• iOS 18 minimum — no backwards compatibility mentioned

Verdict

Worth a look if you’re already using AI coding assistants for iOS and tired of watching them hallucinate SwiftUI syntax. Skip it if you need Android, pre-iOS 18 support, or prefer to hand-craft your view modifiers the old-fashioned way.