swiftui-pro

SwiftUI Agent Skill for AI Coding Assistants

An agent skill that helps AI coding assistants write smarter, simpler, and more modern SwiftUI, including guidance on API usage, design, performance, and accessibility. Covers navigation, layout, animations, state management, VoiceOver, deprecated API, and more, targeting the mistakes LLMs actually make.

Also available:

Find more agent skills for Swift and Apple platform development at Swift Agent Skills.

The skill builds upon my existing AGENTS.md file, meaning that you can bring years of knowledge and practical experience into your coding agent of choice in just a few minutes. It uses the Agent Skills format, so it works smoothly with Claude Code, Codex, Gemini, Cursor, and more.

Installing SwiftUI Pro

You can install this skill into Claude Code, Codex, Gemini, Cursor, and more by using npx:

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

If you get the error npx: command not found, it means you don’t currently have Node installed. You need to run this command to install Node through Homebrew:

brew install node

And if that fails it usually means you need to install Homebrew first.

When using npx, you can select exactly which agents you want to use during the installation. You can also select whether the skill should be installed just for one project, or whether it should be made available for all your projects.

Claude Code users can add the SwiftUI Agent Skill marketplace then install the plugin directly through Claude, like this:

/plugin marketplace add twostraws/SwiftUI-Agent-Skill
/plugin install swiftui-pro@swiftui-agent-skill

Alternatively, you can clone this whole repository and install it however you want.

If you’re using Xcode, watch the YouTube video on How to Install and Use Agent Skills in Xcode for a walkthrough.

Using SwiftUI Pro

The skill is called SwiftUI Pro, and can be triggered in various ways. For example, in Claude Code you would use this:

/swiftui-pro

And in Codex you would use this:

$swiftui-pro

In both cases you can provide specific instructions if you want only a partial review. For example, /swiftui-pro Check for deprecated API on Claude, or $swiftui-pro Focus on accessibility in Codex.

You can also trigger the skill using natural language:

Use the SwiftUI Pro skill to look for performance problems in this project.

Why Use an Agent Skill for SwiftUI?

This skill is built on thousands of hours of learning, experimenting, and building real-world SwiftUI projects. The rules contained here directly target common SwiftUI mistakes made by LLMs. They sometimes make buttons invisible to VoiceOver, they frequently use deprecated API, and they would often write code that causes surprise performance problems.

You can read more about why I created this skill in my article: SwiftUI Agent Skill - Write better code with Claude, Codex, and other AI tools.

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.
2. Check that views, modifiers, and animations have been written optimally using references/views.md.
3. Validate that data flow is configured correctly using references/data.md.
4. Ensure navigation is updated and performant using references/navigation.md.
5. Ensure the code uses designs that are accessible and compliant with Apple’s Human Interface Guidelines using references/design.md.
6. Validate accessibility compliance including Dynamic Type, VoiceOver, and Reduce Motion using references/accessibility.md.
7. Ensure the code is able to run efficiently using references/performance.md.
8. Quick validation of Swift code using references/swift.md.
9. 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.

Output Format

Organize findings by file. For each issue:

1. State the file and relevant line(s).
2. Name the rule being violated (e.g., "Use foregroundStyle() instead of foregroundColor()").
3. Show a brief before/after code fix.

Skip files with no issues. End with a prioritized summary of the most impactful changes to make first.

Example output:

ContentView.swift

**Line 12: Use foregroundStyle() instead of foregroundColor().**

// Before
Text("Hello").foregroundColor(.red)

// After
Text("Hello").foregroundStyle(.red)

Line 24: Icon-only button is bad for VoiceOver - add a text label.

// Before
Button(action: addUser) {
    Image(systemName: "plus")
}

// After
Button("Add User", systemImage: "plus", action: addUser)

**Line 31: Avoid Binding(get:set:) in view body - use @State with onChange() instead.**

// Before
TextField("Username", text: Binding(
    get: { model.username },
    set: { model.username = $0; model.save() }
))

// After
TextField("Username", text: $model.username)
    .onChange(of: model.username) {
        model.save()
    }

Summary

1. Accessibility (high): The add button on line 24 is invisible to VoiceOver.
2. Deprecated API (medium): foregroundColor() on line 12 should be foregroundStyle().
3. Data flow (medium): The manual binding on line 31 is fragile and harder to maintain.

End of example.