### Install ShipSwift Skills using npx Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Installs ShipSwift skills and workflow instructions into your AI coding tool. This command is compatible with over 30 AI tools that support the Skills standard. ```bash # Install ShipSwift skills (works with 30+ AI tools) npx skills add signerlabs/shipswift-skills ``` -------------------------------- ### Connect MCP Recipe Server for Cursor Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures Cursor to connect to the ShipSwift recipe server by adding MCP configuration to the project's settings file. This allows Cursor to fetch SwiftUI recipes. ```json // .cursor/mcp.json { "mcpServers": { "shipswift": { "type": "streamableHttp", "url": "https://api.shipswift.app/mcp" } } } ``` -------------------------------- ### Connect MCP Recipe Server for Gemini CLI Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures Gemini CLI to connect to the ShipSwift recipe server using its built-in MCP command. This allows Gemini CLI to fetch and integrate SwiftUI recipes. ```bash # Add the ShipSwift MCP server to Gemini CLI gemini mcp add --transport http shipswift https://api.shipswift.app/mcp ``` -------------------------------- ### Connect MCP Recipe Server for Windsurf Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures Windsurf to connect to the ShipSwift recipe server by adding MCP configuration to the Windsurf config file. This integration allows Windsurf to utilize ShipSwift's SwiftUI recipes. ```json // ~/.codeium/windsurf/mcp_config.json { "mcpServers": { "shipswift": { "serverUrl": "https://api.shipswift.app/mcp" } } } ``` -------------------------------- ### Use listRecipes MCP Tool Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Demonstrates how to use the listRecipes MCP tool to retrieve ShipSwift recipes. Recipes can be listed all at once or filtered by category. ```text # AI tool usage - list all recipes Call MCP tool: listRecipes # AI tool usage - filter by category Call MCP tool: listRecipes with category: "animation" Call MCP tool: listRecipes with category: "chart" Call MCP tool: listRecipes with category: "component" Call MCP tool: listRecipes with category: "module" # Available categories and examples: # Animation (10): Shimmer, Typewriter, Glow Scan, Mesh Gradient, Orbit, Scan, Viewfinder, Before/After, Shaking Icon # Chart (8): Line, Bar, Area, Donut, Ring, Radar, Scatter, Heatmap # Component (14): Label, Alert, Loading, Stepper, Onboarding, Tab Button # Module (8): Auth (Cognito), Camera, Chat, Settings, Subscriptions, Infrastructure ``` -------------------------------- ### ShipSwift Naming Conventions and Patterns Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Demonstrates ShipSwift's naming conventions for SwiftUI components, including type names (SW prefix), view modifiers (.sw prefix), chart component patterns, animation techniques using masks, internal helper visibility, and corner radius parameters for clipping components. It also shows the dual API approach for overlay components. ```swift // ShipSwift naming conventions // Type names use SW prefix struct SWDonutChart: View { ... } struct SWShimmer: View { ... } struct SWTypewriter: View { ... } // View modifiers use .sw lowercase prefix Text("Loading...") .swShimmer() .swGlowScan() // Chart components use generic CategoryType pattern struct SWLineChart: View { // String convenience initializer available } // Chart animations use mask approach for line draw animation // (Swift Charts doesn't support built-in line draw animation) Rectangle() .mask(alignment: .leading) { GeometryReader { geometry in Rectangle() .frame(width: geometry.size.width * animationProgress) } } // Internal helpers are private with SW prefix private struct SWChartHelper { ... } // Components that clip content include cornerRadius parameter SWDonutChart(cornerRadius: 12) // Overlay components support both struct and modifier API SWShimmer() // Struct initializer .swShimmer() // View modifier ``` -------------------------------- ### Set Up Pro API Key Environment Variable Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Sets the ShipSwift API key as an environment variable for accessing Pro recipes. This key is automatically used by the MCP server for authentication. Remember to reload your shell configuration and restart your AI tool. ```bash # Add to ~/.zshrc or ~/.bashrc export SHIPSWIFT_API_KEY=sk_live_xxxxx # Reload your shell configuration source ~/.zshrc # Restart your AI tool to pick up the new environment variable ``` -------------------------------- ### MCP Server Configuration with Authentication Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures the MCP server for authenticated access to Pro recipes using an API key. The server reads the API key from the SHIPSWIFT_API_KEY environment variable. ```json // .mcp.json (Claude Code Plugin format) { "mcpServers": { "shipswift": { "type": "http", "url": "https://api.shipswift.app/mcp", "headers": { "Authorization": "Bearer ${SHIPSWIFT_API_KEY}" } } } } ``` -------------------------------- ### Connect MCP Recipe Server for VS Code Copilot Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures VS Code Copilot to connect to the ShipSwift recipe server by adding MCP configuration to VS Code's settings. This enables Copilot to access and integrate ShipSwift recipes. ```json // .vscode/mcp.json { "servers": { "shipswift": { "type": "http", "url": "https://api.shipswift.app/mcp" } } } ``` -------------------------------- ### Connect MCP Recipe Server for Claude Code Source: https://context7.com/signerlabs/shipswift-skills/llms.txt Configures Claude Code to connect to the ShipSwift recipe server via HTTP. This enables direct API access for managing SwiftUI recipes within Claude Code. ```bash # Add the ShipSwift MCP server to Claude Code claude mcp add --transport http shipswift https://api.shipswift.app/mcp # Restart Claude Code after adding the server ``` === COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.