Individual skill
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.
skills/ios-swift-specialist/SKILL.md
Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 206
- Repository last updated
- Jan 22, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- antigravity Repository topic
- antigravity-ide Repository topic
- skills Repository topic
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,269 bytesSKILL.mdcore · 2,269 bytesreferences/patterns.mddoc · 7,832 bytesreferences/sharp_edges.mddoc · 11,645 bytesreferences/validations.mddoc · 4,321 bytes
Read excerpt
# 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:
1. SwiftUI for new UI, UIKit when SwiftUI can't - know the limits
2. Value types (structs) by default, classes for identity/inheritance
3. Protocol-oriented design over class inheritance