SwiftUI Expert Skill
A SwiftUI best practices skill: state, view composition, performance, new APIs, Liquid Glass and Instruments trace analysis
- 3,781 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent runs Python scripts over xctrace to record and analyze Instruments traces
- The rest of the skill is rules and references
Install
- Works in
Manual install
npx skills@latest add https://github.com/avdlee/swiftui-agent-skill --skill swiftui-expert-skillAccess and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent runs Python scripts over xctrace to record and analyze Instruments traces
- The rest of the skill is rules and references
This is third-party code. Review the repository files before installing.
What it does
The skill gives the agent vetted rules for writing and reviewing SwiftUI code on iOS and macOS. It guides property wrapper and @Observable choice, invalidation-aware view extraction, stable list identity, navigation, sheets, Swift Charts, animations, accessibility and macOS windows. A latest-APIs reference maps deprecated calls to modern ones up to SDK 27, and Liquid Glass is adopted only on request. It also ships Python scripts over xctrace that record and analyze Instruments traces and tie hangs and hitches to specific views.
Who it is for. For iOS and macOS developers building SwiftUI interfaces with an agent.
Good fit when
- You need a SwiftUI code review for state management and performance issues
- You need to migrate deprecated APIs
- The app hangs and you need to analyze an Instruments trace
Not a fit when
- The project is UIKit without SwiftUI
- You need architecture decisions; the skill deliberately avoids them
Example request
Use the swiftui expert skill and review the current views for state and performance issuesLimitations
The skill does not enforce architecture or code style. Trace recording and analysis work only on macOS with Xcode installed. The latest-APIs reference needs updating after Apple releases.
How to disable. Remove the swiftui-expert plugin via /plugin or run npx skills remove swiftui-expert-skill.
FAQ
Can I enable it for my whole team?
Yes, add the marketplace and plugin to the repo's .claude/settings.json and Claude Code prompts each member to install.
Does it rewrite deprecated APIs?
It replaces hard-deprecated APIs and only flags soft-deprecated ones unless you ask for migration.
Discussion
No questions or reviews yet.
Related
SkillsPaul Hudson's skill for reviewing and writing SwiftUI for iOS 26: deprecated APIs, data flow, navigation, accessibility, performance
Skills for Apple development: SwiftUI, UIKit and Liquid Glass references, Swift 6 guides and a router for iOS 26+ tasks
A set of skills for iOS 26+, Swift 6.3 and SwiftUI that gives the agent knowledge of modern Apple frameworks
SwiftUI Design Skill
swiftui-design-skill
A SwiftUI interface design skill: compilable code, tokens, patterns and six rules against AI sloppiness. One-command installation through npx skills
A skill and MCP server with a library of ready SwiftUI components and recipes so the agent builds iOS screens from tested code instead of writing them from scra
A skill that builds in-app screen and element capture for a SwiftUI app and loops it across every locale for the App Store
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| SwiftUI Expert Skill (this entry) | no | 3,781 | ||
| Apple Skills | no | 349 | skills for Apple development | |
| Apple Doc MCP | no | not required | 632 | an MCP server that lets the agent search symbols and read Apple's |
README in short
The README lists the audience and topics, from state and navigation to Swift Charts and SDK 27. Install via skills.sh, the OpenAI plugins directory for Codex, the Claude Code marketplace with project-level setup, or the Cursor plugin. It details the Instruments trace recording and analysis scripts, shows the reference layout and credits the sources behind the rules. MIT licensed.
README badge
Original SKILL.md
--- name: swiftui-expert-skill description: Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state and `@Observable` data flow, view composition, performance, lists, environment, localization, animation, Liquid Glass, and API migration. Also use for `@State` initialization or synthesized-property diagnostics, `@ContentBuilder` ambiguity, `reorderable` drag/drop, custom `AsyncImage` `URLSession`, swipe actions outside List, item-bound `alert`/`confirmationDialog`, `ToolbarOverflowMenu`, `AnimatableValues`, Document APIs (`Document`/`DocumentReader`), and Instruments `.trace` capture or analysis. --- # SwiftUI Expert Skill ## Operating Rules - Treat each `View` type as an invalidation boundary: give it only the data it reads and keep frequently changing dependencies close to the smallest affected subtree - Search `references/latest-apis.md` when writing, reviewing, or migrating API usage; look up only the APIs relevant to the task - Replace hard-deprecated APIs with modern equivalents. During feature work, flag soft-deprecated APIs and leave them in place (see `references/soft-deprecation.md`) - Prefer native SwiftUI APIs over UIKit/AppKit bridging unless bridging is necessary - Focus on correctness and performance; do not enforce specific architectures (MVVM, VIPER, etc.) - Encourage separating business logic from views for testability without mandating how - Follow Apple's Human Interface Guidelines and API design patterns - Only adopt Liquid Glass when explicitly requested by the user (see `references/liquid-glass.md`) - Present performance optimizations as suggestions, not requirements - Use `#available` gating with sensible fallbacks for version-specific APIs ## Task Workflow ### Review existing SwiftUI code - Read the code under review and identify which topics apply - Flag deprecated APIs (compare against `references/latest-apis.md`); replace hard-deprecated APIs, and flag soft-deprecated APIs without rewriting them unless the user asked to migrate - Run the Topic Router below for each relevant topic - Validate `#available` gating and fallback paths for version-specific features