System Prompt / Instructions
SwiftUI Expert Skill
Overview
Use this skill to build, review, or improve SwiftUI features with correct state management, modern API usage, Swift concurrency best practices, optimal view composition, and iOS 26+ Liquid Glass styling. Prioritize native APIs, Apple design guidance, and performance-conscious patterns. This skill focuses on facts and best practices without enforcing specific architectural patterns.
When to Use This Skill
Use this skill when:
- Building new SwiftUI features
- Refactoring existing SwiftUI views
- Reviewing SwiftUI code quality
- Adopting modern SwiftUI patterns
- Working with SwiftUI state management
- Implementing iOS 26+ Liquid Glass styling
Workflow Decision Tree
1) Review existing SwiftUI code
- Check property wrapper usage against the selection guide (see
references/state-management.md) - Verify modern API usage (see
references/modern-apis.md) - Verify view composition follows extraction rules (see
references/view-structure.md) - Check performance patterns are applied (see
references/performance-patterns.md) - Verify list patterns use stable identity (see
references/list-patterns.md) - Inspect Liquid Glass usage for correctness and consistency (see
references/liquid-glass.md) - Validate iOS 26+ availability handling with sensible fallbacks
2) Improve existing SwiftUI code
- Audit state management for correct wrapper selection (prefer
@ObservableoverObservableObject) - Replace deprecated APIs with modern equivalents (see
references/modern-apis.md) - Extract complex views into separate subviews (see
references/view-structure.md) - Refactor hot paths to minimize redundant state updates (see
references/performance-patterns.md) - Ensure ForEach uses stable identity (see
references/list-patterns.md) - Suggest image downsampling when
UIImage(data:)is used (as optional optimization, seereferences/image-optimization.md) - Adopt Liquid Glass only when explicitly requested by the user
3) Implement new SwiftUI feature
- Design data flow first: identify owned vs injected state (see
references/state-management.md) - Use modern APIs (no deprecated modifiers or patterns, see
references/modern-apis.md) - Use
@Observablefor shared state (with@MainActorif not using default actor isolation) - Structure views for optimal diffing (extract subviews early, keep views small, see
references/view-structure.md) - Separate business logic into testable models (see
references/layout-best-practices.md) - Apply glass effects after layout/appearance modifiers (see
references/liquid-glass.md) - Gate iOS 26+ features with
#availableand provide fallbacks
Core Guidelines
State Management
- Always prefer
@ObservableoverObservableObjectfor new code - Mark
@Observableclasses with@MainActorunless using default actor isolation - Always mark
@Stateand@StateObjectasprivate(makes dependencies clear) - Never declare passed values as
@Stateor@StateObject(they only accept initial values) - Use
@Statewith@Observableclasses (not@StateObject) @Bindingonly when child needs to modify parent state@Bindablefor injected@Observableobjects needing bindings- Use
letfor read-only values;var+.onChange()for reactive reads - Legacy:
@StateObjectfor ownedObservableObject;@ObservedObjectfor injected - Nested
ObservableObjectdoesn't work (pass nested objects directly);@Observablehandles nesting fine
Modern APIs
- Use
foregroundStyle()instead offoregroundColor() - Use
clipShape(.rect(cornerRadius:))instead ofcornerRadius() - Use
TabAPI instead oftabItem() - Use
Buttoninstead ofonTapGesture()(unless need location/count) - Use
NavigationStackinstead ofNavigationView - Use
navigationDestination(for:)for type-safe navigation - Use two-parameter or no-parameter
onChange()variant - Use
ImageRendererfor rendering SwiftUI views - Use
.sheet(item:)instead of.sheet(isPresented:)for model-based content - Sheets should own their actions and call
dismiss()internally - Use
ScrollViewReaderfor programmatic scrolling with stable IDs - Avoid
UIScreen.main.boundsfor sizing - Avoid
GeometryReaderwhen alternatives exist (e.g.,containerRelativeFrame())
Swift Best Practices
- Use modern Text formatting (
.formatparameters, notString(format:)) - Use
localizedStandardContains()for user-input filtering (notcontains()) - Prefer static member lookup (
.bluevsColor.blue) - Use
.taskmodifier for automatic cancellation of async work - Use
.task(id:)for value-dependent tasks
View Composition
- Prefer modifiers over conditional views for state changes (maintains view identity)
- Extract complex views into separate subviews for better readability and performance
- Keep views small for optimal performance
- Keep view
bodysimple and pure (no side effects or complex logic) - Use
@ViewBuilderfunctions only for small, simple sections - Prefer
@ViewBuilder let content: Contentover closure-based content properties - Separate business logic into testable models (not about enforcing architectures)
- Action handlers should reference methods, not contain inline logic
- Use relative layout over hard-coded constants
- Views should work in any context (don't assume screen size or presentation style)
Performance
- Pass only needed values to views (avoid large "config" or "context" objects)
- Eliminate unnecessary dependencies to reduce update fan-out
- Check for value changes before assigning state in hot paths
- Avoid redundant state updates in
onReceive,onChange, scroll handlers - Minimize work in frequently executed code paths
- Use
LazyVStack/LazyHStackfor large lists - Use stable identity for
ForEach(never.indicesfor dynamic content) - Ensure constant number of views per
ForEachelement - Avoid inline filtering in
ForEach(prefilter and cache) - Avoid
AnyViewin list rows - Consider POD views for fast diffing (or wrap expensive views in POD parents)
- Suggest image downsampling when
UIImage(data:)is encountered (as optional optimization) - Avoid layout thrash (deep hierarchies, excessive
GeometryReader) - Gate frequent geometry updates by thresholds
- Use
Self._printChanges()to debug unexpected view updates
Liquid Glass (iOS 26+)
Only adopt when explicitly requested by the user.
- Use native
glassEffect,GlassEffectContainer, and glass button styles - Wrap multiple glass elements in
GlassEffectContainer - Apply
.glassEffect()after layout and visual modifiers - Use
.interactive()only for tappable/focusable elements - Use
glassEffectIDwith@Namespacefor morphing transitions
Quick Reference
Property Wrapper Selection (Modern)
| Wrapper | Use When |
|---------|----------|
| @State | Internal view state (must be private), or owned @Observable class |
| @Binding | Child modifies parent's state |
| @Bindable | Injected @Observable needing bindings |
| let | Read-only value from parent |
| var | Read-only value watched via .onChange() |
Legacy (Pre-iOS 17):
| Wrapper | Use When |
|---------|----------|
| @StateObject | View owns an ObservableObject (use @State with @Observable instead) |
| @ObservedObject | View receives an ObservableObject |
Modern API Replacements
| Deprecated | Modern Alternative |
|------------|-------------------|
| foregroundColor() | foregroundStyle() |
| cornerRadius() | clipShape(.rect(cornerRadius:)) |
| tabItem() | Tab API |
| onTapGesture() | Button (unless need location/count) |
| NavigationView | NavigationStack |
| onChange(of:) { value in } | onChange(of:) { old, new in } or onChange(of:) { } |
| fontWeight(.bold) | bold() |
| GeometryReader | containerRelativeFrame() or visualEffect() |
| showsIndicators: false | .scrollIndicators(.hidden) |
| String(format: "%.2f", value) | Text(value, format: .number.precision(.fractionLength(2))) |
| string.contains(search) | string.localizedStandardContains(search) (for user input) |
Liquid Glass Patterns
// Basic glass effect with fallback
if #available(iOS 26, *) {
content
.padding()
.glassEffect(.regular.interactive(), in: .rect(cornerRadius: 16))
} else {
content
.padding()
.background(.ultraThinMaterial, in: RoundedRectangle(cornerRadius: 16))
}
// Grouped glass elements
GlassEffectContainer(spacing: 24) {
HStack(spacing: 24) {
GlassButton1()
GlassButton2()
}
}
// Glass buttons
Button("Confirm") { }
.buttonStyle(.glassProminent)
Review Checklist
State Management
- [ ] Using
@Observableinstead ofObservableObjectfor new code - [ ]
@Observableclasses marked with@MainActor(if needed) - [ ] Using
@Statewith@Observableclasses (not@StateObject) - [ ]
@Stateand@StateObjectproperties areprivate - [ ] Passed values NOT declared as
@Stateor@StateObject - [ ]
@Bindingonly where child modifies parent state - [ ]
@Bindablefor injected@Observableneeding bindings - [ ] Nested
ObservableObjectavoided (or passed directly to child views)
Modern APIs (see references/modern-apis.md)
- [ ] Using
foregroundStyle()instead offoregroundColor() - [ ] Using
clipShape(.rect(cornerRadius:))instead ofcornerRadius() - [ ] Using
TabAPI instead oftabItem() - [ ] Using
Buttoninstead ofonTapGesture()(unless need location/count) - [ ] Using
NavigationStackinstead ofNavigationView - [ ] Avoiding
UIScreen.main.bounds - [ ] Using alternatives to
GeometryReaderwhen possible - [ ] Button images include text labels for accessibility
Sheets & Navigation (see references/sheet-navigation-patterns.md)
- [ ] Using
.sheet(item:)for model-based sheets - [ ] Sheets own their actions and dismiss internally
- [ ] Using
navigationDestination(for:)for type-safe navigation
ScrollView (see references/scroll-patterns.md)
- [ ] Using
ScrollViewReaderwith stable IDs for programmatic scrolling - [ ] Using
.scrollIndicators(.hidden)instead of initializer parameter
Text & Formatting (see references/text-formatting.md)
- [ ] Using modern Text formatting (not
String(format:)) - [ ] Using
localizedStandardContains()for search filtering
View Structure (see references/view-structure.md)
- [ ] Using modifiers instead of conditionals for state changes
- [ ] Complex views extracted to separate subviews
- [ ] Views kept small for performance
- [ ] Container views use
@ViewBuilder let content: Content
Performance (see references/performance-patterns.md)
- [ ] View
bodykept simple and pure (no side effects) - [ ] Passing only needed values (not large config objects)
- [ ] Eliminating unnecessary dependencies
- [ ] State updates check for value changes before assigning
- [ ] Hot paths minimize state updates
- [ ] No object creation in
body - [ ] Heavy computation moved out of
body
List Patterns (see references/list-patterns.md)
- [ ] ForEach uses stable identity (not
.indices) - [ ] Constant number of views per ForEach element
- [ ] No inline filtering in ForEach
- [ ] No
AnyViewin list rows
Layout (see references/layout-best-practices.md)
- [ ] Avoiding layout thrash (deep hierarchies, excessive GeometryReader)
- [ ] Gating frequent geometry updates by thresholds
- [ ] Business logic separated into testable models
- [ ] Action handlers reference methods (not inline logic)
- [ ] Using relative layout (not hard-coded constants)
- [ ] Views work in any context (context-agnostic)
Liquid Glass (iOS 26+)
- [ ]
#available(iOS 26, *)with fallback for Liquid Glass - [ ] Multiple glass views wrapped in
GlassEffectContainer - [ ]
.glassEffect()applied after layout/appearance modifiers - [ ]
.interactive()only on user-interactable elements - [ ] Shapes and tints consistent across related elements
References
references/state-management.md- Property wrappers and data flow (prefer@Observable)references/view-structure.md- View composition, extraction, and container patternsreferences/performance-patterns.md- Performance optimization techniques and anti-patternsreferences/list-patterns.md- ForEach identity, stability, and list best practicesreferences/layout-best-practices.md- Layout patterns, context-agnostic views, and testabilityreferences/modern-apis.md- Modern API usage and deprecated replacementsreferences/sheet-navigation-patterns.md- Sheet presentation and navigation patternsreferences/scroll-patterns.md- ScrollView patterns and programmatic scrollingreferences/text-formatting.md- Modern text formatting and string operationsreferences/image-optimization.md- AsyncImage, image downsampling, and optimizationreferences/liquid-glass.md- iOS 26+ Liquid Glass API
Philosophy
This skill focuses on facts and best practices, not architectural opinions:
- We don't enforce specific architectures (e.g., MVVM, VIPER)
- We do encourage separating business logic for testability
- We prioritize modern APIs over deprecated ones
- We emphasize thread safety with
@MainActorand@Observable - We optimize for performance and maintainability
- We follow Apple's Human Interface Guidelines and API design patterns
Frequently Asked Questions
What is swiftui-expert-skill?
swiftui-expert-skill is an expert AI persona designed to improve your coding workflow. Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns. It provides senior-level context directly within your IDE.
How do I install the swiftui-expert-skill skill in Cursor or Windsurf?
To install the swiftui-expert-skill skill, download the package, extract the files to your project's .cursor/skills directory, and type @swiftui-expert-skill in your editor chat to activate the expert instructions.
Is swiftui-expert-skill free to download?
Yes, the swiftui-expert-skill AI persona is completely free to download and integrate into compatible Agentic IDEs like Cursor, Windsurf, Github Copilot, and Anthropic MCP servers.
swiftui-expert-skill
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, modern APIs, Swift concurrency, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
Download Skill PackageIDE Invocation
Platform
Price
Setup Instructions
Cursor & Windsurf
- Download the zip file above.
- Extract to
.cursor/skills - Type
@swiftui-expert-skillin editor chat.
Copilot & ChatGPT
Copy the instructions from the panel on the left and paste them into your custom instructions setting.
"Adding this swiftui-expert-skill persona to my Cursor workspace completely changed the quality of code my AI generates. Saves me hours every week."
Level up further
Developers who downloaded swiftui-expert-skill also use these elite AI personas.
3d-web-experience
Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when: 3D website, three.js, WebGL, react three fiber, 3D experience.
ab-test-setup
Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.
accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.