signerlabs/ShipSwift: An AI-Native SwiftUI Component Library with MCP Access for Coding Agents

Why ShipSwift Is Built Around AI Coding Agents

Most SwiftUI component libraries are written for human developers: the documentation is prose, examples are in README files, and using a component means reading docs and writing the code yourself. ShipSwift takes a different position. The README describes the goal as giving an AI coding agent everything it needs in one command: production-ready SwiftUI components, full-stack recipes, and the context to build real apps without guessing.

The mechanism is MCP (Model Context Protocol). By connecting an AI coding agent to the ShipSwift MCP server, the agent can retrieve any component's source code, implementation steps, and best practices on demand without the developer having to copy-paste from a website. The README frames this as getting the AI 80% of the way: the components and recipes handle standard patterns, while the custom features specific to the app are still the developer's work.

This design choice has implications for how the library is structured. Every component is self-contained in a single file so the agent can copy it without managing complex dependencies. The naming convention is strict: all types use the SW prefix (SWAlertManager, SWStoreManager) and all view modifiers use the .sw lowercase prefix (.swAlert(), .swPageLoading()). The dependency rules are explicit in the README: SWUtil has no dependencies on other SWPackage directories, SWAnimation and SWChart and SWComponent may depend only on SWUtil, and SWModule may depend on SWUtil and SWComponent. This makes the dependency graph predictable and prevents circular imports.

Component Catalog: Animations, Charts, UI, and Modules

The SWAnimation group contains 30 components divided into three categories. SwiftUI animations include Shimmer, TypewriterText, ShakingIcon, GlowSweep, LightSweep, ScanningOverlay, AnimatedMeshGradient, BeforeAfterSlider, OrbitingLogos, and FullScreenButton. Canvas-rendered 3D components are DotSphere and CharSphere. Metal-shader procedural backgrounds include Dots, Starfield, FractalClouds, InkSmoke, LiquidChrome, Plasma, and AnimatedLoop. Metal-shader backgrounds include Metaballs, Halftone, Water, LiquidMetal, NeuroNoise, DotOrbit, Voronoi, SimplexNoise, ColorPanels, SmokeRing, and Swirl.

SWChart provides eight chart types: LineChart, BarChart, AreaChart, DonutChart, RingChart, RadarChart, ScatterChart, and ActivityHeatmap. SWComponent covers display components (FloatingLabels, ScrollingFAQ, MarkdownText, OnboardingView, VideoPlayer), feedback components (Alert, Loading, ThinkingIndicator), and input components (TabButton, Stepper, SearchBar, AddSheet).

SWModule contains multi-file frameworks for more complex features. SWAuth provides user authentication via Amplify/Cognito with social login, email/password, and phone sign-in with a country code picker. SWCamera wraps camera capture with viewfinder, zoom, photo picker, and face detection using Vision landmark tracking. SWPaywall builds a subscription paywall using StoreKit 2, with the iOS client included free and the full-stack backend recipe available through Pro. SWChat provides an all-in-one chat view with message list, text input, and optional voice recognition via VolcEngine ASR. SWSubjectLifting uses VisionKit ImageAnalysis for background removal.

Three Installation Options: MCP, Local Skills, or File Copy

The README documents three ways to use ShipSwift. The recommended path combines agent skills with the MCP recipe server:

npx skills add signerlabs/shipswift-skills

Then connect the recipe server so the agent can fetch recipes on demand:

claude mcp add --transport http shipswift https://api.shipswift.app/mcp

For Gemini CLI the connection command is:

gemini mcp add --transport http shipswift https://api.shipswift.app/mcp

After connecting, you can ask the agent natural-language requests like "Add a shimmer loading animation" or "Build an authentication flow with Cognito" and it retrieves the relevant recipe and source.

The second option installs skills that read component source directly from the local repository, with no server connection required:

npx skills add signerlabs/ShipSwift

The third option is manual file copy. Clone the repository, then copy the files you need from ShipSwift/SWPackage/ into your Xcode project. Each component in SWAnimation/, SWChart/, and SWComponent/ is self-contained; copy the file and SWUtil/ if needed.

To run the Showcase App from the repository:

git clone https://github.com/signerlabs/ShipSwift.git
cd ShipSwift
open ShipSwift.xcodeproj

Select a simulator or device and press Cmd+R to build and run.

Directory Structure and the SW Naming Convention

The library source lives under ShipSwift/SWPackage/ with subdirectories for each component group: SWAnimation/, SWChart/, SWComponent/ (which contains Display/, Feedback/, and Input/ subdirectories), SWModule/ (which contains SWAuth/, SWCamera/, SWPaywall/, SWChat/, and others), and SWUtil/.

The consistent SW prefix across all public types serves a practical purpose for AI-assisted development: a coding agent working in a codebase that uses ShipSwift can distinguish ShipSwift types from application types and system types immediately from the name alone. The .sw prefix for view modifiers follows the same logic, letting an agent recognize ShipSwift-provided modifiers in a SwiftUI view body without examining the import chain.

SWUtil contains shared utilities used by all other groups: DebugLog, String, Date, and View extensions, and a LocationManager. Its no-dependency rule means it can always be copied into a project first without any ordering concerns.

A companion repository, signerlabs/shipswift-skills, holds the skills definitions that the npx install uses. The README links there for Cursor, VS Code Copilot, Windsurf, and other MCP setup instructions beyond Claude Code and Gemini CLI.

Free vs Pro Recipes and the Commercial Development Service

ShipSwift divides its recipes into free and Pro tiers. The iOS client source code for all components is free and included in the open-source repository under the MIT license. Full-stack recipes that include backend guides, compliance templates, and documentation of known pitfalls are Pro. SWPaywall and SWTikTokTracking are specifically called out in the README as having their full-stack recipes behind the Pro tier; the iOS client portion is free in both cases.

The README also advertises a custom development service from the signerlabs team. The terms listed are a 48-hour working prototype, a 4-week delivery timeline, and a starting price of $5,000 with milestone-based billing. This service is built on the same component library in the repository.

For a developer evaluating whether to use ShipSwift in a production app, the free tier covers all the UI component source code. The Pro tier is relevant for teams that need a complete backend implementation for subscriptions or TikTok event attribution alongside the iOS client. The README does not describe a self-service sign-up for Pro; it directs interested parties to the pricing section at shipswift.app.

Limitations, Maintenance Status, and License

ShipSwift's MCP-first design is both its advantage and a constraint. The recommended setup requires an outbound connection to api.shipswift.app/mcp for Pro recipe access. Teams working in air-gapped environments or under strict outbound network policies must use the local skills option (Option 2), which limits access to the free recipes in the repository. The README confirms Option 2 works offline.

SWChat uses VolcEngine ASR for voice recognition. VolcEngine is a cloud service from ByteDance; integrating voice features requires an account and API key for that service, which is a dependency the README mentions but does not document in detail. Teams outside mainland China should verify that VolcEngine ASR is available and suitable for their compliance requirements before building on SWChat's voice features.

The last push was on 2026-08-09, about 7 weeks before 2026-09-28. The repository has no GitHub releases. The MIT license covers the iOS source code in the repository. The broader Apple ecosystem alternative for a component library without AI-first design is a framework like SwiftUI-Introspect or TCA (The Composable Architecture), which are well-established community libraries but document themselves for human developers rather than for AI agent retrieval. ShipSwift's differentiation is the explicit MCP interface and the skill-based delivery model, not the number or quality of individual components.

Editorial conclusion

ShipSwift is worth adopting for iOS developers who build primarily with AI coding agents and want a pre-built component library those agents can access via MCP rather than reading scattered documentation. The SW prefix convention and strict dependency rules make the library predictable for automated code generation. It is not the right fit for teams that need a purely offline, server-independent component library, since the recommended path requires connecting to the MCP server at api.shipswift.app/mcp for Pro recipes. Before starting, verify which recipes are free versus Pro by checking the pricing section at shipswift.app, since SWPaywall and SWTikTokTracking list their full-stack recipes as Pro-only.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Project website
4. README
5. signerlabs/ShipSwift on GitHub