swiftui-expert-skill

Review and refactor SwiftUI code for modern state management and iOS 26+ Liquid Glass.

4|Updated Apr 21, 2013
One-click install
npx skills add https://github.com/zeero/dotfiles --skill swiftui-expert-skill-zeero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swiftui-expert-skill
Source: https://github.com/zeero/dotfiles/tree/main/home/.claude/skills/swiftui-expert-skill
Command: npx skills add https://github.com/zeero/dotfiles --skill swiftui-expert-skill-zeero

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers in writing, reviewing, and refining SwiftUI code to meet modern best practices for state management, view composition, performance, Swift concurrency, and iOS 26+ Liquid Glass adoption.

Core Features & Use Cases

  • Provides a framework for evaluating SwiftUI code against up-to-date best practices, including state wrappers, modern APIs, and responsible view composition.
  • Helps teams audit, refactor, and adopt Liquid Glass styling where requested, without enforcing a rigid architecture.
  • Useful for code reviews, feature refactors, or starting new SwiftUI features that require clean data flow and high maintainability.

Quick Start

Analyze the provided SwiftUI view and return concrete recommendations: identify misuse of state wrappers, deprecated APIs, excessive view nesting, or layout inefficiencies, and propose a step-by-step plan.

Frequently Asked Questions about swiftui-expert-skill

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

FAQPage Schema
How do I refactor SwiftUI code to use modern state management and view composition?

Refactoring SwiftUI code involves migrating from ObservableObject to @Observable, replacing deprecated APIs, and extracting complex views to improve data flow and maintainability.

When do I need to adopt Liquid Glass effects in my SwiftUI app?

Adopting Liquid Glass effects is needed for iOS 26+ deployments where post-layout glass styling is requested, requiring explicit fallbacks for unsupported environments.

What is the best way to review SwiftUI code for performance bottlenecks?

The best way to review SwiftUI performance is auditing for excessive view nesting, layout inefficiencies, and outdated state wrappers, proposing a step-by-step optimization plan.

Can I use this SwiftUI code review approach for both new features and refactors?

Yes, evaluating SwiftUI against modern best practices applies cleanly to starting new features, auditing existing code, and guiding refactors without enforcing a rigid architecture.

Why does my SwiftUI view have poor performance with complex nested layouts?

Poor SwiftUI performance often stems from excessive view nesting and layout inefficiencies, which can be resolved by properly extracting complex views and optimizing data flow.