SKILL.md
$27
-
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
-
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.
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
.swlowercase 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 and set SHIPSWIFT_API_KEY in their environment.