swiftui-pro

Reviews SwiftUI code for modern API usage, accessibility, performance, and data flow correctness.

1|Updated Aug 9, 2026
One-click install
npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill swiftui-pro-omixec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swiftui-pro
Source: https://github.com/OMIXEC/all-in-one-swift-skills/tree/main/skills/swiftui-pro
Command: npx skills add https://github.com/OMIXEC/all-in-one-swift-skills --skill swiftui-pro-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SwiftUI codebases accumulate deprecated APIs, accessibility gaps, and performance anti-patterns that are hard to catch manually. This Skill performs a structured, rule-based review of Swift and SwiftUI code against current Apple platform conventions. ## Core Features & Use Cases - Modern API enforcement: Flags deprecated patterns like foregroundColor(), NavigationView, and 1-parameter onChange(), with before/after fixes. - Nine review domains: Covers accessibility, data flow, navigation, performance, design, Swift concurrency, and code hygiene via dedicated reference files. - Prioritized findings: Reports issues by file with rule names, code fixes, and a ranked summary of the most impactful changes. - Use Case: Paste a SwiftUI view into your agent and receive a line-by-line review flagging VoiceOver-inaccessible buttons, fragile Binding(get:set:) usage, and eager stacks that should be lazy. ## Quick Start Ask the agent to review your SwiftUI view file for best practices, deprecated APIs, and accessibility issues.

Frequently Asked Questions about swiftui-pro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review SwiftUI code for deprecated APIs?▼

Run a structured review that flags deprecated patterns like foregroundColor(), cornerRadius(), NavigationView, and 1-parameter onChange(), replacing each with the modern equivalent such as foregroundStyle() or NavigationStack. Findings include before/after code fixes per line.

What are SwiftUI best practices for data flow and state?▼

Use @Observable classes marked @MainActor with @State for ownership and @Bindable or @Environment for passing. Avoid ObservableObject, @StateObject, and Binding(get:set:) in view bodies; prefer bindings from @State with onChange() for side effects.

Does this SwiftUI review cover accessibility and VoiceOver?▼

Yes, it validates Dynamic Type usage, VoiceOver labels on icon-only buttons, Reduce Motion alternatives, and minimum 44x44 tap targets. It flags onTapGesture() misuse and missing accessibilityLabel() on informative images.

Can I review only part of my SwiftUI code?▼

Yes, partial reviews load only the relevant reference files, such as performance.md for rendering issues or navigation.md for NavigationStack problems. You can scope the review to a single concern instead of running all nine domains.

Why should I avoid GeometryReader in SwiftUI layouts?▼

GeometryReader is often unnecessary because modern alternatives like containerRelativeFrame(), visualEffect(), and the Layout protocol handle sizing more efficiently. The review flags GeometryReader usage and suggests the appropriate modern replacement.