swiftui-expert-skill
Skill2 starsChanged 8 months agoMITView on GitHub
Write, review, or improve SwiftUI code following best practices for state management, view composition, performance, and iOS 26+ Liquid Glass adoption. Use when building new SwiftUI features, refactoring existing views, reviewing code quality, or adopting modern SwiftUI patterns.
25 other projects use a version of this, 14 of them edited.
Adopted by
Most recently taken up by
- alexj11324/Mikkatheir own version, first seen Nov 15, 2026
- taixuann/development-spacetheir own version, first seen Nov 8, 2026
- tornikegomareli/Skillstheir own version, first seen Nov 8, 2026
- uinaf/slopwaketheir own version, first seen Nov 3, 2026
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificertheir own version, first seen Nov 1, 2026
- deonmenezes/mobile-app-skilltheir own version, first seen Nov 1, 2026
Used with
Projects with it also use swift-concurrency, swiftui-ui-patterns and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jamesrochabrunSkillswift-concurrency
Guide for building, auditing, and refactoring Swift code using modern concurrency patterns (Swift 6+). This skill should be used when working with async/await, Tasks, actors, MainActor, Sendable types, isolation domains, or when migrating legacy callback/Combine code to structured concurrency. Covers Approachable Concurrency settings, isolated parameters, and common pitfalls.
Also in 8 projects that use this
OpenAISkillswiftui-ui-patterns
Build and refactor SwiftUI UI with component patterns and examples. Use when shaping navigation, state, layouts, controls, or screen composition.
Also in 5 projects that use this
AvdLeeSkillswift-testing-expert
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and maintainability in Apple-platform or Swift server projects.
Also in 3 projects that use this
OpenAISkillswiftui-performance-audit
Audit SwiftUI runtime performance from code first. Use when diagnosing slow rendering, janky scrolling, expensive updates, or profiling needs.
Also in 4 projects that use this
kingsidharthSkillswiftui-pro
Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
Also in 5 projects that use this
eugenepyvovarovSkillswift-concurrency-expert
Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.
Also in 3 projects that use this
- +2 more from openai
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 14
- Provenance-Emu/Provenance★ 6.4k73% same
- pablopunk/SwiftShift★ 66417% same
- anyproto/anytype-swift★ 52573% same
- AFK-surf/OpenBridge★ 43061% same
- sledtools/pika★ 4555% same
- nonameplum/agent-skills★ 1755% same
- xfstudio/skills★ 953% same
- tenondecrpc/tempo-for-claude★ 417% same
- ai4brands-design/claude-skills★ 253% same
- shashwattrili/reclaude★ 217% same
4 more not listed
Wrote their own version · 11
- AvdLee/SwiftUI-Agent-Skill★ 3.9ksame name
- omarshahine/HomeClaw★ 194same name
- alexj11324/Mikka★ 87same name
- RubenGlez/lokalite★ 8same name
- The-Artificer-of-Ciphers-LLC/skills-from-the-artificer★ 6same name
- deonmenezes/mobile-app-skill★ 4same name
- tornikegomareli/Skills★ 2same name
- taixuann/development-space★ 1same name
- hebertzhu/agent-foundry★ 0same name
- omega1119/groundwork★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-native-cliSkill
- api-documentationSkill
- api-security-best-practicesSkill
- architectureSkill
- bash-proSkill
- clean-codeSkill
- code-review-excellenceSkill
- debugging-strategiesSkill
- documentationSkill
- github-actions-templatesSkill
- git-pr-workflows-pr-enhanceSkill
- ios-developerSkill
- performance-optimizerSkill
- rust-async-patternsSkill
- rust-proSkill
- security-auditSkill
- systematic-debuggingSkill
- test-driven-developmentSkill
- testing-patternsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
38 rules. 0 are common, 5 are distinctive, and 33 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
33
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill to build, review, or improve SwiftUI features with correct state management, optimal view composition, and iOS 26+ Liquid …
- Very specific: line 15
Check property wrapper usage against the selection guide (see references/state-management.md)
- Very specific: line 16
Verify view composition follows extraction rules (see references/view-structure.md)
- Very specific: line 17
Check performance patterns are applied (see references/performance-patterns.md)
- Very specific: line 18
Verify list patterns use stable identity (see references/list-patterns.md)
- Very specific: line 19
Check animation patterns for correctness (see references/animation-basics.md, references/animation-transitions.md)
- Very specific: line 29
Ensure ForEach uses stable identity (see references/list-patterns.md)
- Very specific: line 39
Keep business logic in services and models for testability (see references/layout-best-practices.md)
- Very specific: line 40
Use correct animation patterns (implicit vs explicit, transitions, see references/animation-basics.md, references/animation-transitions.md, …
- Very specific: line 41
Use Button for tappable elements, add accessibility grouping and labels (see references/accessibility-patterns.md)
- Very specific: line 52
Use let for read-only values.
- Very specific: line 53
Never pass values into @State or @StateObject — they only accept initial values
- Distinctive: line 58
Prefer modifiers over conditional views for state changes (maintains view identity)
- Very specific: line 59
Keep view body simple and pure (no side effects or complex logic)
- Very specific: line 60
Use @ViewBuilder functions only for small, simple sections
- Very specific: line 61
Prefer @ViewBuilder let content: Content over closure-based content properties
- Distinctive: line 62
Keep business logic in services and models.
- Distinctive: line 69
Check for value changes before assigning state in hot paths
- Very specific: line 70
Avoid redundant state updates in onReceive, onChange, scroll handlers
- Very specific: line 72
Use LazyVStack/LazyHStack for large lists
- Very specific: line 73
Use stable identity for ForEach (never .indices for dynamic content)
- Very specific: line 74
Ensure constant number of views per ForEach element
- Very specific: line 75
Avoid inline filtering in ForEach (prefilter and cache)
- Very specific: line 76
Avoid AnyView in list rows
- Distinctive: line 77
Consider POD views for fast diffing (or wrap expensive views in POD parents)
- Very specific: line 79
Avoid layout thrash (deep hierarchies, excessive GeometryReader)
- Very specific: line 81
Use Self._logChanges() or Self._printChanges() to debug unexpected view updates
- Very specific: line 84
Use .animation(_:value:) with value parameter (deprecated version without value is too broad)
- Very specific: line 85
Use withAnimation for event-driven animations (button taps, gestures)
- Very specific: line 86
Prefer transforms (offset, scale, rotation) over layout changes (frame) for performance
- Very specific: line 89
Use .phaseAnimator for multi-step sequences (iOS 17+)
- Very specific: line 90
Use .keyframeAnimator for precise timing control (iOS 17+)
- Very specific: line 95
Prefer Button over onTapGesture for tappable elements (free VoiceOver support)
- Very specific: line 96
Use @ScaledMetric for custom numeric values that should scale with Dynamic Type
- Very specific: line 99
Use accessibilityRepresentation for custom controls that should behave like native ones
- Very specific: line 103
Use native glassEffect, GlassEffectContainer, and glass button styles
- Very specific: line 106
Use .interactive() only for tappable/focusable elements
- Very specific: line 107
Use glassEffectID with @Namespace for morphing transitions
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SwiftUI Expert Skill
Overview
Use this skill to build, review, or improve SwiftUI features with correct state management, 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.
Workflow Decision Tree
1) Review existing SwiftUI code
- First, consult
references/latest-apis.mdto ensure only current, non-deprecated APIs are used - Check property wrapper usage against the selection guide (see
references/state-management.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) - Check animation patterns for correctness (see
references/animation-basics.md,references/animation-transitions.md) - Review accessibility: proper grouping, traits, Dynamic Type support (see
references/accessibility-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
- First, consult
references/latest-apis.mdto replace any deprecated APIs with their modern equivalents - Audit state management for correct wrapper selection (see
references/state-management.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) - Improve animation patterns (use value parameter, proper transitions, see
references/animation-basics.md,references/animation-transitions.md) - Improve accessibility: use
Buttonover tap gestures, add@ScaledMetricfor Dynamic Type (seereferences/accessibility-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
- First, consult
references/latest-apis.mdto use only current, non-deprecated APIs for the target deployment version - Design data flow first: identify owned vs injected state (see
references/state-management.md) - Structure views for optimal diffing (extract subviews early, see
references/view-structure.md) - Keep business logic in services and models for testability (see
references/layout-best-practices.md) - Use correct animation patterns (implicit vs explicit, transitions, see
references/animation-basics.md,references/animation-transitions.md,references/animation-advanced.md) - Use
Buttonfor tappable elements, add accessibility grouping and labels (seereferences/accessibility-patterns.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
@Statemust beprivate; use for internal view state@Bindingonly when a child needs to modify parent state@StateObjectwhen view creates the object;@ObservedObjectwhen injected- iOS 17+: Use
@Statewith@Observableclasses; use@Bindablefor injected observables needing bindings - Use
letfor read-only values;var+.onChange()for reactive reads - Never pass values into
@Stateor@StateObject— they only accept initial values - Nested
ObservableObjectdoesn't propagate changes — pass nested objects directly;@Observablehandles nesting fine
View Composition
- Extract complex views into separate subviews for better readability and performance
- Prefer modifiers over conditional views for state changes (maintains view identity)
- 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 - Keep business logic in services and models; views should orchestrate UI flow
- Action handlers should reference methods, not contain inline logic
- 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._logChanges()orSelf._printChanges()to debug unexpected view updates
Animations
- Use
.animation(_:value:)with value parameter (deprecated version without value is too broad) - Use
withAnimationfor event-driven animations (button taps, gestures) - Prefer transforms (
offset,scale,rotation) over layout changes (frame) for performance - Transitions require animations outside the conditional structure
- Custom
Animatableimplementations must have explicitanimatableData - Use
.phaseAnimatorfor multi-step sequences (iOS 17+) - Use
.keyframeAnimatorfor precise timing control (iOS 17+) - Animation completion handlers need
.transaction(value:)for reexecution - Implicit animations override explicit animations (later in view tree wins)
Accessibility
- Prefer
ButtonoveronTapGesturefor tappable elements (free VoiceOver support) - Use
@ScaledMetricfor custom numeric values that should scale with Dynamic Type - Group related elements with
accessibilityElement(children: .combine)for joined labels - Provide
accessibilityLabelwhen default labels are unclear or missing - Use
accessibilityRepresentationfor custom controls that should behave like native ones
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
| Wrapper | Use When |
@State | Internal view state (must be private) |
@Binding | Child modifies parent's state |
@StateObject | View owns an ObservableObject |
@ObservedObject | View receives an ObservableObject |
@Bindable | iOS 17+: Injected @Observable needing bindings |
let | Read-only value from parent |
var | Read-only value watched via .onChange() |
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
Latest APIs (see references/latest-apis.md)
- No deprecated modifiers used (check against the quick lookup table)
- API choices match the project's minimum deployment target
State Management
@Stateproperties areprivate@Bindingonly where child modifies parent state@StateObjectfor owned,@ObservedObjectfor injected- iOS 17+:
@Statewith@Observable,@Bindablefor injected - Passed values NOT declared as
@Stateor@StateObject - Nested
ObservableObjectavoided (or passed directly to child views)
Sheets & Navigation (see references/sheet-navigation-patterns.md)
- Using
.sheet(item:)for model-based sheets - Sheets own their actions and dismiss internally
ScrollView (see references/scroll-patterns.md)
- Using
ScrollViewReaderwith stable IDs for programmatic scrolling
View Structure (see references/view-structure.md)
- Using modifiers instead of conditionals for state changes
- Complex views extracted to separate subviews
- 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 kept in services and models (not in views)
- Action handlers reference methods (not inline logic)
- Using relative layout (not hard-coded constants)
- Views work in any context (context-agnostic)
Animations (see references/animation-basics.md, references/animation-transitions.md, references/animation-advanced.md)
- Using
.animation(_:value:)with value parameter - Using
withAnimationfor event-driven animations - Transitions paired with animations outside conditional structure
- Custom
Animatablehas explicitanimatableDataimplementation - Preferring transforms over layout changes for animation performance
- Phase animations for multi-step sequences (iOS 17+)
- Keyframe animations for precise timing (iOS 17+)
- Completion handlers use
.transaction(value:)for reexecution
Accessibility (see references/accessibility-patterns.md)
Buttonused instead ofonTapGesturefor tappable elements@ScaledMetricused for custom values that should scale with Dynamic Type- Related elements grouped with
accessibilityElement(children:) - Custom controls use
accessibilityRepresentationwhen appropriate
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/latest-apis.md- Required reading for all workflows. Version-segmented guide of deprecated-to-modern API transitions (iOS 15+ through iOS 26+)references/state-management.md- Property wrappers and data flowreferences/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/accessibility-patterns.md- Accessibility traits, grouping, Dynamic Type, and VoiceOverreferences/animation-basics.md- Core animation concepts, implicit/explicit animations, timing, performancereferences/animation-transitions.md- Transitions, custom transitions, Animatable protocolreferences/animation-advanced.md- Transactions, phase/keyframe animations (iOS 17+), completion handlers (iOS 17+)references/sheet-navigation-patterns.md- Sheet presentation and navigation patternsreferences/scroll-patterns.md- ScrollView patterns and programmatic scrollingreferences/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 optimize for performance and maintainability
- We follow Apple's Human Interface Guidelines and API design patterns
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

