mcpField
B
build-feature

build-feature

github.com/signerlabsDevelopment34784 installsUpdated 3d ago
Repository

About build-feature

A skill for building iOS features with ShipSwift's copy-ready SwiftUI recipes. It guides feature analysis, recipe search, integration planning, and code adaptation for developers assembling UI and full-stack components.

Key features

  1. 01Search ShipSwift recipes
  2. 02Fetch full recipe implementations
  3. 03Plan recipe integration
  4. 04Adapt code to project structure
  5. 05Provide setup checklists

Use cases

  1. 01Build a chart with loading animation
  2. 02Assemble a feature across UI and backend
  3. 03Adapt recipe code for an iOS project

MCP support

It uses the ShipSwift recipe server, checking availability with `listRecipes` and retrieving recipes through `searchRecipes` and `getRecipe`.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/signerlabs/shipswift-skills --skill build-feature

After installing, type/build-featurein Claude Code to confirm it loaded.

Details

From the project README

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 tools are not available, guide the user to visit shipswift.app for setup instructions, or run npx skills add signerlabs/shipswift-skills to install.

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 a Pro license ($89 one-time). If a recipe returns a purchase prompt, the user can buy at shipswift.app/pricing and set SHIPSWIFT_API_KEY in their environment.

Comments

Markdown supported