← LeaderboardThe Skill Leaderboard

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.

Published by signerlabs ↗signerlabs/ShipSwift

Try your first task

Build a chart with a loading state

Start a fresh conversation.

Use the build-feature skill to build a small donut chart view with a shimmer loading state in my iOS project. Check the local catalog and component sources first, present the integration plan before writing code, then adapt the components to my data model. Include SWUtil, support Dark Mode and Dynamic Type, and provide an integration checklist.

Required inputs

  • The target iOS SwiftUI project.
  • The chart data model and loading-state behavior.
  • Access to skills/catalog.md and the local ShipSwift/SWPackage/ source tree.

Suggested template by Skill Leaderboard, grounded in the linked source. Task evidence ↗

SKILL.md

name: build-featuredescription: >  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 Skills (MCP)

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