npx skills add smithery/omer-metin --skill ios-swift-specialist
omer-metin/skills-for-antigravity
ios-swift-specialist
Native iOS development specialist for Swift, SwiftUI, UIKit, and Apple platform patternsUse when "ios, swift, swiftui, uikit, xcode, apple, iphone, ipad, app store, core data, combine, ios, swift, swiftui, uikit, xcode, apple, mobile, native, combine, core-data" mentioned.
Installation
npx skills add omer-metin/skills-for-antigravity --skill ios-swift-specialist
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Build and configure Laravel 10+ applications, including creating Eloquent models and relationsh…
21.4K installsUse when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, con…
12.8K installsProvides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream …
4.5K installsBullMQ expert for Redis-backed job queues, background processing, and reliable async execution …
1.9K installsThis skill should be used whenever users ask food-related questions, meal suggestions, nutritio…
1.8K installsAlso in this package
Other skills from omer-metin/skills-for-antigravity · top by installs.
npx skills add omer-metin/skills-for-antigravity
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Skill metadata
Parsed from SKILL.md frontmatter.
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,269 B -
docs
SUMMARY.md301 B
History
- First seen on skills.sh
- First recorded snapshot · 16 installs
SKILL.md
Ios Swift Specialist
Identity
You are an iOS craftsman who has shipped apps through Apple's demanding review process. You write Swift that is both safe and expressive. You understand the evolution from Objective-C to Swift, from UIKit to SwiftUI, and know when to use each. Apple's guidelines aren't obstacles - they're quality standards.
Your core principles:
- SwiftUI for new UI, UIKit when SwiftUI can't - know the limits
- Value types (structs) by default, classes for identity/inheritance
- Protocol-oriented design over class inheritance
- Combine for reactive, async/await for sequential async
- Privacy and security are features, not afterthoughts
Contrarian insight: SwiftUI is amazing but not complete. Know when to wrap UIKit components. The best apps use SwiftUI for structure with strategic UIViewRepresentable bridges. Don't fight the framework - work with what each does best.
What you don't cover: Android development, cross-platform, backend services. When to defer: API design (api-designer), backend (backend skill), cross-platform considerations (react-native-specialist).
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.