Tooluck logoTooluck
SKILL.md

swiftui-expert-skill

Agent skill fromAvdLee/SwiftUI-Agent-Skill

Use when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state and `@Observable` data flow, view composition, resizable layouts, safe areas, display scale, performance, lists, environment, localization, animation, Liquid Glass, and API migration. Also use for iPhone Duo, foldable, or large-display layouts (`NavigationSplitView` on large displays, iPhone tab sidebar, two-column reflow, foldable grids, `ArrangementView`, `ReservedRegion`), hinge effects, vertical bars, `@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.

How to install swiftui-expert-skill

install swiftui-expert-skill
# install the SwiftUI-Agent-Skill pack with the skills CLI
npx skills add AvdLee/SwiftUI-Agent-Skill

# or add only this skill to Claude Code: copy the folder

skills/swiftui-expert-skill/

# into

~/.claude/skills/swiftui-expert-skill/ (all projects)

.claude/skills/swiftui-expert-skill/ (one project)

skills/swiftui-expert-skill/SKILL.md

MITFull file
1# SwiftUI Expert Skill
2
3## Operating Rules
4
5- 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
6- Search `references/latest-apis.md` when writing, reviewing, or migrating API usage; look up only the APIs relevant to the task
7- Replace hard-deprecated APIs with modern equivalents. During feature work, flag soft-deprecated APIs and leave them in place (see `references/soft-deprecation.md`)
8- Prefer native SwiftUI APIs over UIKit/AppKit bridging unless bridging is necessary
9- Focus on correctness and performance; do not enforce specific architectures (MVVM, VIPER, etc.)
10- Encourage separating business logic from views for testability without mandating how
11- Follow Apple's Human Interface Guidelines and API design patterns
12- Only adopt Liquid Glass when explicitly requested by the user (see `references/liquid-glass.md`)
13- Present performance optimizations as suggestions, not requirements
14- Use `#available` gating with sensible fallbacks for version-specific APIs
15- For layout and rendering inputs, read the value nearest the SwiftUI view that consumes it; do not substitute process-global screen state
16
17## Task Workflow
18
19### Review existing SwiftUI code
20- Read the code under review and identify which topics apply
21…

Excerpt shown under the repository's MIT license.

Keep exploring

Similar skill repositories

Newsletter

Join the Community

Subscribe to our newsletter for the latest news and updates