swiftui-expert-skill

Review SwiftUI code for correctness, maintainability, and modern API usage.

1|Updated Apr 15, 2025
One-click install
npx skills add https://github.com/unPi-ro/unPiNetworking --skill swiftui-expert-skill-unpi-ro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swiftui-expert-skill
Source: https://github.com/unPi-ro/unPiNetworking/tree/main/.claude/skills/swiftui-expert-skill
Command: npx skills add https://github.com/unPi-ro/unPiNetworking --skill swiftui-expert-skill-unpi-ro

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 frameworks, reducing bugs caused by outdated patterns and inconsistent state handling.

Core Features & Use Cases

  • State Management Guidance: Choose the right property wrappers for owned, injected, and shared data, with a preference for @Observable and clear ownership boundaries.
  • Modern API Refactoring: Replace deprecated SwiftUI patterns with newer equivalents for navigation, styling, scrolling, text formatting, and interaction.
  • Performance and Structure Reviews: Improve view composition, list identity, layout efficiency, and update behavior in complex SwiftUI screens.
  • iOS 26 Liquid Glass Adoption: Apply Glass effect styling with availability checks and fallbacks when explicitly requested.
  • Use Case: Refactor a large feed screen to use stable ForEach identity, smaller subviews, cleaner state flow, and modern navigation while preserving behavior.

Quick Start

Ask the SwiftUI expert skill to review this view or feature and return concrete fixes for state management, modern API usage, performance, and iOS version 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 choose the right SwiftUI property wrappers for state management?

Use @State for owned view data, @Observable for shared models, and @Binding or @Bindable for injected values to maintain clear ownership boundaries and ensure correct view updates.

What is the best way to refactor a large SwiftUI feed screen for performance?

Refactoring a large SwiftUI feed screen for performance requires using stable ForEach identity, extracting smaller subviews, applying performance-conscious modifier patterns, and streamlining state flow to reduce unnecessary view updates.

How do I adopt iOS 26 Liquid Glass styling with availability checks in SwiftUI?

Adopting iOS 26 Liquid Glass styling in SwiftUI requires applying Glass effect modifiers while implementing availability checks and providing fallback styling patterns for older iOS versions to ensure consistent behavior.

Why does my SwiftUI ForEach list have rendering bugs and update issues?

SwiftUI ForEach rendering bugs and update issues occur when list identity is unstable, requiring you to provide stable identifiers to items so the diffing engine can track views correctly across data changes.

Can I replace deprecated SwiftUI navigation patterns with modern APIs?

You can replace deprecated SwiftUI navigation patterns with modern APIs by adopting newer navigation equivalents for routing and stack management, ensuring cleaner state flow and improved maintainability in your feature implementation.

Do I need availability checks to use modern SwiftUI scrolling and text formatting APIs?

Availability checks are required when using modern SwiftUI scrolling and text formatting APIs to ensure the newer modifier patterns have appropriate fallbacks, preventing crashes and maintaining compatibility with older iOS versions.