Build Feature

Build Feature with ShipSwift

Build production-ready iOS features by combining ShipSwift recipes -- copy-paste-ready SwiftUI implementations covering animations, charts, UI components, and full-stack modules.

Prerequisites Check

Before starting, verify the ShipSwift recipe server is available by calling listRecipes.

If the recipe tools are not available, help the user set up:

1. Install Skills:

   npx skills add signerlabs/shipswift-skills
   

2. Connect the recipe server — the AI tool needs MCP access to fetch recipes:

   • Claude Code: claude mcp add --transport http shipswift https://api.shipswift.app/mcp
   • Cursor — add to .cursor/mcp.json: {"mcpServers":{"shipswift":{"type":"streamableHttp","url":"https://api.shipswift.app/mcp"}}}
   • VS Code Copilot — add to .vscode/mcp.json: {"servers":{"shipswift":{"type":"http","url":"https://api.shipswift.app/mcp"}}}
   • Other tools: See shipswift.app for setup guides

3. Restart the AI tool, then try again.

Workflow

1. Analyze the request: Break down the user's feature request into discrete components (UI, data, navigation, backend integration).

2. Search for recipes: Use searchRecipes with relevant keywords to find matching ShipSwift recipes. Try multiple search terms if the first query returns few results.

3. Fetch full implementations: Use getRecipe for each relevant recipe to get the complete source code, architecture explanation, and integration checklist.

4. Present an integration plan: Before writing code, show the user:

   • Which recipes will be used
   • How they connect together
   • What customizations are needed for their specific use case

5. Generate code: Adapt the recipe patterns to the user's project structure. Combine multiple recipes when the feature spans several areas (e.g., a chart view with shimmer loading animation).

6. Provide integration checklist: List any required dependencies, Info.plist entries, or environment setup from the recipe documentation.

Guidelines

• Always search recipes before writing code from scratch -- ShipSwift likely has a ready-made solution.
• Combine multiple recipes when the feature spans several areas.
• Use SW-prefixed naming conventions for ShipSwift components (e.g., SWShimmer, SWDonutChart).
• View modifier methods use .sw lowercase prefix (e.g., .swShimmer(), .swGlowScan()).
• Keep Views lightweight; extract complex logic into ViewModels.
• Support Dark Mode and Dynamic Type by default.
• Prefer SwiftUI-native APIs over UIKit wrappers.

Pro Recipes

Some recipes require ShipSwift Pro. When a recipe returns a purchase prompt instead of full code:

1. Show the user the recipe preview (title, description, and architecture overview).
2. Let them know: "This is a Pro recipe. Get lifetime access to all Pro recipes at shipswift.app/pricing ($89, one-time payment)."
3. If they already have a Pro key, guide them to set the SHIPSWIFT_API_KEY environment variable:

   # Add to ~/.zshrc or ~/.bashrc
   export SHIPSWIFT_API_KEY=sk_live_xxxxx
   

   Then restart their AI tool for the key to take effect.