swiftui-expert-skill

Analyze and refactor SwiftUI code for state management and Liquid Glass adoption.

1|1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/andrea-sdl/kotoba-libre --skill swiftui-expert-skill-andrea-sdl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swiftui-expert-skill
Source: https://github.com/andrea-sdl/kotoba-libre/tree/main/.agents/skills/swiftui-expert-skill
Command: npx skills add https://github.com/andrea-sdl/kotoba-libre --skill swiftui-expert-skill-andrea-sdl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SwiftUI development often suffers from inconsistent state management, brittle view composition, and missed opportunities to adopt iOS 26+ Liquid Glass patterns. This skill provides a structured approach to building, reviewing, and refining SwiftUI code to align with native APIs, Apple's design guidance, and performance-conscious patterns.

Core Features & Use Cases

  • Review and validate existing SwiftUI code against current APIs and guidelines.
  • Refactor complex views for better state management, composition, and accessibility.
  • Implement or review SwiftUI features using iOS 26+ Liquid Glass styling with proper fallback paths.
  • Use real-world examples to improve performance and maintainability.

Quick Start

Review a SwiftUI module and align it with iOS 26+ Liquid Glass guidelines, updating state management and view structure accordingly.

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 views for better state management and view composition?

Refactoring SwiftUI views involves applying best practices for per-item observable state, stable identity in lists, and modular view composition to improve maintainability and alignment with native APIs.

What are the best practices for adopting iOS 26 Liquid Glass effects in SwiftUI?

Adopting iOS 26 Liquid Glass effects requires applying proper glass styling patterns with fallback paths, validating existing code against current APIs, and following Apple's design guidance for modern SwiftUI features.

How do I review SwiftUI code quality for performance and maintainability?

SwiftUI code review checks state management consistency, view composition brittleness, stable list identity, and performance-conscious patterns against native APIs and Apple's design guidance using real-world examples.

When do I need per-item observable state in SwiftUI lists?

Per-item observable state is needed in SwiftUI lists when individual items require independent state tracking, combined with stable identity to prevent rendering issues and improve overall view performance.

Does this SwiftUI refactoring approach work with existing iOS projects?

The approach works with existing iOS projects by reviewing and validating current SwiftUI code, refactoring complex views, and adopting iOS 26+ patterns with proper fallback paths for backward compatibility.

What's the best way to handle state management in complex SwiftUI views?

Handling state management in complex SwiftUI views requires per-item observable state, stable identity in lists, and structured view composition following native API patterns and performance-conscious guidelines.