swiftui-expert-skill

Review SwiftUI code for correctness, performance, and modern API adoption.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/obadasemary/Woko --skill swiftui-expert-skill-obadasemary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swiftui-expert-skill
Source: https://github.com/obadasemary/Woko/tree/main/.claude/skills/swiftui-expert-skill
Command: npx skills add https://github.com/obadasemary/Woko --skill swiftui-expert-skill-obadasemary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you write, review, and improve SwiftUI code that is correct, performant, and aligned with modern Apple APIs, reducing bugs from weak state handling, outdated navigation patterns, and inefficient view structure.

Core Features & Use Cases

  • State Management Guidance: Choose the right ownership and binding strategy for view state, injected models, and shared data.
  • Modern API Review: Replace deprecated SwiftUI patterns with current equivalents for navigation, styling, text formatting, sheets, scrolling, and interactions.
  • Performance and Structure Feedback: Spot unnecessary body work, unstable list identity, deep view hierarchies, and other patterns that hurt rendering efficiency.
  • Use Case: Review a feed, form, or detail screen before shipping to ensure it uses stable identity, clean subviews, responsive layout, and sensible iOS availability fallbacks.

Quick Start

Ask the SwiftUI Expert Skill to review this SwiftUI view for state management, performance, modern API usage, and iOS 26 compatibility.

Frequently Asked Questions about swiftui-expert-skill

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

FAQPage Schema
How do I review SwiftUI code for state management and performance issues?

To review SwiftUI code for state management and performance, check state ownership, binding strategies, stable list identity, and view hierarchy depth to eliminate unnecessary body work and rendering inefficiencies.

What is the best way to replace deprecated SwiftUI patterns with modern APIs?

To replace deprecated SwiftUI patterns with modern APIs, update navigation flows, styling, text formatting, and sheet presentations while ensuring deprecated features have proper fallback handling for platform-specific contexts.

Does this SwiftUI review approach support iOS 26 and Liquid Glass styling decisions?

Yes, SwiftUI review supports iOS 26 compatibility and Liquid Glass styling decisions by applying availability gating and checking fallback handling for deprecated or platform-specific features during code review.

How do I choose the right SwiftUI state ownership and binding strategy for shared data?

To choose the right SwiftUI state ownership and binding strategy for shared data, evaluate view state, injected models, and shared data requirements to ensure correct ownership boundaries and prevent weak state handling bugs.

Why does my SwiftUI list exhibit unstable identity and unnecessary body work?

SwiftUI lists exhibit unstable identity and unnecessary body work when view hierarchy depth is mismanaged and list identity protocols are unstable, requiring structural feedback to optimize rendering efficiency.