Agent skill · avdlee
swiftui-expert-skill
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 soft-deprecated APIs, or Instruments `.trace` capture/analysis for hangs, hitches, CPU hotspots, or
What it needs
About 6k tokens when loaded.
What this skill does
SwiftUI Expert Skill 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 #available and provide fallbacks Record a new Instruments trace Trigger when the user asks to "record a trace", "profile the app", "capture a session", etc. Full reference: references/trace-recording.md. 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills avdlee/swiftui-expert-skill--3d7f18