Agent skills for iOS, iPadOS, Swift, SwiftUI, and modern Apple framework development.
71
89%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Platform-specific focus behaviors beyond the common SwiftUI and UIKit patterns covered in the main SKILL.md.
tvOS uses a geometric focus model: the focus engine evaluates the spatial positions of focusable items and moves focus in the direction the user swipes on the Siri Remote.
UIFocusEnvironment.preferredFocusEnvironments determines the preferred
destination when focus enters a container.UIFocusUpdateContext provides previouslyFocusedItem, nextFocusedItem,
focusHeading, and animationCoordinator.override func collectionView(
_ collectionView: UICollectionView,
canFocusItemAt indexPath: IndexPath
) -> Bool {
// Prevent focus on disabled cells
let item = dataSource.itemIdentifier(for: indexPath)
return item?.isEnabled ?? false
}
override func collectionView(
_ collectionView: UICollectionView,
didUpdateFocusIn context: UIFocusUpdateContext,
with coordinator: UIFocusAnimationCoordinator
) {
coordinator.addCoordinatedFocusingAnimations { _ in
context.nextFocusedView?.transform = CGAffineTransform(scaleX: 1.1, y: 1.1)
} completion: {}
coordinator.addCoordinatedUnfocusingAnimations { _ in
context.previouslyFocusedView?.transform = .identity
} completion: {}
}focusSection() (tvOS 15+) groups focusable children in SwiftUI so the focus
engine treats them as a navigable region:
HStack {
VStack {
ForEach(sidebarItems) { item in
Button(item.title) { select(item) }
}
}
.focusSection()
LazyVGrid(columns: columns) {
ForEach(gridItems) { item in
CardView(item: item)
}
}
.focusSection()
}Without focusSection(), swiping right from the sidebar might land on a grid
item at the wrong vertical position.
watchOS uses the Digital Crown as its primary navigation input alongside
touch. SwiftUI provides digitalCrownRotation(_:) to track crown input.
Docs: digitalCrownRotation
struct CrownScrollView: View {
@State private var offset: Double = 0
var body: some View {
ScrollView {
VStack {
ForEach(items) { item in
ItemRow(item: item)
}
}
}
.digitalCrownRotation($offset, from: 0, through: 100)
}
}Focus on watchOS is simpler than tvOS — most views are linearly scrollable and focus is implicit via the crown/scroll position.
visionOS uses gaze and hand tracking for focus. The system determines which element the user is looking at and highlights it. Pinch gestures act as taps.
All interactive elements get automatic hover effects in visionOS. Customize
with .hoverEffect(_:):
Button("Action") { }
.hoverEffect(.highlight) // Default for buttons
.hoverEffect(.lift) // Raises the elementIn RealityKit scenes, use InputTargetComponent and HoverEffectComponent
to make entities respond to gaze:
let entity = ModelEntity(mesh: .generateBox(size: 0.1))
entity.components.set(InputTargetComponent())
entity.components.set(HoverEffectComponent())
entity.components.set(CollisionComponent(shapes: [.generateBox(size: [0.1, 0.1, 0.1])]))Users who cannot use gaze tracking rely on Switch Control, Voice Control, or pointer devices. Ensure all focusable elements have proper accessibility labels and traits.
UIKit-based macOS Catalyst apps and AppKit apps use the key view loop to
determine Tab order. NSView.nextKeyView chains views together.
SwiftUI on macOS uses @FocusState identically to iOS, with Tab moving
focus between fields by default.
// AppKit: make a custom view focusable
class CustomControl: NSView {
override var acceptsFirstResponder: Bool { true }
override var canBecomeKeyView: Bool { true }
override func becomeFirstResponder() -> Bool {
needsDisplay = true
return true
}
override func resignFirstResponder() -> Bool {
needsDisplay = true
return true
}
}macOS Full Keyboard Access (System Settings → Keyboard → Keyboard Navigation) enables Tab focus on all controls, not just text fields. Test your app with this setting enabled.
skills
accessorysetupkit
references
activitykit
references
adattributionkit
references
alarmkit
references
app-clips
app-intents
references
app-store-optimization
app-store-review
apple-on-device-ai
appmigrationkit
references
audioaccessorykit
references
authentication
references
avkit
references
background-processing
references
browserenginekit
references
callkit
references
carplay
references
cloudkit
references
contacts-framework
references
core-bluetooth
references
core-data
core-motion
references
core-nfc
references
coreml
references
cryptokit
references
cryptotokenkit
references
debugging-instruments
device-integrity
references
dockkit
references
energykit
references
eventkit
references
financekit
references
focus-engine
gamekit
references
healthkit
references
homekit
references
ios-accessibility
ios-localization
ios-networking
ios-simulator
references
mapkit
metrickit
references
musickit
references
natural-language
references
paperkit
references
passkit
references
pdfkit
references
pencilkit
references
permissionkit
references
photokit
push-notifications
realitykit
references
relevancekit
references
scenekit
references
sensorkit
references
speech-recognition
spritekit
references
storekit
swift-api-design-guidelines
swift-architecture
swift-charts
references
swift-codable
swift-concurrency
swift-formatstyle
swift-language
swift-security
references
swift-testing
swiftdata
swiftlint
swiftui-animation
swiftui-gestures
references
swiftui-layout-components
swiftui-liquid-glass
references
swiftui-patterns
swiftui-performance
swiftui-uikit-interop
swiftui-webkit
tabletopkit
references
tipkit
references
vision-framework
weatherkit
references
widgetkit
references