Agent skill · software engineering · aiskillstore
swiftui-expert-skill
Write, review, and refactor SwiftUI for iOS or macOS, covering data flow, view composition, performance, identity, environment, localization, animation, API migration, and Instruments traces.
Why this skill is useful
Provides specific guidelines and best practices for SwiftUI development that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
SwiftUI Expert Skill When to Use Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management and @Observable data flow, view composition and invalidation/performance, lists and ForEach identity, environment usage, localization, animations, Liquid Glass adoption, migrating... Operating Rules Consult references/latest-apis.md at the start of every task to avoid deprecated APIs 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 #available gating with sensible fallbacks for version-specific APIs Task Workflow Review existing SwiftUI code Read the code under review and identify which topics apply Flag deprecated APIs (compare against references/latest-apis.md) Run the Topic Router below for each relevant topic Validate #available gating and fallback paths for iOS 26+ features Improve existing SwiftUI code Audit current implementation against the Topic Router topics Replace deprecated APIs with modern equivalents from references/latest-apis.md Refactor hot paths to reduce unnecessary state updates Extract complex view bodies into separate subviews Suggest image downsampling when UIImage(data:) is encountered (optional optimization, see references/image-optimization.md) Implement new SwiftUI feature Design data flow first: identify owned vs injected state Structure views for optimal diffing (extract subviews early) Apply correct animation patterns (implicit vs explicit, transitions) Use Button for all tappable elements; add accessibility grouping and labels Gate version-specific APIs with #avail …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/swiftui-expert-skill--44563d