要点
Expert SwiftUI code review, refactoring, and implementation guidance with iOS 26+ and macOS support.
- Covers state management, view composition, performance optimization, and modern SwiftUI patterns across iOS 15+ through iOS 26+
- Flags deprecated APIs and suggests modern replacements; gates version-specific features with
#availableand fallbacks - Addresses lists, layouts, animations, accessibility, Swift Charts, and platform-specific patterns (macOS scenes, Liquid Glass)
- Enforces correctness rules for property wrappers, ForEach identity, and view diffing; presents performance improvements as optional suggestions
SKILL.md
SwiftUI Expert Skill
Operating Rules
- Treat each
Viewtype as an invalidation boundary: give it only the data it reads and keep frequently changing dependencies close to the smallest affected subtree - Search
references/latest-apis.mdwhen writing, reviewing, or migrating API usage; look up only the APIs relevant to the task - Replace hard-deprecated APIs with modern equivalents. During feature work, flag soft-deprecated APIs and leave them in place (see
references/soft-deprecation.md) - Prefer native SwiftUI APIs over UIKit/AppKit bridging unless bridging is necessary
- Focus on correctness and performance; do not enforce specific architectures (MVVM, VIPER, etc.)
- Encourage separating business logic from views for testability without mandating how
- Follow Apple's Human Interface Guidelines and API design patterns
- Only adopt Liquid Glass when explicitly requested by the user (see
references/liquid-glass.md) - Present performance optimizations as suggestions, not requirements
- Use
#availablegating with sensible fallbacks for version-specific APIs - For layout and rendering inputs, read the value nearest the SwiftUI view that consumes it; do not substitute process-global screen state