Build Feature
Ship a SwiftUI iOS feature by finding ShipSwift recipes, planning how they connect, and adapting production-ready patterns to your app.
Overview
Build-feature is an agent skill for the Build phase that implements iOS SwiftUI features by searching ShipSwift recipes, publishing an integration plan, and adapting shipped recipe code to the user's project.
Install
npx skills add https://github.com/signerlabs/shipswift-skills --skill build-featureWhat is this skill?
- Verifies ShipSwift availability via listRecipes before any implementation work
- searchRecipes with keyword iteration and getRecipe for full source, architecture notes, and integration checklists
- Requires an integration plan listing recipes, connections, and customizations before code generation
- Covers animations, charts, UI components, and full-stack module recipes from shipswift.app
- Install path: npx skills add signerlabs/shipswift-skills when MCP tools are missing
Adoption & trust: 594 installs on skills.sh; 28 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You described an iOS feature but lack a fast path from idea to wired SwiftUI modules without stitching random snippets by hand.
Who is it for?
Solo builders adding SwiftUI screens, charts, or animated flows when the ShipSwift recipe MCP is installed and reachable.
Skip if: Android or cross-platform Flutter builds, greenfield apps with no SwiftUI project, or feature work when listRecipes fails and you refuse to install ShipSwift tooling.
When should I use this skill?
User says build, create, add a feature, or describes an iOS feature to implement with ShipSwift component recipes.
What do I get? / Deliverables
You get a recipe-backed integration plan and adapted SwiftUI implementation aligned to ShipSwift patterns and your app structure.
- Integration plan mapping recipes and customizations
- Adapted SwiftUI source following recipe patterns
- Per-recipe integration checklist items addressed
Recommended Skills
Journey fit
Build is where feature implementation happens; this skill is invoked when the user wants to create or add an iOS feature, not during idea or launch work. Frontend fits because the workflow centers on SwiftUI UI modules, animations, charts, and client-side composition from recipe catalogs.
How it compares
Recipe-driven SwiftUI integration skill backed by ShipSwift MCP—not a generic mobile codegen prompt without cataloged implementations.
Common Questions / FAQ
Who is build-feature for?
Indie and solo iOS developers using agentic coding tools who want ShipSwift’s catalog-driven SwiftUI implementations instead of one-off generated UI.
When should I use build-feature?
During build/frontend when the user says build, create, or add an iOS feature and you need to search recipes, plan integration, then generate adapted SwiftUI code.
Is build-feature safe to install?
Check the Security Audits panel on this Prism page; recipe fetch uses MCP/network APIs and generated code should be reviewed like any third-party UI source.
SKILL.md
READMESKILL.md - 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 tools are not available, guide the user to visit [shipswift.app](https://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](https://shipswift.app/pricing) and set `SHIPSWIFT_API_KEY` in their environment.