swiftui-pro

Reviews SwiftUI code for modern API usage, accessibility, performance, and maintainability.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/RavitejaKarra24/dotfiles --skill swiftui-pro-ravitejakarra24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swiftui-pro
Source: https://github.com/RavitejaKarra24/dotfiles/tree/main/agents/.agents/skills/swiftui-pro
Command: npx skills add https://github.com/RavitejaKarra24/dotfiles --skill swiftui-pro-ravitejakarra24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? SwiftUI evolves rapidly, and 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 so genuine problems are found and fixed with concrete before/after corrections. ## Core Features & Use Cases - Nine-dimension code review: Checks deprecated APIs, view structure, data flow, navigation, design, accessibility, performance, modern Swift, and code hygiene using dedicated reference guides. - Actionable findings: Reports issues organized by file with line numbers, the violated rule, and a before/after code fix, ending with a prioritized summary. - Partial reviews: Load only the relevant reference files when reviewing a specific concern such as accessibility or performance. - Use Case: Point it at an existing SwiftUI project before an iOS 26 release to flag deprecated modifiers like foregroundColor(), missing VoiceOver labels on icon-only buttons, and GeometryReader usages that should migrate to containerRelativeFrame(). ## Quick Start Use the swiftui-pro skill to review my SwiftUI project for deprecated APIs, accessibility issues, and performance problems.

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 checks each file against a modern API reference, flagging patterns like foregroundColor(), cornerRadius(), and NavigationView. Each finding includes the violated rule and a before/after code fix using the current replacement API.

What should a SwiftUI code review checklist include?

A thorough checklist covers deprecated APIs, view composition, data flow with @Observable, navigation with NavigationStack, accessibility, performance, modern Swift concurrency, and code hygiene. Reviewing each dimension separately keeps findings accurate and avoids nitpicking.

Does this work with Swift 6 and iOS 26 projects?

Yes, the review targets Swift 6.2 or later with modern Swift concurrency and treats iOS 26 as the default deployment target. It flags GCD usage, missing @MainActor annotations, and legacy patterns replaced by newer iOS 26 APIs like the native WebView.

Can I review only accessibility or performance issues in SwiftUI?

Yes, partial reviews are supported by loading only the relevant reference file, such as accessibility.md for Dynamic Type and VoiceOver checks or performance.md for rendering efficiency. This keeps the review focused on one concern.

When should I avoid ObservableObject in SwiftUI?

Prefer @Observable classes with @State and @Bindable for shared state instead of ObservableObject, @Published, and @StateObject. ObservableObject remains acceptable only in legacy or integration contexts, and requires an explicit import Combine.