SwiftUI Pro

Install

npx skills add https://github.com/twostraws/swiftui-agent-skill --skill swiftui-pro

This is third-party code. Review the repository files before installing.

What it does

The skill targets the mistakes language models most often make in SwiftUI: deprecated APIs, buttons invisible to VoiceOver and code with surprise performance problems. Review runs in steps, each with its own reference: APIs, views and modifiers, data flow, navigation, Human Interface Guidelines design, accessibility including Dynamic Type and Reduce Motion, performance, Swift and code hygiene. It assumes iOS 26 and Swift 6.2 and does not add third-party frameworks without asking. Findings are grouped by file with line, rule name and a before and after fix, ending with a prioritized list.

Who it is for. For iOS developers writing SwiftUI interfaces with an agent.

Example request

/swiftui-pro Check for deprecated API

Limitations

Rules assume iOS 26 and Swift 6.2, so some advice will not fit older deployment targets. The skill analyzes code and does not run builds or tests.

How to disable. Uninstall the swiftui-pro plugin via /plugin or delete the swiftui-pro folder from the skills directory.

Security check

• The skill consists of review rules and references

README in short

The README explains the skill grew out of the author's AGENTS.md and targets typical model mistakes in SwiftUI. Install via npx skills with agent and scope selection or the Claude Code plugin marketplace, plus a video for Xcode. It shows invocation in Claude Code and Codex and partial reviews. MIT licensed.

SKILL.md

---
name: swiftui-pro
description: Comprehensively reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. Use when reading, writing, or reviewing SwiftUI projects.
license: MIT
metadata:
  author: Paul Hudson
  version: "1.1"
---

Review Swift and SwiftUI code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems - do not nitpick or invent issues.

Review process:

1. Check for deprecated API using `references/api.md`.
1. Check that views, modifiers, and animations have been written optimally using `references/views.md`.
1. Validate that data flow is configured correctly using `references/data.md`.
1. Ensure navigation is updated and performant using `references/navigation.md`.
1. Ensure the code uses designs that are accessible and compliant with Apple’s Human Interface Guidelines using `references/design.md`.
1. Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using `references/accessibility.md`.
1. Ensure the code is able to run efficiently using `references/performance.md`.
1. Quick validation of Swift code using `references/swift.md`.
1. Final code hygiene check using `references/hygiene.md`.

If doing a partial review, load only the relevant reference files.


## Core Instructions

- iOS 26 exists, and is the default deployment target for new apps.
- Target Swift 6.2 or later, using modern Swift concurrency.
- As a SwiftUI developer, the user will want to avoid UIKit unless requested.
- Do not introduce third-party frameworks without asking first.
- Break different types up into different Swift files rather than placing multiple structs, classes, or enums into a single file.
- Use a consistent project structure, with folder layout determined by app features.

Related