Check SwiftUI state and performance with swiftui-expert-skill

Who it is for

If you write SwiftUI and want an Agent to talk about state management, view composition, performance, and iOS 26+ Liquid Glass adoption in expert practice, this skill matches. It is aimed at any coding tool that supports the Agent Skills open format. Format notes:

https://agentskills.io/home

The repository is also packed as an Agent Plugin (spec 1.0.0): compatible clients auto-discover skills from the root plugin.json and skills/. Plugin spec:

https://agent-plugins.org/

It gives guidance; it does not promise that edits will compile. If you have no SwiftUI code and do not plan to discuss those topics, do not install first.

First try in 3 minutes

Open the official repository and confirm the source:

https://github.com/avdlee/swiftui-agent-skill

Install writes skills. After you confirm, copy only this official command; do not drop --skill or the skill name:

npx skills add https://github.com/avdlee/swiftui-agent-skill --skill swiftui-expert-skill

A normal finish with no terminal error is the install-success signal. The source does not write an install directory; do not invent a path. The source also has no second installer; do not invent a marketplace command.

Then open existing SwiftUI code and trigger the first time with the source sentence: Use the swiftui expert skill and review the current SwiftUI code for state-management and performance improvements. This is a check, not a default file change. Watch whether the Agent gives concrete notes on state management and performance. If it starts changing code at once, stop and confirm you accept a file write before continuing. The first time, do not also ask to land Liquid Glass.

Usage examples

Example 1: Check state management and performance of current SwiftUI. The source writes usage as that English request above. It fits people who already have interface code and only want advice first. Confirm the target file before you speak; success is receiving notes on state and performance. The source gives no checklist or severity grades; do not invent a score sheet.

Example 2: Discuss iOS 26+ Liquid Glass adoption. The source writes the capability scope as SwiftUI state management, view composition, performance, and iOS 26+ Liquid Glass adoption. It fits people already looking at the new-system look who only want to compare against the guidance. First confirm you are discussing how to adopt, not changing the project at once; if you later want code changes, confirm the file write separately. The source gives no API roster and no detail beyond the minimum system version; do not add interfaces that never appear.

Limits

The only recommended install is the npx skills add line with --skill swiftui-expert-skill. Do not change the skill name, and do not invent a skills add variant that never appears. The source wrote an exclusive inventory for several clients and said compatible clients auto-discover from plugin.json and skills/. Do not copy that client roster into the body, and do not claim support only for tools on it.

The evidence covers guidance: state management, view composition, performance, Liquid Glass. The source gives no automatic refactor command or test scaffold. Read the English review as checking code, not as an unauthorized batch rewrite. Do not fill in UIKit migration or non-SwiftUI topics that were never written.