Add production-ready SwiftUI components to your project using ShipSwift's recipe library. Each recipe is a complete, copy-paste-ready implementation with architecture documentation.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionadd-componentExecute the skills CLI command in your project's root directory to begin installation:
Fetches add-component 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 add-component. Access via /add-component 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
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
22
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
22
stars
Add production-ready SwiftUI components to your project using ShipSwift's recipe library. Each recipe is a complete, copy-paste-ready implementation with architecture documentation.
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.
Identify the component type: Determine what kind of component the user needs:
Search for the recipe: Use searchRecipes with the component name or type. For example:
Fetch the full recipe: Use getRecipe with the recipe ID to get the complete implementation, including:
Integrate into the project: Adapt the recipe code to fit the user's project:
Verify integration: Walk through the recipe's integration checklist to ensure nothing is missed (dependencies, Info.plist entries, etc.).
SW-prefixed type names for ShipSwift components (e.g., SWDonutChart, SWTypewriter)..sw lowercase prefix (e.g., .swShimmer(), .swGlowScan()).CategoryType pattern with String convenience initializer..mask() approach with animated Rectangle width via GeometryReader -- Swift Charts does not support built-in line draw animation.private and use the SW prefix.cornerRadius parameter when components clip content.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.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend add-component for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added add-component from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
add-component reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: add-component is focused, and the summary matches what you get after install.
add-component is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for add-component matched our evaluation — installs cleanly and behaves as described in the markdown.
add-component fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in add-component — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added add-component from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: add-component is focused, and the summary matches what you get after install.
showing 1-10 of 75