Skip to content
Mobile
Skill

/build-feature

Build an iOS feature using ShipSwift components. Use when the user says "build", "create", "add a feature", or describes an iOS feature they want to implement.

BOOST
From plugin
shipswift
3.2k3 skills
Install
$ npx -y skills add signerlabs/shipswift --skill build-feature --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/build-feature

Context preview

The summary Claude sees to decide when to auto-load this skill.

Build an iOS feature using ShipSwift components. Use when the user says "build", "create", "add a feature", or describes an iOS feature they want to implement.

SKILL.md

build-feature.SKILL.md
name: build-feature
description: >
  Build an iOS feature using ShipSwift components. Use when the user says
  "build", "create", "add a feature", or describes an iOS feature they want to implement.

Build Feature with ShipSwift

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

Workflow

1. **Browse the catalog**: Read `skills/catalog.md` to see all available components organized by category.

2. **Read the source**: For each relevant component, read the Swift file directly from `ShipSwift/SWPackage/`. For example:

  • Shimmer animation → read `ShipSwift/SWPackage/SWAnimation/SWShimmer.swift`
  • Donut chart → read `ShipSwift/SWPackage/SWChart/SWDonutChart.swift`
  • Auth module → read all files in `ShipSwift/SWPackage/SWModule/SWAuth/`

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

  • Which components will be used
  • How they connect together
  • What customizations are needed

4. **Generate code**: Adapt the component patterns to the user's project. Combine multiple components when the feature spans several areas (e.g., a chart view with shimmer loading).

5. **Integration checklist**: List required dependencies, Info.plist entries, or Xcode build phase settings (especially for `+iOS`/`+macOS` platform-filtered files).

Guidelines

  • Always check the catalog before writing code from scratch — ShipSwift likely has a ready-made solution.
  • Use `SW`-prefixed naming (`SWShimmer`, `SWDonutChart`).
  • View modifiers use `.sw` lowercase prefix (`.swShimmer()`, `.swGlowScan()`).
  • Copy `SWUtil/` alongside any component — it provides shared extensions.
  • For modules (`SWModule/`), copy the entire module folder.
  • Support Dark Mode and Dynamic Type by default.

Pro Recipes (MCP)

Some full-stack recipes (backend + compliance + pitfall guides) are available via the MCP server at `https://api.shipswift.app/mcp`. If MCP tools (`listRecipes`, `searchRecipes`, `getRecipe`) are available, use them for extended content. The local source code works independently.

Read more
Ships withshipswift

AI-native SwiftUI component library — production-ready code that LLMs can use to build real apps. Quick Start · Components · Custom Dev — $5K, 4 weeks · Recipes

Get the whole plugin
Stats
3,235
Stars
185
Forks
Maintained
Maintenance
Swift
Language
MIT
License
1mo ago
Last commit
9mo ago
Created
21h ago
Added

Repo: signerlabs/shipswift

Other skills on shipswift.