Build production-ready iOS features by combining ShipSwift recipes -- copy-paste-ready SwiftUI implementations covering animations, charts, UI components, and full-stack modules.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuild-featureExecute the skills CLI command in your project's root directory to begin installation:
Fetches build-feature from signerlabs/shipswift-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate build-feature. Access via /build-feature in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
22
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22
stars
Build production-ready iOS features by combining ShipSwift recipes -- copy-paste-ready SwiftUI implementations covering animations, charts, UI components, and full-stack modules.
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.
Analyze the request: Break down the user's feature request into discrete components (UI, data, navigation, backend integration).
Search for recipes: Use searchRecipes with relevant keywords to find matching ShipSwift recipes. Try multiple search terms if the first query returns few results.
Fetch full implementations: Use getRecipe for each relevant recipe to get the complete source code, architecture explanation, and integration checklist.
Present an integration plan: Before writing code, show the user:
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).
Provide integration checklist: List any required dependencies, Info.plist entries, or environment setup from the recipe documentation.
SW-prefixed naming conventions for ShipSwift components (e.g., SWShimmer, SWDonutChart)..sw lowercase prefix (e.g., .swShimmer(), .swGlowScan()).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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
build-feature is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
build-feature fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for build-feature matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: build-feature is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: build-feature is focused, and the summary matches what you get after install.
We added build-feature from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for build-feature matched our evaluation — installs cleanly and behaves as described in the markdown.
We added build-feature from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: build-feature is focused, and the summary matches what you get after install.
Keeps context tight: build-feature is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 34